The correct answer is B. A Check Point Threat Prevention Policy integrates prevention-oriented blades and protections such as IPS, Anti-Bot, Anti-Virus, and SandBlast-related capabilities such as Threat Emulation and Threat Extraction, depending on licensing and configuration. Option A incorrectly includes Content Awareness and URL Filtering as Threat Prevention Policy capabilities; those are part of Access Control policy functionality in the unified policy model. Option C incorrectly places Application Control and URL Filtering under Threat Prevention. Option D makes the same category error by mixing Access Control features with IPS. In R82, Access Control answers “who/what may access what,” using blades such as Firewall, Application Control, URL Filtering, Content Awareness, Identity Awareness, VPN, and Mobile Access. Threat Prevention answers “what malicious activity should be prevented,” using protections against exploits, malware, bots, malicious files, and suspicious content. Reference topics: Threat Prevention Policy, IPS, Anti-Bot, Anti-Virus, SandBlast protections.

The correct answer is D. A shared layer allows a policy layer to be reused rather than recreated separately in every rule or policy package. In R82, layer properties include a sharing option that lets administrators share a layer with other policies. Official guidance also states that a new policy layer can be configured directly in a specific policy or as a shared policy layer for several policies, and that an Inline Layer can be configured within a specific rule while an Ordered Layer exists as a separate dedicated layer. This supports modular policy design: common controls can be centralized and reused, which improves consistency and reduces administrative duplication. Option A is wrong because NAT translation is configured through NAT rules and NAT settings, not by enabling a shared layer. Option B is the opposite of the real function; sharing increases reuse rather than disabling the layer elsewhere. Option C is also wrong because permissions can restrict who edits a layer, but the “Shared Layer” function itself is about reuse across rules or policies. Reference topics: Policy Layers, Inline Layers, Ordered Layers, Shared Layers, SmartConsole Layer Properties.

The correct answer is C. The Object Explorer is the separate SmartConsole window used for comprehensive object management. It lets administrators search, filter, create, edit, import, export, and organize many object types beyond the limited gateway/server creation flow. The Gateways & Servers New menu is useful for defining management servers, gateways, clusters, and related infrastructure objects, but Object Explorer is broader. Option A, “Objects Pane,” is not the specific separate object-management tool being tested. Option B, “Categories Explorer,” is not the official SmartConsole tool name. Option D, “More object types menu,” may appear as a creation/navigation option, but it is not the separate window used for full object management. Object Explorer is especially useful in larger environments because it gives administrators a structured view of objects by type/category and supports management operations such as CSV import/export. Reference topics: Object Management, Object Explorer, Objects menu, SmartConsole object administration.

The correct answer is B. Identity Collector is the correct Identity Awareness component for high-volume environments that integrate with Microsoft Active Directory, Cisco Identity Services Engine, NetIQ eDirectory, or Syslog. It centrally acquires identity data from those sources and forwards identity information to Check Point gateways for policy enforcement. Option A is wrong because the Terminal Server identity agent is used for environments where multiple users share terminal server or Citrix infrastructure. Option C is an identity source mechanism, not the high-volume client described by the question. Option D is installed on user endpoints and is useful where endpoint identity reporting is required, but it is not the central high-volume collector for AD, ISE, eDirectory, and Syslog. This question tests the deployment role of Identity Collector: it is infrastructure-facing and scalable, not endpoint-focused. Reference topics: Identity Awareness, Identity Collector, high-volume identity acquisition, AD/Cisco ISE/NetIQ/Syslog integration.