
Ultimate access to all questions.
Deep dive into the quiz with AI chat providers.
We prepare a focused prompt with your quiz and certificate details so each AI can offer a more tailored, in-depth explanation.
A gaming company is moving its public scoreboard from a data center to the AWS Cloud. The company uses Amazon EC2 Windows Server instances behind an Application Load Balancer to host its dynamic application. The company needs a highly available storage solution for the application. The application consists of static files and dynamic server-side code.
Which combination of steps should a solutions architect take to meet these requirements? (Choose two.)
A
Store the static files on Amazon S3. Use Amazon CloudFront to cache objects at the edge.
B
Store the static files on Amazon S3. Use Amazon ElastiCache to cache objects at the edge.
C
Store the server-side code on Amazon Elastic File System (Amazon EFS). Mount the EFS volume on each EC2 instance to share the files.
D
Store the server-side code on Amazon FSx for Windows File Server. Mount the FSx for Windows File Server volume on each EC2 instance to share the files.
E
Store the server-side code on a General Purpose SSD (gp2) Amazon Elastic Block Store (Amazon EBS) volume. Mount the EBS volume on each EC2 instance to share the files.
Explanation:
Correct Answers: A and D
Why A is correct:
Why D is correct:
Why other options are incorrect:
B: Amazon ElastiCache is an in-memory caching service (Redis/Memcached) for database query results or session data, not for caching static objects at the edge. CloudFront is the appropriate service for edge caching.
C: Amazon EFS is a Linux-based file system (NFS protocol). While it provides shared file storage, it's not compatible with Windows Server instances, which require SMB protocol support.
E: Amazon EBS volumes are block storage devices that can only be attached to a single EC2 instance at a time. They cannot be shared across multiple instances simultaneously, which is required for server-side code that needs to be accessible by all instances behind the load balancer.
Key Architecture Principles: