SaveMyCert
Log in
5 of 5 free questions left today·for 10 a day
SOA-C03 · Domain 5

Networking and Content Delivery practice questions

Networking and Content Delivery is worth 18% of the SOA-C03 exam — the 4th-heaviest of the 5 domains. VPC networking and private connectivity, DNS and content delivery, and troubleshooting with flow logs and network monitoring. 6 fully worked examples are further down this page, answers included.

Exam weight
18%
the 4th-heaviest of the 5 domains
Questions
93
across 3 topics
Free, no account
5/day
a free account allows 10 a day
Explanations
Every option
right and wrong

Build a practice session

5 free questions left today.

Domains

How many?

5 free questions left today.

Mode

Ready when you are

10 fresh questions drawn across 1 of 5 domains, in Learn mode.

Review what you missed

Every question you answer incorrectly, and every question you flag while practising, is saved here automatically. Finish a session and you can come back to re-drill just those.

6 sample Networking and Content Delivery questions, fully explained

Questions from the SOA-C03 bank mapped to domain 5, with the answer key and the reasoning behind every option. None of them repeat the examples on the main SOA-C03 practice page.

Question 1Networking and Content Delivery

An operations team runs IPv6-enabled EC2 instances in private subnets that must download packages from internet repositories over IPv6. The security policy requires that no connection can be initiated from the internet to these instances. What should the team configure?

Choose one.

  • a
    Create an egress-only internet gateway and route ::/0 to it Correct

    An egress-only internet gateway is stateful and allows outbound-initiated IPv6 connections and their replies while blocking all inbound-initiated traffic — exactly the outbound-only IPv6 requirement.

  • b
    Route ::/0 to a NAT gateway in a public subnet

    A NAT gateway does not give IPv6 instances general IPv6 internet egress. Its only IPv6 role is NAT64 (with DNS64), which translates traffic to IPv4 destinations through a 64:ff9b::/96 route, not a ::/0 route to IPv6 repositories.

  • c
    Route ::/0 to the VPC's internet gateway

    An internet gateway allows inbound-initiated connections to the instances' publicly routable IPv6 addresses, violating the policy.

  • d
    Create a gateway VPC endpoint for the package repositories

    Gateway endpoints support only Amazon S3 and DynamoDB; they cannot provide general outbound access to internet repositories.

The concept

VPC IPv6 addresses are globally unique and publicly routable, so there is no NAT for IPv6-to-IPv6 traffic. The egress-only internet gateway is the IPv6 construct for outbound-only access: instances can initiate connections out, and inbound-initiated traffic is blocked.

Why that’s the answer

Routing ::/0 to an egress-only internet gateway gives the instances outbound IPv6 access while its stateful behavior blocks anything the internet initiates. A NAT gateway is wrong because its IPv6 support is limited to NAT64 translation toward IPv4 destinations; a standard internet gateway is wrong because it accepts inbound connections to the publicly routable IPv6 addresses; and a gateway endpoint only reaches S3 and DynamoDB, not internet repositories.

How to reason it out
  1. Create an egress-only internet gateway and attach it to the VPC.
  2. In the private subnets' route tables, add a route sending ::/0 to the egress-only internet gateway.
  3. Verify security groups and NACLs permit the outbound traffic and (for NACLs) the ephemeral-port return traffic.
  4. Confirm instances can reach the repositories while inbound IPv6 connection attempts fail.

Exam tip: "IPv6, outbound only" maps to an egress-only internet gateway; a NAT gateway's NAT64 only helps IPv6 hosts reach IPv4 destinations.

VPC Networking and Private Connectivity for SOA-C03 — the lesson that teaches this.

Question 2Networking and Content Delivery

EC2 instances in private subnets upload hundreds of gigabytes of objects to Amazon S3 every day through a NAT gateway, and the NAT data-processing charge is now the largest line on the VPC bill. The company wants this traffic to stay off the public internet at no additional data-processing cost. What should a CloudOps engineer do?

