SAA-C03 Question #559: Real Exam Question with Answer & Explanation

Question

A company runs a containerized application on a Kubernetes cluster in an on-premises data center. The company is using a MongoDB database for data storage. The company wants to migrate some of these environments to AWS, but no code changes or deployment method changes are possible at this time. The company needs a solution that minimizes operational overhead. Which solution will meet this requirement?

Options

• AUse Amazon Elastic Container Service (Amazon ECS) with Amazon EC2 worker nodes for
• BUse Amazon Elastic Container Service (Amazon ECS) with AWS Fargate for compute and
• CUse Amazon Elastic Kubernetes Service (Amazon EKS) with Amazon EC2 worker nodes for
• DUse Amazon Elastic Kubernetes Service (Amazon EKS) with AWS Fargate for compute and

Explanation

EKS lets teams "run Kubernetes on AWS without needing to install and operate your own Kubernetes control plane," and with AWS Fargate, you "run Kubernetes pods without managing servers," reducing operational overhead for worker nodes. For the data layer, Amazon DocumentDB (with MongoDB compatibility) "supports the MongoDB API and drivers," allowing existing MongoDB applications to work without application changes, while the service "automatically scales storage," provides "high availability across multiple Availability Zones," automatic backups, and patching. Because the company cannot change code or deployment methods, keeping Kubernetes (EKS) and the MongoDB API (DocumentDB compatibility) is essential. Options A and C either change the orchestrator (to ECS) or the database API (to DynamoDB), which would require code/deployment changes. Option A also leaves you managing EC2 nodes and a self-managed MongoDB on EC2, increasing ops burden. Therefore, EKS on Fargate + Amazon DocumentDB minimizes operations and preserves compatibility.

No community discussion yet for this question.