Free Amazon ANS-C01 Actual Exam Questions - Question 2 Discussion
multiple VPCs that are connected to a transit gateway. The transit gateway connects to an on-
premises data center through an AWS Direct Connect gateway and a pair of redundant Direct
Connect connections that use transit VIFs. The company must receive notification each time a new
route is advertised to AWS from on premises over Direct Connect.
What should a network engineer do to meet these requirements?
CloudWatch Logs on transit VIFs sounds right for tracking route changes, so D.
A, since CloudWatch metrics on Direct Connect can directly monitor route changes without extra setup.
Option B also makes sense because Transit Gateway Network Manager is designed to give a holistic view of network routing across all connected VPCs and on-prem links. It can detect route changes from the Direct Connect gateway and push these events to EventBridge, which can then trigger notifications. This approach avoids custom polling or log parsing and gives centralized monitoring, especially useful if you want to track changes across multiple transit gateways or Direct Connect connections in one place. Plus, it’s native AWS tooling designed for this kind of network visibility.
I’m wondering if option B could also work since Transit Gateway Network Manager tracks route changes and integrates with EventBridge for notifications. Wouldn’t that provide a more centralized way to monitor across VPCs?
Maybe D here too. The transit VIF is the actual point where routes come in from on-prem, so enabling CloudWatch Logs on it makes sense to catch any changes quickly. Options A and B don’t seem to provide direct visibility into route advertisements—CloudWatch metrics or Transit Gateway Network Manager are more about overall monitoring, not specific route updates. C feels too manual and laggy since polling routes periodically isn’t real-time enough. D’s metric filters and alarms can automate notifications efficiently as soon as a new route shows up.
It’s D for me. Enabling CloudWatch Logs on the transit VIFs sounds like the right way to track new routes since the VIF is what actually receives the routes from on-prem. The rest don’t seem to handle route changes directly or depend on checking routes indirectly, which could miss timely notifications. But I feel like the question could use a bit more detail on how to set up the metric filter properly for route changes-does anyone have a clearer explanation?