Amazon Web Services Updated SAA-C03 Exam Questions and Answers by ryder

For a large-scale multi-account AWS environment with many VPCs and centralized Direct Connect, AWS recommends using a Transit Gateway (TGW) architecture combined with a Direct Connect gateway (DXGW). This setup allows scalable, centralized connectivity between on-premises and multiple VPCs across accounts.

Step B: Creating a Direct Connect gateway and Transit Gateway in a central network account and connecting them via a transit VIF enables the on-premises network to access all connected VPCs.

Step D: Sharing the transit gateway with other accounts via AWS Resource Access Manager (RAM) allows the central TGW to attach VPCs in multiple accounts, simplifying multi-account connectivity.

Step F: To route cloud resources’ internet traffic back through the on-premises data center (for centralized egress), provisioning only private subnets and routing outbound internet traffic through NAT or firewall services in the data center is necessary. This requires configuring transit gateway and customer gateway routes appropriately.

Option A is partially correct in the use of Direct Connect gateway but association proposals are not scalable for hundreds of VPCs and accounts compared to transit gateway. Option C (internet gateway) is irrelevant here as traffic egress is required via on-premises data center, not directly to the internet. Option E (VPC peering) is not scalable for hundreds of VPCs.

AWS Fargate is a serverless compute engine for containers that works with Amazon EKS. With Fargate, you do not need to provision or manage EC2 instances or clusters. You simply define and deploy your pods, and Fargate automatically launches the required compute resources. This results in the lowest operational overhead because AWS manages the infrastructure. Fargate profiles allow you to specify which pods run on Fargate.

AWS Documentation Extract:

“AWS Fargate is a serverless, pay-as-you-go compute engine that lets you focus on building applications without managing servers. With Amazon EKS and Fargate, you only need to define your application’s pods; Fargate provisions and manages the required compute resources for you.”

(Source: Amazon EKS documentation, AWS Fargate integration)

Other options:

A: Self-managed nodes require you to manage EC2 instances.

B: Managed node groups reduce some overhead, but you are still responsible for patching and managing the EC2 instances.

D: Managed node groups with Karpenter automate scaling but do not remove the need to manage underlying instances.

Provisioned concurrency is the key requirement match because AWS documentation states that it pre-initializes Lambda execution environments and is designed to reduce cold-start latency, supporting predictable response times in the double-digit millisecond range. That makes it ideal for APIs that must remain consistently low-latency during peak traffic periods. Reserved concurrency does not solve cold starts; it only reserves capacity. ECS and EKS could certainly host the API, but both introduce more infrastructure management than API Gateway plus Lambda. Since the question asks for theleast operational overheadwhile maintaining consistent low latency, the serverless pattern with API Gateway and Lambdawith provisioned concurrencyis the strongest AWS-native answer. (AWS Documentation)

============

The requirement is for astructured relational databasewith backups and scalable managed operations. Amazon RDS is the natural fit because it provides a managed relational database platform, and AWS documents that General Purpose SSD is recommended for new storage needs. AWS also documents that automated backups are enabled through the backup retention period parameter. Compared with self-managed EC2 databases, RDS reduces operational burden significantly. Aurora Serverless can be attractive, but for a general-purpose new application, standard RDS with GP SSD and automated backups is the more straightforward cost-conscious choice among the listed answers. Therefore, RDS with GP SSD storage and automated backups is the best match.