An administrator wants to monitor availability and response time of an external HTTPS API endpoint from multiple geographic locations. After enabling synthetic monitoring in the Instana backend settings, what must be configured next?

Instana Synthetic Monitoring uses Points of Presence (PoPs) — self-hosted or Instana-managed — deployed in geographic locations to execute tests from outside the monitored application. Administrators create synthetic test definitions specifying the endpoint URL, test type (ping, API script, or browser), execution frequency, geographic PoP selection, and assertion thresholds. Results populate the Synthetic Monitoring dashboard with per-location availability and latency data. The correct answer is 'Deploy Instana synthetic Points of Presence in the target regions and create a synthetic test specifying the URL, test type, frequency, and assertion criteria'. The incorrect options — 'Install Instana host agents on web servers in each geographic region and configure the HTTP sensor for external URL monitoring', 'Create a custom metric via the Instana Events API that polls the endpoint on a schedule and reports latency and status codes', 'Configure Instana application monitoring with a synthetic user session profile that replays browser interactions' — are wrong because they do not align with IBM Instana's architecture or recommended practices for this scenario. Understanding this concept is essential for the Domain 4: Integration domain of the IBM Instana Observability certification.