Q1 — AWS SAA-C03 Ch.16

Question 1 of 100 | ← Chapter 16

Q1201. A company has set up hybrid connectivity between an on-premises data center and AWS by using AWS Site-to-Site VPN. The company is migrating a workload to AWS.The company sets up a VPC that has two public subnets and two private subnets.The company wants to monitor the total packet loss and round-trip-time (RTT) between the data center and AWS.Which solution will meet these requirements with the LEAST operational overhead?

Correct Answer: A. Use Amazon CloudWatch Network Monitor to set up Internet Control Message Protocol (ICMP) probe monitoring from each subnet to the on-premises destination.

Explanation

To meet the requirements of monitoring the total packet loss and round-trip-time (RTT) between the on- premises data center and AWS with the least operational overhead, the most suitable solution is:A. Use Amazon CloudWatch Network Monitor to set up Internet Control Message Protocol (ICMP) probe monitoring from each subnet to the on-premises destination.Analysis:Amazon CloudWatch Network Monitor: This is a managed service that provides network performance monitoring, including metrics for packet loss and round-trip time (RTT). By using CloudWatch Network Monitor, you can set up ICMP probe monitoring from each subnet to the on-premises destination without the need to manage additional infrastructure or scripts. This reduces operational overhead significantly. Managed Service: CloudWatch Network Monitor is a fully managed service, meaning AWS handles the infrastructure, scaling, and maintenance. This eliminates the need for you to create and manage EC2 instances, Lambda functions, or Batch jobs for monitoring purposes. Centralized Monitoring: CloudWatch Network Monitor provides a centralized console for viewing network performance metrics, making it easy to monitor and troubleshoot connectivity issues between the on- premises data center and AWS.Why the Other Options Are Not Suitable:B. Create an Amazon EC2 instance in each subnet. Create a scheduled job to send Internet Control Message Protocol (ICMP) packets to the on-premises destination. Why Not: This solution involves creating and managing EC2 instances in each subnet, which increases operational overhead. You would need to set up and maintain the instances, as well as the scheduled jobs to send ICMP packets. This approach is more complex and less scalable than using a managed service like CloudWatch Network Monitor.C. Create an AWS Lambda function in each subnet. Write a script to perform Internet Control Message Protocol (ICMP) connectivity checks.Why Not: While Lambda functions are a good choice for serverless computing, using them for continuous network monitoring can be inefficient and costly. Lambda functions are designed for short-lived, event- driven tasks, not for continuous monitoring. Additionally, you would need to write and maintain the script for performing ICMP connectivity checks, which adds to the operational overhead. D. Create an AWS Batch job in each subnet. Write a script to perform Internet Control Message Protocol (ICMP) connectivity checks.Why Not: AWS Batch is designed for batch processing of large-scale compute jobs, not for continuous network monitoring. Using Batch for this purpose would be overkill and would not provide the real-time monitoring capabilities needed for tracking packet loss and RTT. Additionally, you would need to write and maintain the script for performing ICMP connectivity checks, which adds to the operational overhead.Conclusion:Using Amazon CloudWatch Network Monitor to set up ICMP probe monitoring from each subnet to the on- premises destination provides a simple, scalable, and operationally efficient solution for monitoring network performance between the on-premises data center and AWS.