Option B is a classic rule-shadowing condition. Zscaler documents that URL Filtering rules stop at the first matching rule, and Cloud App Control rules likewise use an explicit numerical rule order. The first rule matches every employee request to the sanctioned application without checking time. The service therefore applies Allow and never reaches the later outside-business-hours block. This leaves the application available during the restricted period and can also explain the absence of expected restricted-access log hits. The corrective design is to place the narrower time-based block above the broad allow or add the required time condition to the applicable access rule. Device posture does not supply policy time, logging actions do not automatically override earlier matches, and SSL inspection does not invalidate the application category in the manner described.

Zscaler's Microsoft 365 optimization model is designed to reduce latency and avoid breaking Microsoft- recommended connectivity patterns. The Office 365 One Click rule automatically applies recommended bypass/optimization behavior for Microsoft 365 traffic, including exemption from SSL inspection and other web-policy processing where required. Option C (Multiple distributed DNS resolvers providing local results) is correct because the immediate effect is optimized M365 handling rather than blanket inspection or blocking.
Why the other options are incorrect:
A). Single DNS resolver with forwarders providing centralized results: DNS resolves names to IP addresses; it is a support service, not an access protocol or scoring engine by itself.
B). Private MPLS in each branch office providing connection: Private MPLS backhaul keeps traffic on the old hub-and-spoke path instead of sending users directly to the nearest cloud service.
D). Optimized TCP Scaling for maximum throughput of files: TCP scaling can improve throughput for some flows, but it does not choose the nearest Microsoft 365 service endpoint.

URL Filtering remains the most widely deployed web filtering method, serving as the first line of defense by categorizing and controlling access to websites before any deeper inspection or cloud#based security service takes over.

Option B separates application identity, traffic forwarding, and authorization cleanly. Zscaler defines private applications through Application Segments, including their FQDN or IP and ports. Each resource set should therefore have a distinct segment or segment group. The administrator can then ensure Client Connector forwards those destinations to ZPA and use Access Policy to allow the engineering identity group only to engineering resources and the finance group only to finance resources, with posture conditions where required. A location condition does not correct cross-department entitlement. A broad Allow rule preserves the overexposure even if it includes a department attribute incorrectly, and inspection policy is not a substitute for ZPA authorization. Consolidating the applications makes least-privilege separation harder. Segmentation plus group-specific access rules preserves intended connectivity while preventing access to the other department's resources.

Option D blocks both indicator types at the appropriate enforcement layers. Hard-coded IP callbacks can be matched through a destination IP group referenced by a Cloud Firewall Drop rule, while domain-based callbacks can be denied through a custom URL category and URL Filtering policy. Positioning the specific Firewall denial before generic outbound allows ensures that it is evaluated. Zscaler's Destination IP Group documentation explains how IP addresses, FQDNs, and URL categories are grouped for Firewall policy. The URL Filtering overview documents rules based on URL categories, users, groups, and other criteria. Browser Isolation permits controlled rendering and is not the correct response for confirmed command-and-control infrastructure. TLS inspection alone does not constitute a deny decision. Risk-based page scoring is less deterministic than explicitly blocking known indicators and does not adequately address hard-coded IP callbacks.