The correct answer is B. The Security Management Server manages the objects and policies in the Check Point environment. It stores the management database, policy packages, objects, administrator definitions, revisions, and related configuration. Administrators connect to it with SmartConsole to define and publish changes, then install policies to Security Gateways. Option A describes the Security Gateway’s enforcement role more than the management server. Option C is also the gateway’s function; gateways inspect inbound and outbound traffic according to the installed policy. Option D describes Gaia Portal or SmartView-style browser interfaces, not the Security Management Server’s core role. In the three-tier architecture, the Security Management Server is the central management authority, not the traffic enforcement point. Reference topics: Introduction to Network Security Management, Security Management Server, objects, policies, SmartConsole.

The correct answer is B. The Fail Mode setting controls what the gateway does when HTTPS/SSL inspection cannot be completed successfully. Operationally, this determines whether traffic is allowed to pass without inspection or blocked when inspection fails, depending on the configured mode and side of the connection. Check Point R82 SSL/HTTPS inspection settings describe fail-mode behavior as defining whether requests are allowed or blocked when inspection fails. Option A is wrong because NAT policy enforcement is separate from HTTPS Inspection failure behavior. Option C is wrong because bypassing internal or trusted traffic is handled with bypass rules, categories, or allow lists, not fail mode itself. Option D is also incorrect because fail mode is about failure handling for HTTPS inspection, not forcing the environment to use HTTP only. This is a critical production setting: a fail-open posture improves availability but can reduce inspection coverage, while a fail-close posture improves security control but may affect user connectivity if inspection errors occur. Reference topics: HTTPS Inspection, Fail Mode, SSL Inspection failure handling, inspection bypass versus block behavior.

The correct answer is C. In the R82 policy model, URL Filtering is part of the Access Control Policy, specifically in layers where Application Control and URL Filtering are enabled. It is used to control access to websites and URL categories as part of the broader access decision. Option A is wrong because HTTPS Inspection is a separate inspection policy used to decrypt or bypass encrypted HTTPS traffic; URL Filtering may use HTTPS Inspection for better visibility, but it is not part of HTTPS Inspection Policy. Option B is imprecise because “URL Filtering policy” is not the main R82 policy package classification in this question; the blade is managed through Access Control. Option D is wrong because Threat Prevention Policy contains protections such as IPS, Anti-Bot, Anti-Virus, and SandBlast/Threat Emulation-related controls, not URL Filtering as its core policy category. Reference topics: Access Control Policy, Application Control and URL Filtering, HTTPS Inspection distinction, Threat Prevention distinction.

The correct answer is A. Office 365 is represented in Check Point policy through an Updatable Object. Updatable Objects are maintained by Check Point and updated dynamically so administrators can reference cloud services, SaaS platforms, and internet resources without manually tracking every changing IP address or network range. This is exactly the kind of object needed for Microsoft Office 365 because Microsoft cloud service endpoints can change over time. Option B is wrong because Office 365 is not a single Check Point “server” object. Option C is wrong because a host object represents a single host/IP definition, which is unsuitable for a large dynamic SaaS platform. Option D is too generic; while objects can be logical in a broad sense, the official object type used for Office 365 in policy is Updatable Object. For exam purposes, associate cloud/SaaS services such as Office 365 with Updatable Objects because they reduce administrative maintenance and keep policy references aligned with current provider endpoint data. Reference topics: Object Management, Updatable Objects, SaaS/cloud service objects, SmartConsole policy objects.

The correct answer is C. Check Point Identity Awareness relies on two key functional roles: Policy Decision Point (PDP) and Policy Enforcement Point (PEP). The PDP is responsible for acquiring identity information from configured identity sources and sharing identity data as required. The PEP is responsible for enforcing network access restrictions based on identity information. This architecture lets Check Point map users, computers, and groups to network activity, then use that identity context inside Access Control rules. Option A invents process names that are not official Identity Awareness process names. Option B incorrectly expands PDP and PEP as “Pre-Deployment” and “Pre-Enforcement”; those are not Check Point terms. Option D refers to generic communication concepts and not the Identity Awareness blade’s main decision/enforcement model. This question is foundational because Identity Awareness is not merely authentication; it is the bridge between identity acquisition and firewall enforcement. Reference topics: Identity Awareness, Policy Decision Point, Policy Enforcement Point, identity-based enforcement.

