Amazon Web Services SAA-C03 Exam With Confidence Using Practice Dumps

The correct answer is A because the company wants engineers to reach a specific development EC2 instance through a Route 53 hosted zone , while ensuring that traffic continues to route correctly even if the development instance is replaced . The best way to achieve this is to point the Route 53 record for the development website to the Application Load Balancer and then configure an ALB listener rule that forwards requests for the development hostname to a dedicated target group containing the development instance.

This design works well because the ALB provides a stable endpoint, and Route 53 can alias the development DNS name to the ALB. If the development EC2 instance is replaced, the target group can simply register the new instance. The DNS record does not need to change, and engineers continue to use the same development URL. This minimizes operational effort and supports automatic continuity.

Option B is incorrect because using a public IP address for a specific instance does not automatically handle instance replacement unless additional manual steps are taken. Option C is incorrect because redirecting users to a public IP is not the intended design and introduces unnecessary exposure and management complexity. Option D is incorrect because placing all instances in the same target group would not ensure that requests for the development website are sent only to the specific development instance.

AWS best practices favor using load balancers and target groups as stable routing layers rather than binding DNS names directly to ephemeral instance IP addresses. Therefore, the most reliable and maintainable solution is to use Route 53 + ALB + a dedicated target group for the development instance.

To handle unpredictable traffic surges and improve scalability, Auto Scaling is essential. Creating an AMI and deploying it into an Auto Scaling group behind an Application Load Balancer (ALB) allows AWS to automatically scale the number of EC2 instances based on demand.

This architecture improves availability and responsiveness by distributing traffic and launching instances when needed. Option A satisfies the need for high scalability and resilience. Other options either lack Auto Scaling or are more complex without added benefit in this context.

D is the best match because AWS Lambda is a serverless compute service that runs code without provisioning or managing servers, which directly aligns with the requirement for minimal infrastructure and minimal operational support. Lambda supports Python runtimes, so the team can deploy the selected component as a microservice using the same language. For workloads with hundreds of requests per second, Lambda is designed to handle request-driven execution and automatically scales by running more concurrent instances of the function in response to incoming traffic, without the customer needing to pre-size or manage capacity.

The other options introduce significantly more operational responsibility. Option A still requires managing EC2 instances (AMI lifecycle, patching, capacity planning, scaling policies) and Spot interruptions can add complexity for a web microservice test. Option B (Elastic Beanstalk) reduces some management overhead but still relies on underlying instances and environment management (platform updates, scaling configuration, health monitoring), and it is not a serverless model. Option C (EKS with self-managed nodes) has the highest operational burden here: cluster and node management, scaling node groups, patching, and Kubernetes operations—this conflicts with “minimal operational support.”

Lambda fits the serverless microservices goal: deploy code as small independent services, integrate with other managed services (commonly API-driven invocation patterns), and rely on AWS-managed scaling and availability mechanisms rather than administering fleets or clusters.