1Z0-1072-25 Question 150
Single answerYour company hosts a global e-commerce application on Oracle Cloud Infrastructure (OCI). Customers in various geographic regions report slow loading times, especially for images and static assets. You plan to configure OCI Web Application Firewall (WAF) for web application acceleration. Which action would most effectively reduce latency for those static resources while maintaining security controls?
- A
Enable and configure caching rules within the OCI WAF for static assets, ensuring they are served from the Edge nodes closest to end-users.
- B
Deploy a Private Load Balancer with custom SSL termination in your Virtual Cloud Network (VCN) and expect it to cache static content automatically.
- C
Rely on the built-in object caching policy of your backend service instances, leaving the WAF in pass-through mode.
- D
Place all static files in an OCI File Storage system and mount it to the WAF as an NFS share for caching.
Show answer and explanation
Correct answer: A
Explanation
To implement web application acceleration on OCI, you must leverage caching at the Edge. Configuring the OCI WAF with caching rules for static content ensures those assets are delivered from geographically distributed OCI Edge nodes. This shortens delivery paths for end-users and maintains security coverage via WAF. Refer to the Oracle Cloud Infrastructure documentation for details on WAF configuration and caching best practices.
- A. Correct.
Correct: Configuring caching rules within OCI WAF allows Edge nodes to store and serve static assets from the nearest location to end-users. This reduces round trips to the origin server and improves latency while still applying WAF security policies. It is a best practice for accelerating global web traffic in OCI.
- B. Incorrect.
Incorrect: A Private Load Balancer in OCI is designed for internal traffic within a VCN and does not provide global content caching. Simply using a private load balancer with SSL termination will not automatically accelerate static content for geographically distributed users.
- C. Incorrect.
Incorrect: Relying solely on backend caching on the origin servers does not offload traffic at the Edge. While origin caching can help reduce requests to the application, it won't significantly shorten the network path for users in distant regions. The WAF must be configured for content acceleration at the Edge nodes.
- D. Incorrect.
Incorrect: OCI File Storage over NFS is not intended to handle global content delivery at the Edge. Mounting a file system to WAF is not a supported method for caching static web assets, and it would not improve performance for distant users.