Q17 — AWS DVA-C02 Ch.2

Question 17 of 100 | ← Chapter 2

A company is migrating its legacy human resources application to AWS. Leadership wants to rebuild the employee directory using native AWS services. A developer needs to design a solution to store employees’ contact information and high-resolution photos for use by the new application. Which solution supports searching and retrieving individual employee details and photos using AWS APIs?

• A. Base64-encode each employee’s contact information and photo. Store the information in an Amazon DynamoDB table using a sort key.
• B. Store each employee’s contact information in an Amazon DynamoDB table, along with the object key of the corresponding photo stored in Amazon S3. ✓
• C. Use Amazon Cognito user pools to implement the employee directory as a fully managed Software-as-a-Service (SaaS) solution.
• D. Store employee contact information in an Amazon RDS DB instance and store photos in Amazon Elastic File System (Amazon EFS).

Correct Answer: B. Store each employee’s contact information in an Amazon DynamoDB table, along with the object key of the corresponding photo stored in Amazon S3.

Explanation

Option B is the most appropriate solution. It stores structured contact information in Amazon DynamoDB for fast, scalable querying and retrieval, while storing large binary objects (photos) in Amazon S3 — the optimal service for object storage — and referencing them via object keys. This architecture balances performance, cost, and scalability. Option A encodes photos into Base64, increasing DynamoDB item size and cost, degrading performance, and limiting search flexibility. Option C is designed for authentication and authorization, not for general-purpose employee directory storage and retrieval. Option D introduces unnecessary complexity, higher cost, and lower scalability compared to the DynamoDB+S3 pattern.