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.

AWS Lambda is not suitable for long-running jobs that can take up to 20 minutes, as Lambda has a maximum execution duration of 15 minutes.

Amazon ECS with AWS Fargate allows you to run containers without managing EC2 instances, providing a scalable and highly available environment. You can scale Fargate tasks to handle large and parallel video processing jobs. Amazon Aurora is a highly available, managed relational database. S3 Intelligent-Tiering is cost-effective for storing large video files with variable access patterns.

AWS Documentation Extract:

" AWS Fargate lets you run containers without managing servers or clusters, providing a highly available and scalable compute environment. Fargate is suitable for running data processing workloads that require long-running compute tasks. "

(Source: AWS Fargate documentation, Use Cases)

A: Lambda is not suitable for long-running (over 15 min) or heavy compute jobs.

C: Amazon EMR is optimized for big data analytics, not specific video processing. FSx for Lustre and Kinesis are not best fit for this use case.

D: EKS with EC2 adds operational overhead and RDS in a single AZ is not highly available; Glacier Deep Archive is not suitable for frequently accessed video files.

TooManyRequestsException errors occur when Lambda exceeds concurrency limits. The recommended pattern is to use Amazon SQS with Lambda to decouple and buffer traffic, ensuring that bursts of requests are queued and processed smoothly. Enabling provisioned concurrency for Lambda ensures that functions are pre-initialized and ready to handle spikes in load with low latency. Step Functions (B) is designed for workflow orchestration, not high-throughput request buffering. SNS with Lambda (C) does not provide buffering and may overwhelm Lambda during bursts. Reserved concurrency (D) limits function scaling instead of improving resilience. Therefore, option A provides a scalable and resilient solution, minimizing errors during traffic surges.