Home / networking / AWS Certified Advanced Networking - Specialty (ANS-C01) / Cheat Sheet
AWS Certified Advanced Networking - Specialty (ANS-C01)

ANS-C01 Cheat Sheet

ANS-C01 Tests Hybrid Routing and DNS Design Under Constraints — Not VPC Basics

ANS-C01 is retiring: the last test date is 31 December 2026, and no successor exam has been announced. It suits engineers who design multi-account, hybrid AWS networks and think in BGP, DNS and route tables.

Check Your Readiness →
Among the harder certs
Avg: Not published by Amazon Web Services
Pass: 750 / 1000
Most candidates understand AWS Certified Advanced Networking - Specialty (ANS-C01) concepts — and still fail. This exam tests how you apply knowledge under pressure.

ANS-C01 Domain Map (final months before retirement)

Long scenarios where several designs work; you rank them on latency, static IPs, transitive routing, resilience and cost. Expect multiple-response items asking for two parts of one design, and precise settings such as appliance mode, VIF types and route propagation.

  1. 01
    Network Design (30%) — edge services, multi-VPC and hybrid topologies, DNS architecture, load balancer selection
  2. 02
    Network Implementation (26%) — Direct Connect VIFs and gateways, Transit Gateway routing, Route 53 Resolver, automation
  3. 03
    Network Management and Operation (20%) — Reachability Analyzer, Flow Logs, MTU and BGP troubleshooting, cost tuning
  4. 04
    Network Security, Compliance and Governance (24%) — security groups vs. NACLs, Network Firewall, WAF placement, encryption

Wrong instinct vs correct approach

A gaming company needs two static IPs worldwide and sub-minute failover between Regions for UDP traffic
✕ Wrong instinct

Route 53 failover routing with health checks

✓ Correct approach

Clients cache DNS answers for the TTL, so DNS failover lags. Global Accelerator gives two static anycast IPs, supports TCP and UDP, and shifts traffic to healthy endpoints within seconds. CloudFront serves HTTP and HTTPS only.

Third-party firewall appliances must inspect all traffic transparently while keeping flows symmetric
✕ Wrong instinct

Put a Network Load Balancer in front of the appliance fleet

✓ Correct approach

Gateway Load Balancer encapsulates traffic with GENEVE on port 6081, keeps each flow on the same appliance, and is reached through Gateway Load Balancer endpoints in route tables. An NLB cannot act as a transparent bump in the wire.

SSH sessions over Direct Connect work but large file copies hang partway through
✕ Wrong instinct

Move the instances to a larger instance type

✓ Correct approach

Small packets passing while large ones stall points to an MTU mismatch with ICMP blocked, which breaks path MTU discovery. Align MTU end to end and allow the ICMP 'fragmentation needed' messages.

Two VPCs owned by different business units both use 10.0.0.0/16 and one service must be shared
✕ Wrong instinct

Peer the VPCs or attach both to a Transit Gateway

✓ Correct approach

Peering and Transit Gateway cannot route between overlapping ranges. Publish the service behind a Network Load Balancer as an AWS PrivateLink endpoint service; consumers reach it through an interface endpoint, so the CIDRs never meet.

BGP on a private VIF went idle right after the on-premises team advertised more routes
✕ Wrong instinct

Open a support case for a faulty circuit

✓ Correct approach

A private VIF accepts up to 100 prefixes from on premises; exceeding the quota idles the BGP session while the physical link stays up. Summarize the advertised routes back under the quota.

Know these cold

  • ▸ VPC peering is non-transitive; Transit Gateway routes transitively and segments with route tables
  • ▸ Transit Gateway peering attachments take static routes only; propagation does not cross them
  • ▸ VGW cannot ECMP across VPN connections; Transit Gateway with ECMP aggregates VPN bandwidth
  • ▸ Inbound Resolver endpoint — n premises resolves AWS names. Outbound endpoint: VPCs resolve corporate names
  • ▸ Jumbo frames — 001 MTU on private VIFs and 8500 on transit VIFs; VPN never carries them
  • ▸ Reachability Analyzer checks configuration without sending packets and names the blocking component
  • ▸ Need packet payloads for an IDS? Use Traffic Mirroring; Flow Logs hold metadata only
  • ▸ Security groups are stateful and allow-only; network ACLs are stateless with ordered allow and deny
  • ▸ AWS WAF attaches to ALB, CloudFront, API Gateway and AppSync, never to an NLB
  • ▸ Filter egress by domain name with AWS Network Firewall; security groups only match IP ranges

Can you answer these without checking your notes?

In this scenario: "A gaming company needs two static IPs worldwide and sub-minute failover between Regions for UDP traffic" — what should you do first?
Clients cache DNS answers for the TTL, so DNS failover lags. Global Accelerator gives two static anycast IPs, supports TCP and UDP, and shifts traffic to healthy endpoints within seconds. CloudFront serves HTTP and HTTPS only.
In this scenario: "Third-party firewall appliances must inspect all traffic transparently while keeping flows symmetric" — what should you do first?
Gateway Load Balancer encapsulates traffic with GENEVE on port 6081, keeps each flow on the same appliance, and is reached through Gateway Load Balancer endpoints in route tables. An NLB cannot act as a transparent bump in the wire.
In this scenario: "SSH sessions over Direct Connect work but large file copies hang partway through" — what should you do first?
Small packets passing while large ones stall points to an MTU mismatch with ICMP blocked, which breaks path MTU discovery. Align MTU end to end and allow the ICMP 'fragmentation needed' messages.

Common Exam Mistakes — What candidates get wrong

Expecting a Direct Connect gateway to route traffic between attached VPCs

A Direct Connect gateway links on-premises networks to VPCs but never routes VPC to VPC. Associate it with a Transit Gateway over a transit VIF when many VPCs need both hybrid access and inter-VPC routing.

Forgetting appliance mode on the Transit Gateway inspection VPC attachment

Without appliance mode, return traffic can land in a different Availability Zone than the request, and a stateful firewall drops it. Adding firewall capacity does not help; enable appliance mode on the inspection VPC attachment.

Assuming Direct Connect traffic is encrypted because the circuit is private

Direct Connect has no encryption by default. Use MACsec on supported dedicated connections for link-layer encryption, or run IPsec Site-to-Site VPN over the connection for end-to-end encryption, accepting lower throughput per tunnel.

Relying on AS_PATH prepending to steer AWS-to-on-premises traffic across two links

Tag advertised prefixes with local preference communities: 7224:7300 is highest preference, 7224:7100 lowest. AWS evaluates local preference before AS_PATH length, so prepending alone loses when the question asks how AWS picks a Direct Connect link.

Adding another forwarding rule when one subdomain must resolve inside AWS

Resolver forwarding rules cover a domain and its subdomains. When the parent forwards to corporate DNS but one subdomain is a private hosted zone, add a system rule for it. Inbound endpoints serve on-premises clients; outbound endpoints forward from VPCs.

Resources to help you pass AWS Advanced Networking - Specialty on your first attempt

ANS-C01 retires on 31 December 2026. Check your hybrid routing and DNS readiness before you book.