1Z0-1072-25 Question 160
Single answerYour company runs a global e-commerce application deployed in two Oracle Cloud Infrastructure (OCI) regions. Lately, the team has noticed intermittent timeouts when microservices in one region call APIs hosted in the other region. You suspect high latency between the two OCI regions is causing these failures. Which approach provides a reliable, in-OCI solution to measure and analyze inter-region latency over time so you can effectively troubleshoot and optimize your architecture?
- A
Enable Flow Logs in each region� Virtual Cloud Network (VCN) and parse log entries to infer network latency.
- B
Use OCI Health Checks with vantage points in each region to measure real-time Round Trip Times (RTT) between the two regions.
- C
Deploy a local compute instance in each region and run a manual traceroute every day, archiving the results.
- D
Set up a scheduled job on an on-premises server that pings both regions for latency data and stores the results in a spreadsheet.
Show answer and explanation
Correct answer: B
Explanation
Using OCI Health Checks is the most effective in-OCI method to continuously measure and analyze inter-region latency over time. OCI Health Checks can be configured with multiple vantage points, including those within specific OCI regions, to collect granular real-time data. This setup is recommended in the Oracle Cloud Infrastructure Health Checks documentation for diagnosing and troubleshooting cross-region application performance issues.
- A. Incorrect.
Incorrect. While Flow Logs provide metadata such as source/destination IP addresses and port numbers, they do not capture actual latency metrics, making them unsuitable for detailed inter-region latency analysis.
- B. Correct.
Correct. OCI Health Checks can be configured with vantage points in different regions, providing round-trip latency data that is tracked over time in the OCI console. This is a reliable approach for measuring inter-region latency inside OCI.
- C. Incorrect.
Incorrect. Although manual traceroute can provide some insight, it is neither continuous nor integrated with OCI metrics. It results in spot data rather than a comprehensive performance trend.
- D. Incorrect.
Incorrect. This approach measures from an on-premises location to OCI, not purely inter-region latency within OCI. Additionally, storing data in a spreadsheet lacks the unified dashboards and historical trending available in OCI� native tools.