An organization wants to create a custom URL category for a list of highly sensitive internal web applications that should only be accessible from specific internal subnets. However, these applications are accessed via FQDNs that share a common, publicly resolvable root domain (e.g., 'appl.corp.example.com', 'app2.corp.example.com' , 'finance.corp.example.com'). The challenge is that .corp.example.com' is also used by many other public-facing services, and blocking the entire 'corp.example.com' domain would cause significant business disruption. The security team needs to precisely define the custom URL category to include only appl.corp.example.com' , 'app2.corp.example.com' , and 'finance.corp.example.com' , without affecting other subdomains, and then apply a strict access policy. Which configuration approach for the custom URL category is most precise and least prone to false positives, assuming other subdomains like 'public.corp.example.com' or 'dev.corp.example.com' exist and should not be included?
Select one answer.
Purchase Full Access to view answer options & explanation
The first 151 questions in this bank are completely free. Unlock Full Access on the exam page to view all answer choices, verified answers, explanations, and community discussions for all 503 questions.
