Which AWS storage and database architecture meets the requirements of the application?
Web servers: store read-only data in S3, and copy from S3 to root volume at boot time. App servers: share state using a combination of DynamoDB and IP unicast. Database: use RDS with multi-AZ deployment and one or more read replicas. Backup: web servers, app servers, and database backed up weekly to Glacier using snapshots.
Web servers: store read-only data in an EC2 NFS server, mount to each web server at boot time. App servers: share state using a combination of DynamoDB and IP multicast. Database: use RDS with multi- AZ deployment and one or more Read Replicas. Backup: web and app servers backed up weekly via AMIs, database backed up via DB snapshots.
Web servers: store read-only data in S3, and copy from S3 to root volume at boot time. App servers: share state using a combination of DynamoDB and IP unicast. Database: use RDS with multi-AZ deployment and one or more Read Replicas. Backup: web and app servers backed up weekly via AMIs, database backed up via DB snapshots.
Web servers: store read-only data in S3, and copy from S3 to root volume at boot time App servers: share state using a combination of DynamoDB and IP unicast. Database: use RDS with multi-AZ deployment. Backup: web and app servers backed up weekly via AMIs, database backed up via DB snapshots.
Explanations:
While S3 is suitable for storing read-only data and RDS with multi-AZ and read replicas provides good database scalability, using IP unicast for app server state sharing does not align with the previous multicast dependency. Additionally, Glacier is not an ideal choice for weekly backups compared to snapshots.
Using an EC2 NFS server does not eliminate reliance on a shared storage model, which is not optimal in a cloud environment. IP multicast is also not supported in AWS, making the solution flawed. While RDS is appropriately used, the overall architecture does not meet the requirements.
This option correctly utilizes S3 for read-only data storage, which is scalable and eliminates the need for a distributed file system. Using DynamoDB with IP unicast is a suitable alternative for shared state, and RDS with multi-AZ deployment and read replicas ensures high availability and scalability. Weekly backups via AMIs and snapshots provide comprehensive data protection.
While S3 is correctly used for read-only data, this option lacks read replicas, limiting the database’s scalability and failover capabilities. The use of AMIs for web and app servers does not provide the same level of granularity and flexibility as snapshots, making this option less robust.