A company has a Direct Connect connection with a private VIF to a VPC. The on-premises network uses BGP to advertise its prefixes. Recently, the on-premises router started advertising a more specific route (10.0.0.0/24) that overlaps with the VPC's CIDR (10.0.0.0/16). What is the impact on traffic destined to 10.0.0.5?
More specific route is preferred.
Why this answer
When an on-premises router advertises a more specific route (10.0.0.0/24) via BGP over a Direct Connect private VIF, the VPC propagates this route into its route tables. For traffic destined to 10.0.0.5, the VPC now has a more specific route (10.0.0.0/24) pointing to the virtual private gateway (VGW), overriding the local VPC route (10.0.0.0/16). This causes return traffic from the instance to on-premises to be routed through Direct Connect instead of staying within the VPC, as the VPC's route table prefers the longest prefix match.
Exam trap
The ANS-C01 exam often tests the misconception that a more specific BGP route will cause the instance to become unreachable or blackholed, but the actual impact is asymmetric routing where return traffic is forced out through Direct Connect.
How to eliminate wrong answers
Option A is wrong because the instance remains reachable from on-premises; the on-premises router can still send traffic to 10.0.0.5 via the Direct Connect connection, and the VPC will forward it locally. Option C is wrong because traffic is not blackholed; the more specific route directs traffic to the VGW, which forwards it to the on-premises network, so packets are not dropped. Option D is wrong because there is no load-balancing; the VPC route table selects a single path based on the longest prefix match, and the more specific route (10.0.0.0/24) takes precedence over the local VPC route (10.0.0.0/16).