Question 370
An IT support ticket describes this situation: A user changes browser secure-DNS settings to a private unmanaged provider, bypassing corporate filtering. Which observation should the technician check first to distinguish the cause?
Explanation
Correct Answer
Compare browser DoH policy, endpoint DNS settings, filtering logs and approved resolver. This is the most targeted initial check for: A user changes browser secure-DNS settings to a private unmanaged provider, bypassing corporate filtering. It tests whether the underlying mechanism applies: Enterprise-controlled DNS resolution and policy enforcement can be undermined by unmanaged browser DoH. Based on the results, the appropriate intervention is: Enforce managed secure DNS policy and block unauthorized resolver overrides. A successful resolution is demonstrated by: Browsing uses approved DNS controls without losing legitimate encrypted resolution.
Incorrect Answers
Check exact URL, certificate subject/issuer, DNS resolution and published portal address. That addresses a different mechanism; this question turns on Compare browser DoH policy, endpoint DNS settings, filtering logs.
Inspect active browser identity, sync settings, enterprise policies and stored credential scope. That observation may hold without resolving the relevant issue: Compare browser DoH policy, endpoint DNS settings, filtering logs.
Inspect installation source, extension permissions, updates and suspicious network activity. It does not verify the requested outcome; here the decisive check concerns Compare browser DoH policy, endpoint DNS settings, filtering logs.