AWS Certified Solutions Architect Professional SAP-C02 Practice Question
A financial-services company operates hundreds of microservices in Kubernetes clusters both on-premises and in AWS. The on-premises clusters run on VMware vSphere and must stay in company data centers for regulatory reasons; they can operate in a completely disconnected (air-gapped) mode for short periods. In AWS, the workloads run in a managed Amazon EKS cluster backed by managed node groups.
The architecture team wants to modernize and sets these goals:
Reduce the operational effort of patching and upgrading the on-premises Kubernetes control planes.
Preserve the Kubernetes API and existing Helm charts across environments.
Remove EC2 node management for most cloud workloads while gaining pod-level isolation.
View the health of every cluster (cloud and on-premises) in a single AWS console.
Which modernization approach meets all of these requirements with the LEAST ongoing infrastructure management?
Install AWS Outposts racks in each data center and run Amazon EKS on Outposts while continuing to use managed node groups in the AWS Region.
Replace all clusters with self-managed Kubernetes on Amazon EC2 Auto Scaling groups and on-premises servers, instrumented with the CloudWatch agent to provide a common monitoring plane.
Adopt Amazon EKS Anywhere for the on-premises clusters, create Fargate profiles in the existing Amazon EKS cluster, and register every cluster with Amazon EKS Connector for unified visibility.
Deploy Amazon ECS Anywhere on the on-premises servers and migrate the AWS workloads to Amazon ECS running on AWS Fargate, using CloudWatch Container Insights for observability.
Amazon EKS Anywhere lets the company create and maintain on-premises clusters that use the same EKS Distro as the managed service, so the team no longer has to build, patch, or upgrade its own control planes. EKS Anywhere supports installation on vSphere and can run in air-gapped environments, satisfying regulatory and connectivity constraints. In the AWS Region, using EKS Fargate profiles remove the need to provision or patch worker nodes and deliver pod-level isolation. Registering both the on-premises and regional clusters with EKS Connector surfaces every cluster's status in the EKS console for a single-pane-of-glass view.
ECS Anywhere (distractor) would require porting from Kubernetes to ECS and does not keep the Kubernetes API. EKS on Outposts still depends on an always-available service link to an AWS Region for its primary operational model, so it cannot tolerate the stated air-gapped periods as effectively as EKS Anywhere. Continuing with self-managed Kubernetes on EC2 retains all node and control-plane maintenance, failing the "least management" goal.
Ask Bash
Bash is our AI bot, trained to help you pass your exam. AI Generated Content may display inaccurate information, always double-check anything important.
What is Amazon EKS Anywhere and how does it help with on-premises Kubernetes clusters?
Open an interactive chat with Bash
How does using AWS Fargate for Amazon EKS improve workload management in the cloud?
Open an interactive chat with Bash
What is the Amazon EKS Connector and how does it enable unified visibility?
Open an interactive chat with Bash
AWS Certified Solutions Architect Professional SAP-C02
Accelerate Workload Migration and Modernization
Your Score:
Report Issue
Bash, the Crucial Exams Chat Bot
AI Bot
Loading...
Loading...
Loading...
IT & Cybersecurity Package Join Premium for Full Access