I vaguely recall that changing subnet sizes could impact performance, but I'm not confident about option D. It seems like a risky move without proper planning.
I remember practicing a question similar to this where subnet overlap was important. So, option C might be the right choice, but I need to double-check that.
I think option A makes sense because routing is crucial for communication between subnets, right? But I'm not entirely sure if it's the only thing to consider.
I think option D is the way to go here. Adding a scan step right before the deployment to the EKS cluster seems like the most logical place to do it, and using an AWS Lambda function to check the results and fail the pipeline if needed is a nice touch.
Option C looks good to me - using instance templates with network tags seems like the best way to enforce consistent network security as the Web and App tiers autoscale.
Alright, let's think this through. The default configuration covers the four standard issue types, and we need new screens for the first and second sub-tasks. I think the answer is B, 4 new Screen Schemes.
upvoted 0 times
...
Log in to Pass4Success
Sign in:
Report Comment
Is the comment made by USERNAME spam or abusive?
Commenting
In order to participate in the comments you need to be logged-in.
You can sign-up or
login
Michel
4 months agoRyan
4 months agoGwenn
4 months agoMerlyn
4 months agoBreana
4 months agoCiara
5 months agoIluminada
5 months agoJamie
5 months agoBelen
5 months agoLorean
5 months agoArthur
5 months agoTamera
5 months ago