Answer-first summary for fast verification
Answer: Store the static files on Amazon S3. Use Amazon CloudFront to cache objects at the edge., 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.
## Explanation **Correct Answers:** A and D **Why A is correct:** - **Amazon S3** is ideal for storing static files (images, CSS, JavaScript, etc.) as it provides high durability, availability, and scalability. - **Amazon CloudFront** is a Content Delivery Network (CDN) that caches static content at edge locations worldwide, reducing latency and improving performance for global users. - This combination provides a highly available, scalable solution for static content delivery. **Why D is correct:** - The application runs on **Windows Server instances**, and **Amazon FSx for Windows File Server** is specifically designed for Windows-based applications. - FSx provides a fully managed, highly available Windows file system that supports SMB protocol and Active Directory integration. - Mounting FSx volumes on each EC2 instance allows multiple instances to share the same server-side code, ensuring consistency across the application tier. - FSx provides built-in redundancy and automatic failover, meeting the high availability requirement. **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:** 1. **Separation of concerns:** Static files (S3 + CloudFront) vs. dynamic code (FSx) 2. **Platform compatibility:** Using Windows-compatible services (FSx) for Windows workloads 3. **High availability:** Both S3 and FSx provide built-in redundancy and durability 4. **Scalability:** S3 scales automatically, and FSx can scale performance and storage independently
Author: LeetQuiz Editorial Team
Ultimate access to all questions.
No comments yet.
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.