SAA-C03 Design Cost-Optimized Architectures Practice Question

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

• ✗

  Deploy a NAT Gateway in each VPC.

  Why it's wrong here

  NAT Gateways carry an hourly charge per gateway and a data processing fee per GB. While they allow access to S3 via the internet, they are significantly more expensive than using a Gateway Endpoint, which provides the same connectivity for free and without the per-GB processing costs.

• ✗

  Create an S3 Interface Endpoint (PrivateLink) in each VPC.

  Why it's wrong here

  Interface Endpoints (AWS PrivateLink) charge an hourly fee for each Availability Zone where they are deployed, plus a data processing fee per GB. While useful for accessing S3 from on-premises or across regions, they are more expensive than Gateway Endpoints for standard VPC-to-S3 connectivity within a region.

• ✗

  Establish a AWS Direct Connect connection to S3.

  Why it's wrong here

  Direct Connect is a high-cost physical connection between an on-premises data center and AWS. It is not a cost-effective solution for intra-region VPC-to-S3 traffic, as it involves significant setup costs, monthly port fees, and is designed for hybrid cloud connectivity rather than internal AWS traffic.

• ✓

  Create an S3 Gateway Endpoint in each VPC.

  Why this is correct

  S3 Gateway Endpoints are a free feature of VPCs. They require no management of hardware or software and do not charge for the amount of data processed. By updating the route table to point S3 traffic to the endpoint, the company eliminates data transfer costs to the internet.