The correct answer is A. The primary benefit of HTTPS Inspection is that it enables the Security Gateway to inspect encrypted HTTPS traffic for threats, policy violations, malicious content, inappropriate websites, and application behavior. Without HTTPS Inspection, many security blades can see only limited metadata for encrypted sessions, reducing visibility into modern web traffic. Option B is false because Check Point does not replace SSL/TLS with a proprietary protocol; it intercepts and re-encrypts traffic using certificate-based inspection where configured. Option C is wrong because HTTPS Inspection does not block all HTTPS traffic by default; policy defines what is inspected, bypassed, allowed, or blocked. Option D is wrong because traffic acceleration belongs to performance technologies such as SecureXL, not HTTPS Inspection. The technical model is controlled TLS interception using an outbound CA certificate for client-initiated HTTPS or inbound certificate/private key handling for protected servers. Reference topics: HTTPS Inspection, encrypted traffic inspection, outbound policy, inbound policy, Threat Prevention with HTTPS.

The correct answer is B. Check Point R82 Autonomous Threat Prevention uses predefined profiles so administrators can apply threat-prevention posture according to the protected network segment. Official R82 documentation lists supported profiles such as Recommended for Perimeter, Strict Security for Perimeter, Cloud/Data Center, Internal Network, Recommended for Guest Network, and Monitor. Option B is the best match because it correctly identifies the major deployment categories: perimeter protection, cloud/data center protection, internal network protection, and guest network protection. Option A is wrong because “Cloud North-West” and “Lateral Movement” are not official predefined profile names. Option C is close but uses “East-West-Traffic” as if it were a standalone profile name; in R82, east-west protection is primarily associated with the Cloud/Data Center profile description. Option D is unrelated to Threat Prevention profiles and uses VPN encryption-domain terminology. The key exam point is that Autonomous Threat Prevention is profile-driven and segment-oriented, not manually built from unrelated VPN or directional traffic labels. Reference topics: Autonomous Threat Prevention Profiles, Threat Prevention Fundamentals, Perimeter, Cloud/Data Center, Internal Network, Guest Network.

The correct answer is B. A direct security benefit of HTTPS Inspection is filtering malicious content inside encrypted traffic. Modern malware delivery, phishing, command-and-control activity, and file downloads often use HTTPS. If the gateway cannot inspect encrypted content, Threat Prevention, Anti-Virus, Threat Emulation, URL Filtering, and Application Control may have reduced visibility. Option A is partially related because URL Filtering can block sites, but site blocking is not the main technical benefit of HTTPS Inspection itself. Option C is wrong because bandwidth control is not the purpose of HTTPS Inspection. Option D is also only partially related: inspection can improve application visibility, but the stronger security answer is malicious-content filtering. HTTPS Inspection enables deeper inspection by decrypting traffic according to policy, applying security blades, and then re-encrypting traffic. Reference topics: HTTPS Inspection, Threat Prevention with HTTPS traffic, malicious content filtering, encrypted traffic visibility.

The correct answer is B. The R82 Logging and Monitoring Administration Guide describes log storage disk-management behavior where old log and index files can be deleted when available disk space falls below the configured threshold. The search extract specifically identifies the default threshold behavior: when disk space is below 5000 MBytes, old files begin to be deleted. Option A is incomplete because alerts can be configured for disk thresholds, but the question asks what happens at the default 5000 MB deletion threshold. Option C is wrong because logging does not immediately stop at that threshold; stopping logging is controlled by a different lower threshold. Option D is unsupported because the default response is disk maintenance by deleting older files, not running a script. Operationally, this prevents the log partition from filling completely while retaining as much recent searchable logging as possible. Reference topics: Log Server disk management, log storage thresholds, deleting old log files, Logging and Monitoring.

The correct answer is D. Application Control and URL Filtering rules are used to control which applications and websites users can access and how that usage is recorded. Typical use cases include monitoring application usage, blocking specific applications, informing users through UserCheck-style actions, and blocking websites or URL categories that violate policy. Option A is incorrect because “block malicious files” is primarily a Threat Prevention function involving blades such as Anti-Virus, Threat Emulation, Threat Extraction, and related prevention controls, not the core use case of Application Control and URL Filtering rules. Options B and C include “limit application traffic,” which is not the best description for the tested App Control/URL Filtering rule use cases, and they also incorrectly include blocking malicious files. Official Check Point guidance describes Application Control and URL Filtering rules as defining which users can use specified applications and sites and what application/site usage is recorded in logs. Therefore, monitoring, blocking applications, informing users, and blocking sites are the correct operational examples. Reference topics: Application Control and URL Filtering, UserCheck, Access Control Policy, application/site usage logging.