RetailCorp wants to monitor connectivity from three front-end VMs to five backend APIs. They require 60-second monitoring intervals, group-based configuration to manage the five endpoints as one logical set, and alerts when more than three consecutive tests fail within five minutes. Which configuration using Connection Monitor v2 and Azure Monitor is the correct approach?

The correct option leverages Connection Monitor v2's capabilities for group-based monitoring and integration with Azure Monitor alerts. A single Connection Monitor resource with a Test Group allows defining multiple sources (front-end VMs) and destinations (APIs) as a logical unit, meeting the group configuration requirement. Setting the test frequency to 60 seconds directly addresses the monitoring interval. Azure Monitor metric alerts can then be configured on the Connection Monitor's availability or failed tests metric, using an evaluation period of 5 minutes and a threshold of more than three failed tests to meet the alerting criteria. The other options are less efficient or don't fully meet the requirements: Deploying five separate Connection Monitor instances is less efficient and doesn't provide a single logical group for the APIs. Classic Network Watcher connection troubleshoot runbooks are for on-demand troubleshooting, not continuous monitoring, and would be overly complex to configure for this scenario. Installing custom agents for curl checks is a manual, custom solution that bypasses Azure's native monitoring tools, adding unnecessary complexity and maintenance overhead.