
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 runs its infrastructure on AWS and has a registered base of 700,000 users for its document management application. The company intends to create a product that converts large .pdf files to .jpg image files. The .pdf files average 5 MB in size. The company needs to store the original files and the converted files. A solutions architect must design a scalable solution to accommodate demand that will grow rapidly over time.
Which solution meets these requirements MOST cost-effectively?
A
Save the .pdf files to Amazon S3. Configure an S3 PUT event to invoke an AWS Lambda function to convert the files to .jpg format and store them back in Amazon S3.
B
Save the .pdf files to Amazon DynamoDB using the DynamoDB Streams feature to invoke an AWS Lambda function to convert the files to .jpg format and store them back in DynamoDB.
C
Upload the .pdf files to an AWS Elastic Beanstalk application that includes Amazon EC2 instances, Amazon Elastic Block Store (Amazon EBS) storage, and an Auto Scaling group. Use a program in the EC2 instances to convert the files to .jpg format. Save the .pdf files and the .jpg files in the EBS store.
D
Upload the .pdf files to an AWS Elastic Beanstalk application that includes Amazon EC2 instances, Amazon Elastic File System (Amazon EFS) storage, and an Auto Scaling group. Use a program in the EC2 instances to convert the file to .jpg format. Save the .pdf files and the .jpg files in the EBS store.
Explanation:
Option A is the most cost-effective solution because:
Why other options are less cost-effective:
Option B (DynamoDB): DynamoDB is a NoSQL database optimized for key-value access, not for storing large binary files. It would be extremely expensive to store 5MB files in DynamoDB compared to S3.
Option C (Elastic Beanstalk with EBS): Requires provisioning and managing EC2 instances, which means paying for compute capacity even during idle periods. EBS storage is more expensive than S3 for this use case, and scaling requires managing Auto Scaling groups.
Option D (Elastic Beanstalk with EFS): Similar to Option C but with EFS, which is a shared file system. While EFS allows multiple EC2 instances to access the same files, it's more expensive than S3 and still requires EC2 instances to be running.
Key AWS Services Used:
This solution aligns with AWS best practices for cost optimization by leveraging serverless services that scale automatically and only incur costs when actually processing files.