How to Fix Inter-Region Traffic Through Inspection VPC in Transit Gateway?
Short answer
D Enable Appliance mode on both the transit gateway attachments for the inspection VPC.
Question
Key Takeaways
This question tests your understanding of Transit Gateway Appliance Mode and asymmetric routing pitfalls when using AWS Network Firewall; the trap is that simply recognizing asymmetric routing (option C) is not enough—you must know the exact configuration setting that forces symmetric inspection.
When inter-Region traffic fails in a Transit Gateway hub-and-spoke architecture with AWS Network Firewall inspection VPCs, enabling Appliance Mode on the Transit Gateway attachments is the correct fix. The AWS community unanimously confirms this solution, which ensures symmetric traffic flow through the originating inspection VPC.
Common mistake: Selecting option C, 'Prevent asymmetric routing in the inspection VPCs,' because it correctly identifies the root cause but fails to provide the actionable Transit Gateway configuration needed. Option C describes the desired outcome, not the mechanism, while Appliance Mode is the specific feature that resolves it.
Expert Analysis
Why the Answer Is Correct
Option D is correct because AWS Transit Gateway's default routing can send each flow across different attachments, causing asymmetric paths. Enabling Appliance Mode on both inspection VPC attachments forces the Transit Gateway to pin each bidirectional flow to a single attachment, ensuring request and response traffic traverse the same Network Firewall inspection VPC. This is exactly what is needed when inter-Region traffic must be inspected in the originating Region, as stated in the question.
Why the Other Options Are Wrong
Option A is invalid because Transit Gateway does not support OSPF dynamic routing; it uses static routes and BGP only in Direct Connect/VPN contexts. Option B is incorrect because AWS RAM is for sharing Transit Gateways across accounts, not for enabling inter-Region connectivity or fixing routing. Option C identifies the symptom but offers no specific configuration; it fails to mention Appliance Mode, which is the actual solution required.
Community Comment Notes
Community comments strongly support D. One commenter notes that OSPF is unsupported on TGW, making A wrong. Another explains that Appliance Mode must be enabled on both inspection VPC attachments in both Regions, and explicitly advises enabling it to 'resolve the asymmetric routing issue and enable inter-Region communication.' A third comment clarifies that default optimized routing can lead to asymmetric paths, which is precisely why Appliance Mode is necessary.
Official Reference
- https://docs.aws.amazon.com/vpc/latest/tgw/tgw-appliance-mode.html
- https://docs.aws.amazon.com/vpc/latest/tgw/transit-gateway-peering.html
- https://docs.aws.amazon.com/network-firewall/latest/developerguide/architectures.html
These links open the official vendor documentation in a new tab.
Exam Strategy
For ANS-C01, always match the described behavior with the exact AWS feature—when you see asymmetric routing in an inspection VPC scenario, immediately look for 'Appliance Mode' in the options. Remember that AWS Transit Gateway does not use OSPF, and AWS RAM only shares resources across accounts, so eliminate those distractors first.
Community Votes
100% of anonymous learners picked answer D. Votes are pick records left by other test-takers — they are not the verified answer.
Discussion 3 contributions
Compiled from public community threads and reader submissions, lightly edited for clarity. Handles and vote tallies are shown as recorded, and comments reflect the views of individual contributors.
From public community threads 3
-
woorkim 👍 2D is correct! A (Configure OSPF routing): AWS Transit Gateway does not support dynamic routing protocols like OSPF. Instead, it uses static routes or BGP for route propagation in Direct Connect scenarios. B (Use AWS RAM to share access): AWS RAM is used to share transit gateways across accounts, not for enabling inter-Region communication or fixing routing issues. C (Prevent asymmetric routing in the inspection VPCs): While preventing asymmetric routing is important, the root cause here is the lack of appliance mode. Simply ensuring symmetry without enabling appliance mode will not resolve the issue.
-
kowal_001 👍 2 Answered DEnable Appliance Mode on the transit gateway attachments for both inspection VPCs in the us-east-1 and eu-west-1 Regions. This ensures that bidirectional traffic passes through the same inspection VPC, resolving the asymmetric routing issue and enabling inter-Region communication.
-
ashk123456 👍 1 Answered DIn a hub-and-spoke architecture using AWS Transit Gateway, when traffic is routed to an inspection VPC (which contains AWS Network Firewall), the traffic path must remain symmetric—meaning that both request and response traffic must pass through the same inspection VPC. By default, AWS Transit Gateway performs packet routing optimally, which can sometimes lead to asymmetric routing issues when using an inspection VPC.
Reader comments & corrections
No reader corrections yet — spotted an error or have a note? Share it below.
Related Analysis
Practice All ANS-C01 Questions
Access 137 questions with complete answers and detailed explanations.
View Full ANS-C01 Practice Test →