Choose one.

  • a
    Create an interface VPC endpoint for Amazon S3 in each private subnet's Availability Zone

    An interface endpoint keeps the traffic private, but it bills per endpoint-hour in each AZ plus a per-GB data-processing charge, which breaks the no-additional-cost requirement.

  • b
    Create a gateway VPC endpoint for Amazon S3 and add it to the private subnets' route tables Correct

    A gateway endpoint for S3 has no hourly or data-processing charge. AWS adds a prefix-list route to the selected route tables, which is more specific than 0.0.0.0/0, so S3 traffic bypasses the NAT gateway and stays on the AWS network.

  • c
    Replace the NAT gateway with a NAT instance in a public subnet sized for the daily volume

    A NAT instance removes the NAT gateway processing fee but still sends the uploads to S3's public endpoints through the internet gateway, and it adds instance cost and patching work.

  • d
    Enable S3 Transfer Acceleration on the buckets and switch the private subnets' uploads to it

    Transfer Acceleration speeds long-distance uploads through CloudFront edge locations, adds a per-GB charge, and still needs an internet path from the private subnets.

The concept

A gateway VPC endpoint gives resources in a VPC private access to Amazon S3 (or DynamoDB) through a route-table entry, with no hourly or data-processing charge.

Why that’s the answer

The requirement combines privacy and zero added cost. The gateway endpoint inserts a managed prefix-list route for S3 into the associated route tables; that route is more specific than the default route, so S3 traffic stops flowing through the NAT gateway and its per-GB processing fee disappears. An interface endpoint is also private but charges per hour and per GB. A NAT instance and Transfer Acceleration both keep traffic on the internet path.

How to reason it out
  1. Identify the destination: Amazon S3, one of the two services with gateway endpoints.
  2. Check the cost constraint: gateway endpoints are free; interface endpoints bill hourly and per GB.
  3. Create the gateway endpoint and associate it with every private subnet route table that carries the uploads.
  4. Confirm the prefix-list route appears and the NAT gateway's BytesOutToDestination drops.

Exam tip: Private S3 or DynamoDB access at no added cost is a gateway endpoint associated with the subnets' route tables.

VPC Networking and Private Connectivity for SOA-C03 — the lesson that teaches this.

Question 3Networking and Content Delivery

During a network protection audit, a manager asks a CloudOps engineer what defense the company's public-facing resources (CloudFront, an ALB and Route 53 hosted zones) already have against common layer 3 and layer 4 DDoS attacks such as SYN floods, and what that protection costs. No protection services have been configured. What should the engineer report?

Choose one.

  • a
    AWS Shield Advanced already protects the resources and is included with every account

    Shield Advanced is a paid subscription that you turn on and then apply to specific resources; it is not included by default.

  • b
    The resources have no DDoS protection until an AWS WAF web ACL is associated with each

    WAF is a layer 7 filter you configure; layer 3 and 4 protection from Shield Standard exists without it.

  • c
    The resources are protected once AWS Network Firewall endpoints are deployed in each VPC

    Network Firewall inspects VPC traffic routed through its endpoints. It is not the DDoS layer for CloudFront, Route 53 or ALB traffic.

  • d
    AWS Shield Standard already protects the resources automatically at no additional charge Correct

    Shield Standard is applied automatically to all AWS customers at no extra cost and mitigates common network and transport layer attacks such as SYN floods and UDP reflection.

The concept

AWS Shield has two tiers. Shield Standard is automatic and free for every AWS customer and covers common layer 3 and 4 DDoS attacks. Shield Advanced is a paid subscription applied to chosen resources, adding enhanced detection, the Shield Response Team and DDoS cost protection.

Why that’s the answer

Because nothing was configured, only automatic protections apply, and Shield Standard is the automatic one: it already defends CloudFront, Route 53 and load balancers against SYN floods and reflection attacks at no extra charge. Shield Advanced requires a subscription, WAF filters layer 7 requests only after you associate a web ACL, and Network Firewall protects VPC traffic routed through it rather than providing edge DDoS mitigation.

How to reason it out
  1. Note what has been configured: nothing.
  2. Recall which protection is applied automatically: Shield Standard, at no charge.
  3. Separate it from Shield Advanced (paid, opt-in per resource) and WAF (layer 7, needs a web ACL).
  4. Report Shield Standard for layer 3 and 4 and list Shield Advanced as the upgrade path.

Exam tip: Shield Standard is automatic and free; Shield Advanced is paid and applied per resource.

VPC Networking and Private Connectivity for SOA-C03 — the lesson that teaches this.

Question 4Networking and Content Delivery

