Amazon Web Services SAA-C03 Dumps Questions Answers

Amazon ECS with Application Auto Scaling, an Application Load Balancer, and CloudFront is the strongest architecture because it supports scale, high availability, and lower operational overhead while allowing the company to reuse the existing application code through containerization. The ALB distributes traffic across ECS tasks and supports health checks. ECS Service Auto Scaling automatically adjusts running tasks based on demand, allowing the application to handle millions of requests. CloudFront improves global delivery by caching content and routing users through edge locations. A self-managed Kubernetes cluster in one Availability Zone is not highly available and creates unnecessary management work. API Gateway and Lambda would require application redesign. Keeping the origin on premises does not meet the migration goal.

This solution meets the company ' s requirements with minimal administrative overhead and ensures security and ease of management.

AWS AppConfig: AWS AppConfig is a service designed to manage application configuration in a secure and validated way. It allows you to deploy configurations safely and quickly without affecting the application ' s performance or availability.

AWS Secrets Manager: AWS Secrets Manager is specifically designed to manage, retrieve, and rotate credentials for databases and other services. It integrates seamlessly with AWS services like Amazon RDS, making it an ideal solution for securely storing and retrieving database credentials. Secrets Manager also provides automatic rotation of credentials, reducing the operational burden.

Why Not Other Options?:

Option B (AWS Lambda + Parameter Store): While AWS Lambda can be used for managing configurations and AWS Systems Manager Parameter Store can store credentials, this approach involves more manual setup and does not offer the same level of integrated management and security as AppConfig and Secrets Manager.

Option C (Encrypted S3 Configuration File): Storing configuration and credentials in S3 files involves more manual management and security considerations, increasing the administrative overhead.

Option D (AppConfig + RDS for credentials): RDS is not designed for storing application credentials; it ' s better suited for managing database instances and their configurations.

AWS References:

AWS AppConfig- Describes how to use AWS AppConfig for managing application configurations.

AWS Secrets Manager- Provides details on securely storing and retrieving credentials using AWS Secrets Manager.

Amazon SQS with Amazon ECS on AWS Fargate is the best managed architecture for containerized, loosely coupled message processing. SQS is a fully managed message queue that decouples distributed application components and scales without the operational burden of managing broker infrastructure. SNS can fan out messages to the SQS queue when publish-subscribe behavior is needed. ECS on Fargate runs containers without requiring the company to manage EC2 instances, Kubernetes worker nodes, or server capacity. Amazon MQ is useful when applications need traditional broker compatibility, but it does not provide the same virtually unlimited scaling model as SQS standard queues. EC2 Reserved Instances also violate the goal of fully managed infrastructure.