
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 company's website uses an Amazon EC2 instance store for its catalog of items. The company wants to make sure that the catalog is highly available and that the catalog is stored in a durable location.
What should a solutions architect do to meet these requirements?
A
Move the catalog to Amazon ElastiCache for Redis.
B
Deploy a larger EC2 instance with a larger instance store.
C
Move the catalog from the instance store to Amazon S3 Glacier Deep Archive.
D
Move the catalog to an Amazon Elastic File System (Amazon EFS) file system.
Explanation:
Why D is correct:
Instance Store Limitations: EC2 instance stores are ephemeral storage that is physically attached to the host computer. Data on instance stores is lost when:
Amazon EFS Benefits:
Why other options are incorrect:
A. Amazon ElastiCache for Redis: This is an in-memory data store, not suitable for persistent storage of a catalog. Data in ElastiCache is volatile and can be lost if nodes fail.
B. Deploy a larger EC2 instance with a larger instance store: This doesn't solve the fundamental problem. Instance stores are still ephemeral and not highly available across multiple instances.
C. Amazon S3 Glacier Deep Archive: This is designed for long-term archival storage with retrieval times of 12+ hours, not for active website catalogs that need immediate access.
Key AWS Concepts:
Best Practice: For shared, highly available, and durable storage that needs to be accessed by multiple EC2 instances, Amazon EFS is the appropriate AWS service.