AWS Network Manager for Inter-Region Latency Monitoring
Short answer
B Set up AWS Network Manager Infrastructure Performance. Publish network performance metrics to Amazon CloudWatch.
Question
Key Takeaways
The exam tests knowledge of AWS Network Manager's specific capability to publish infrastructure performance metrics (like latency) to CloudWatch, which retains data for historical analysis, unlike real-time-only tools.
This question tests the use of AWS Network Manager Infrastructure Performance to monitor and measure latency between AWS Regions. The community consensus confirms that this service is the correct solution for gathering historical network performance metrics over a 30-day period.
Common mistake: Candidates often choose VPC Flow Logs or Reachability Analyzer because they are more commonly discussed. However, Flow Logs track packet metadata for security/auditing, not performance latency, and Reachability Analyzer is a diagnostic tool for single paths, not a continuous metric collector.
Expert Analysis
Why the Answer Is Correct
AWS Network Manager provides a centralized view of your network infrastructure. Its 'Infrastructure Performance' feature specifically monitors key metrics such as latency, jitter, and packet loss between endpoints across regions. By publishing these metrics to Amazon CloudWatch, it allows you to query historical data, satisfying the requirement to analyze at least the previous 30 days.
Why the Other Options Are Wrong
Option A is incorrect because Network Access Analyzer focuses on security policies and resource accessibility, not performance latency. Option C, Reachability Analyzer, is designed for diagnosing connectivity issues along a specific path at a point in time; it does not provide continuous historical metric collection. Option D, VPC Flow Logs, captures IP traffic flow information for auditing and security purposes and does not natively collect latency or performance metrics.
Community Comment Notes
Comment [1] highlights that AWS Network Manager is a built-in, minimal-effort solution for inter-region latency measurement. Comment [3] reinforces that the requirement to analyze historical data aligns perfectly with CloudWatch integration via Network Manager.
Exam Strategy
Distinguish between security/auditing tools (Flow Logs, Access Analyzer) and performance monitoring tools. When a question asks for 'latency,' 'jitter,' or 'historical performance metrics' over a long period, look for AWS Network Manager or CloudWatch Synthetics rather than basic logging services.
Community Votes
100% of anonymous learners picked answer B. 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
-
ashk123456 👍 1 Answered B✅ AWS Network Manager Infrastructure Performance can monitor and log latency metrics between Regions. ✅ It publishes network performance data to CloudWatch, allowing historical analysis for at least 30 days. ✅ Minimal setup effort, built-in AWS solution for inter-region latency measurement.
-
Sudeepshiv 👍 1 Answered BThe company needs to: Measure latency between AWS Regions before expanding. Analyze historical latency data for the past 30 days. AWS Network Manager Infrastructure Performance is designed for this use case.
-
Franck12az31 👍 1 Answered BAWS Network Manager Infrastructure Performance allows latency monitor between AWS region and can gather metrics to 30 days.
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 →