1Z0-1072-25 Question 147
Single answerYou manage a global eCommerce application hosted in a single Oracle Cloud Infrastructure (OCI) region. Many customers who are geographically distant from your region are reporting slow page load times. You have deployed an OCI Web Application Firewall (WAF) for security, but overall performance has not improved significantly for distant users. Which solution is recommended to reduce latency and accelerate your application's static content for these users?
- A
Enable edge caching in your OCI Web Application Firewall to serve static assets from globally distributed edge nodes.
- B
Upgrade your OCI Compute instances to larger shapes in the same region to handle more user requests simultaneously.
- C
Configure a custom script on your application server to compress and serve static content directly without OCI Load Balancer involvement.
- D
Implement a second application stack in another OCI region and rely on manual DNS updates to direct traffic to the closest region.
Show answer and explanation
Correct answer: A
Explanation
To implement web application acceleration on OCI, you can leverage the built-in caching capabilities of the OCI Web Application Firewall. By enabling edge caching, static content is stored on globally distributed edge nodes, reducing round-trip time for distant users. This approach aligns with Oracle� best practices for improving application performance and minimizing latency. Refer to the 'OCI WAF Documentation' and 'Edge Services Best Practices' in the Oracle Cloud Infrastructure documentation for more details.
- A. Correct.
Option 1 is correct. OCI WAF caching can significantly improve performance for distant users by storing and serving static content from edge locations around the world, reducing round-trip time to the origin server.
- B. Incorrect.
Option 2 is incorrect. While larger shapes can handle more concurrent requests, they do not by themselves reduce network latency for users far from the OCI region. The bottleneck is distance, not server capacity.
- C. Incorrect.
Option 3 is incorrect. Compressing content may help reduce payload size, but it does not address global latency or provide geographically distributed caching. You still rely on a single origin for all users.
- D. Incorrect.
Option 4 is incorrect. Deploying in multiple regions can improve availability and local performance, but relying on manual DNS changes is error-prone and not a straightforward way to achieve global web acceleration. Without a global traffic management solution or caching, you are not fully addressing latency.