A company is migrating legacy internal applications to AWS and is redesigning its internal employee directory with native AWS services. You must store employee contact details plus high-resolution photos and allow searching and retrieval of each employee's details and photos via AWS APIs. Which design accomplishes this?

Storing employee contact information in Amazon DynamoDB and high-resolution photos in Amazon S3 is the most suitable and cost-effective solution. DynamoDB provides fast, scalable NoSQL access for structured contact details, while S3 is ideal for storing large, unstructured objects like high-resolution images. Storing S3 object keys in DynamoDB links the contact information to the corresponding photos. Encoding photos in Base64 and storing them directly in DynamoDB is inefficient and expensive, as DynamoDB is not optimized for large binary objects and has item size limits. Amazon Cognito user pools are for identity management and authentication, not for general data storage of employee directories and photos. Amazon RDS with Amazon EFS is a viable option for some use cases, but DynamoDB and S3 offer better scalability and cost-effectiveness for this specific requirement of structured data and large objects, aligning with native AWS service best practices.