A CloudOps engineer creates a custom route table with a route that sends 0.0.0.0/0 to the VPC's internet gateway, then launches EC2 instances with public IPv4 addresses into a newly created subnet. The instances are unreachable from the internet. The VPC's main route table holds only the local route, and the security groups and network ACL allow the traffic. What is the MOST likely cause?

Choose one.

  • a
    The custom route table needs its own local route for the VPC CIDR added

    Every route table, custom or main, gets the local route automatically and it cannot be removed.

  • b
    The internet gateway needs to be attached to the new subnet instead of the VPC

    Internet gateways attach to a VPC, not to subnets. Subnets reach it through a route in their route table.

  • c
    The new subnet is still implicitly associated with the main route table Correct

    A new subnet uses the main route table until you explicitly associate another table. The main table has no internet gateway route, so the instances have no path to the internet.

  • d
    The instances also need an IPv6 ::/0 route added to the custom route table

    An IPv6 default route matters only for IPv6 traffic. It has no effect on inbound IPv4 reachability.

The concept

Each subnet uses exactly one route table. A subnet without an explicit association uses the VPC's main route table, so creating a custom table changes nothing until the subnet is associated with it.

Why that’s the answer

The custom table is correct but unused: the new subnet was never associated with it, so the router applies the main table, which only has the local route. Associating the subnet with the custom table (or adding the IGW route to the main table, which affects every unassociated subnet) fixes it. The local route is automatic, internet gateways attach at the VPC level, and IPv6 egress routes do not affect IPv4 inbound reachability.

How to reason it out
  1. List what makes a subnet public: an IGW route in the subnet's effective route table and public IPs.
  2. Public IPs are present, so check which route table the subnet actually uses.
  3. A subnet with no explicit association uses the main table, which lacks the IGW route.
  4. Associate the subnet with the custom route table.

Exam tip: A new subnet uses the main route table until you explicitly associate it with another one.

VPC Networking and Private Connectivity for SOA-C03 — the lesson that teaches this.

Question 5Networking and Content Delivery

A private subnet's route table in a VPC with CIDR 10.0.0.0/16 contains three routes: the local route for 10.0.0.0/16, a route sending 0.0.0.0/0 to a NAT gateway, and a route sending 172.16.0.0/16 to a VPC peering connection. An instance in the subnet sends a packet to 172.16.40.9. Where does the VPC router deliver it?

Choose one.

  • a
    The NAT gateway, through the 0.0.0.0/0 default route

    0.0.0.0/0 matches every destination, but it is the least specific route. A more specific matching route takes priority.

  • b
    Dropped, as the peering connection and NAT routes overlap

    Overlapping routes are normal. The router picks the longest matching prefix and does not drop the packet.

  • c
    The peering connection, through the 172.16.0.0/16 route Correct

    172.16.40.9 falls inside 172.16.0.0/16, and a /16 is more specific than /0, so the peering route wins.

  • d
    The local target, through the VPC's 10.0.0.0/16 route

    The local route covers only the VPC's own CIDR, 10.0.0.0/16, which does not contain 172.16.40.9.

The concept

When multiple routes in a table match a destination, the VPC router uses the most specific (longest) prefix: a /32 beats a /16, which beats 0.0.0.0/0. The unremovable local route always handles intra-VPC traffic for the VPC's own CIDR.

Why that’s the answer

172.16.40.9 matches both 0.0.0.0/0 and 172.16.0.0/16, and the /16 is more specific, so traffic goes to the peering connection. The default-route answer ignores longest-prefix matching, "dropped" wrongly treats overlap as a conflict, and the local route only covers 10.0.0.0/16.

How to reason it out
  1. List every route whose prefix contains the destination address.
  2. Compare prefix lengths — the longest prefix (largest number after the slash) wins.
  3. Here 172.16.0.0/16 beats 0.0.0.0/0, so the peering connection carries the packet.
  4. Remember the same logic explains why a gateway-endpoint prefix route diverts S3 traffic away from a NAT default route.

Exam tip: VPC routing always picks the most specific matching prefix — the default route only carries what nothing narrower claims.

VPC Networking and Private Connectivity for SOA-C03 — the lesson that teaches this.

Question 6Networking and Content Delivery

A production VPC spans three Availability Zones. Private subnets in all three AZs route 0.0.0.0/0 to a single zonal NAT gateway in AZ A. The operations team must ensure that the failure of any one Availability Zone cannot remove outbound internet access for workloads in the surviving AZs, and it will keep using zonal NAT gateways. What should the team do?

