1Z0-1072-25 Question 162
Select 2Your organization hosts a global application across the Phoenix and Frankfurt regions in Oracle Cloud Infrastructure (OCI). European users have reported slow response times reaching the application components in the Phoenix region. You suspect high inter-region latency. Which two approaches will help you effectively measure and identify potential latency or routing issues between these OCI regions?
- A
Configure OCI Health Checks from a vantage point in Frankfurt to test endpoints hosted in Phoenix.
- B
Rely on native Object Storage metrics to directly track network latency across the two regions.
- C
Run traceroute or ping from a Compute instance in the Frankfurt region to your Phoenix endpoints, observing hop counts and round-trip times.
- D
Force all user traffic to route through an on-premises data center to enable granular network latency insights.
Show answer and explanation
Correct answers: A, C
Explanation
To analyze inter-region latency in OCI, it is critical to use monitoring or diagnostic tools that can generate real-time network measurements. OCI Health Checks (https://docs.oracle.com/en-us/iaas/Content/HealthChecks/Concepts/healthchecks.htm) provide synthetic monitoring from multiple vantage points, offering insight into end-to-end performance. Complementing this method with OS-level diagnostics like traceroute or ping from regional Compute instances helps pinpoint routing bottlenecks. Object Storage metrics and forcing traffic through external paths are less effective for measuring actual round-trip times between OCI regions.
- A. Correct.
Configuring OCI Health Checks from a vantage point near the Frankfurt region to endpoints in Phoenix is an effective method to measure end-to-end latency. Health Checks let you monitor from multiple vantage points and track response times. This enables proactive detection of high latencies or outages.
- B. Incorrect.
While Object Storage metrics do feature some performance statistics, they are not designed to measure detailed inter-region network latency. These metrics typically focus on storage-related performance rather than continuous end-to-end latency tests.
- C. Correct.
Using traceroute or ping from Compute instances located in different regions is a straightforward way to diagnose network path and measure round-trip times. This approach provides detailed hop-by-hop latency, helping identify high-latency segments.
- D. Incorrect.
Routing all traffic through an on-premises data center usually adds extra hops and does not provide direct, granular measurements of native inter-region latency on OCI's backbone. This would likely increase latency rather than isolate its cause.