Choose one.

  • a
    Add a second NAT gateway in another public subnet in AZ A and split the private subnets between them

    Both gateways live in AZ A, so an AZ A outage still removes outbound access for every private subnet.

  • b
    Move the NAT gateway into AZ B's public subnet and associate a second Elastic IP address with it

    Moving the gateway only shifts the single point of failure to AZ B. Extra Elastic IPs add connection capacity, not zonal resilience.

  • c
    Create a NAT gateway in each AZ's public subnet and route each private subnet to its own AZ's gateway Correct

    With one zonal NAT gateway per AZ and same-AZ routes, an AZ failure only affects the workloads in that AZ, and traffic no longer crosses AZs to reach the gateway.

  • d
    Create a NAT gateway in each AZ's public subnet and keep each private subnet routed to the AZ A gateway

    The new gateways sit unused because the routes still point at AZ A, so an AZ A failure still cuts outbound access everywhere.

The concept

A zonal NAT gateway runs in one Availability Zone. Its redundancy is within that AZ, so a highly available design places one zonal NAT gateway in each AZ and points each AZ's private route tables at the gateway in the same AZ. A regional NAT gateway is the newer alternative that expands across AZs automatically.

Why that’s the answer

Zonal resilience comes from the routing as much as from the gateways: each AZ needs its own NAT gateway and its private subnets must route to it. Creating the gateways but leaving the routes on AZ A changes nothing, and adding or moving a gateway within a single AZ keeps a single zonal point of failure. Same-AZ routing also avoids cross-AZ data transfer charges. Because the team is staying with zonal gateways here, a regional NAT gateway (created with availability mode regional, no public subnet needed) is not the choice, but it is how AWS now offers multi-AZ NAT in one resource.

How to reason it out
  1. Find the single point of failure: one zonal NAT gateway serving every AZ.
  2. Deploy a zonal NAT gateway with an Elastic IP in a public subnet in each AZ.
  3. Update each AZ's private route table so 0.0.0.0/0 targets the NAT gateway in the same AZ.
  4. Test by checking that each AZ's workloads egress through their local gateway.

Exam tip: Zonal NAT gateways are highly available only as one per AZ with same-AZ routes; a regional NAT gateway does that expansion for you.

VPC Networking and Private Connectivity for SOA-C03 — the lesson that teaches this.

What SOA-C03 domain 5 tests, topic by topic

The official exam guide breaks Networking and Content Delivery into 3 topics. The question bank follows the same split, so a weak topic shows up as a cluster of misses you can go back and read.

Published SOA-C03 practice questions per topic in Networking and Content Delivery
TopicWhat it coversQuestions
Implement and optimize networking features and connectivityExam guide task 5.1. Configuring a VPC — subnets, route tables, network ACLs, security groups, NAT gateways, internet gateway, egress-only internet gateway; private networking connectivity (VPC endpoints, AWS PrivateLink, VPC peering); auditing network protection services (Route 53 Resolver DNS Firewall, WAF, Shield, Network Firewall) in a single account; optimizing network architecture cost.31
Configure domains, DNS services, and content deliveryExam guide task 5.2. Configuring DNS with Route 53 Resolver; Route 53 routing policies, configurations, and query logging; content and service distribution with CloudFront and Global Accelerator.31
Troubleshoot network connectivity issuesExam guide task 5.3. Troubleshooting VPC configurations (subnets, route tables, network ACLs, security groups, transit gateways, NAT gateways); interpreting networking logs (VPC flow logs, ELB access logs, WAF web ACL logs, CloudFront logs, container logs); remediating CloudFront caching issues; troubleshooting hybrid and private connectivity; configuring and analyzing CloudWatch network monitoring.31
Total93

Revise Networking and Content Delivery before you drill it

Other SOA-C03 domains

Networking and Content Delivery: your questions

Networking and Content Delivery is domain 5 of the SOA-C03 exam guide and carries 18% of the scored content — the 4th-heaviest of the 5 domains. On a 65-question paper that works out to roughly 12 questions, though AWS does not publish an exact per-domain count and individual exam forms vary.

Source

The domain weight and topic list on this page come from the official SOA-C03 exam guide.