First 50 of 200 questions. Each one lists the choices, the correct answer, and an explanation. The checker at the top of this page saves progress in this browser when it is available.
Continue in the practice tool above to load more questions, 50 at a time.
Question 1Hybrid Mesh Network Security
In a Check Point Hybrid Mesh deployment, what is the primary role of the Management Server relative to the Security Gateways?
- It terminates all remote access VPN tunnels for the mesh
- It forwards all inspected traffic between mesh peers as an inline proxy
- It centrally stores the security policy and distributes it to the participating gateways Correct answer.
- It performs threat emulation on behalf of every gateway
Explanation
The management server is the single policy authority in a Hybrid Mesh. It holds the rule base and pushes the relevant policy to each managed gateway, while traffic inspection stays on the gateways themselves. This separation of management plane and data plane is the defining characteristic of the architecture.
Question 2Hybrid Mesh Network Security
Which component in a Hybrid Mesh environment enforces the security policy on traffic that traverses between locations?
- The policy installation scheduler
- The Security Gateway Correct answer.
- The Multi-Domain Server
- The SmartConsole client
Explanation
Security Gateways are the enforcement points that inspect and act on traffic according to the installed policy. SmartConsole and the Multi-Domain Server are management-side components that define and store policy but do not inspect packets. Enforcement always occurs at the gateway.
Question 3Hybrid Mesh Network Security
A company wants one central management server to govern gateways at several branch offices while each branch inspects its own traffic locally. Which deployment model fits this requirement?
- Remote access only deployment
- Standalone deployment with a combined gateway and management appliance at each branch
- Distributed deployment with a central management server and separate branch gateways Correct answer.
- Virtual System extension on a single gateway
Explanation
A distributed deployment separates management from enforcement, allowing one management server to control multiple gateways that each inspect local traffic. This matches the Hybrid Mesh principle of centralized policy with distributed enforcement. A standalone appliance would duplicate management at every site.
Question 4Hybrid Mesh Network Security
What does a gateway do during a policy installation initiated from the management server?
- It converts the policy into firewall log entries
- It deletes its local configuration and requests a full rebuild
- It forwards the policy package to every peer gateway in the mesh
- It retrieves the compiled policy, verifies it, and installs it atomically for enforcement Correct answer.
Explanation
During installation the gateway receives the compiled policy package, verifies its integrity, and installs it so enforcement switches over consistently. The management server orchestrates distribution; gateways do not relay policy to peers. This ensures each enforcement point runs the intended rule set.
Question 5Hybrid Mesh Network Security
Why does a Hybrid Mesh architecture reduce the amount of traffic that must be backhauled to a central data center?
- Because gateways inspect traffic locally at the location where it enters or leaves Correct answer.
- Because the management server caches all user sessions
- Because encryption is removed from inter-site links
- Because logging is disabled at branch sites
Explanation
Local enforcement lets each gateway apply policy to traffic at its own site, so traffic destined for the internet or another branch need not traverse a central inspection point. This lowers latency and WAN load. Management remains centralized even though inspection is distributed.
Question 6Hybrid Mesh Network Security
Which management object represents a group of gateways that share a common security policy in a mesh deployment?
- A gateway cluster Correct answer.
- An address range
- A service group
- A network group
Explanation
A gateway cluster groups gateways that share policy and provide redundancy and load sharing. Network groups, service groups, and address ranges are object types used inside rules, not containers for enforcing gateways. Grouping gateways is what enables consistent policy across a mesh.
Question 7Hybrid Mesh Network Security
An administrator needs to verify that a specific branch gateway received the latest policy. Which action best confirms this on the management side?
- Delete and recreate the gateway object
- Disable logging on the branch gateway
- Check the gateway's installed policy version and installation status in the management interface Correct answer.
- Reboot the branch gateway and observe startup messages
Explanation
The management interface reports each gateway's installed policy version and the status of the last installation. Comparing that to the current policy package confirms whether the gateway is up to date. Rebooting or recreating objects does not verify policy state and risks disruption.
Question 8Hybrid Mesh Network Security
What is the purpose of establishing a secure internal communication channel between the management server and each gateway?
- To replace the need for a site-to-site VPN
- To encrypt user traffic between branch offices
- To allow the gateway to authenticate management commands and protect policy transfers Correct answer.
- To provide internet browsing for management users
Explanation
The management channel authenticates the gateway to the management server and protects policy and command exchanges from tampering or eavesdropping. It is a control-plane channel, distinct from data-plane encryption of user traffic. Without it, policy installation could not be trusted.
Question 9Hybrid Mesh Network Security
In a mesh where branches connect to each other and to headquarters, which statement describes how policy consistency is maintained across all enforcement points?
- Each gateway maintains an independent, manually synchronized rule base
- The management server distributes a common policy model to every managed gateway Correct answer.
- Policy is generated dynamically from log data at each site
- Only the headquarters gateway enforces policy for all sites
Explanation
The management server holds the authoritative policy model and installs the applicable rules on every managed gateway. This keeps intent consistent across the mesh while allowing site-specific objects and rules where needed. Manual per-gateway rule bases would drift and create gaps.
Question 10Hybrid Mesh Network Security
Which benefit most directly results from centralizing logging for all gateways in a Hybrid Mesh?
- Reduced need for any gateway to inspect traffic
- Elimination of the management server
- Automatic elimination of false positives
- Correlated visibility of events across sites for investigation and reporting Correct answer.
Explanation
Centralized logging aggregates events from every enforcement point, enabling correlation across sites during investigations and consistent reporting. It does not remove the need for inspection or automatically resolve false positives. The management server remains essential.
Question 11Hybrid Mesh Network Security
A security team wants a branch gateway to keep enforcing its last installed policy if connectivity to the management server is lost. Which behavior supports this?
- The gateway reverts to a default permit-any rule
- The gateway continues enforcing the locally installed policy until a new one is installed Correct answer.
- The gateway forwards traffic to a peer gateway for inspection
- The gateway stops forwarding all traffic immediately
Explanation
Gateways enforce the policy already installed locally, so a management outage does not halt enforcement. Traffic continues to be inspected against the last known good policy. This resilience is a key operational property of distributed enforcement.
Question 12Hybrid Mesh Network Security
What distinguishes a Hybrid Mesh from a purely centralized single-gateway inspection design?
- Management is duplicated at every branch
- All traffic is inspected at one gateway regardless of source
- Enforcement is distributed across multiple gateways while management stays centralized Correct answer.
- No logging is collected
Explanation
Hybrid Mesh distributes enforcement across many gateways but keeps management centralized, combining local inspection with unified control. A purely centralized design funnels traffic to one inspection point. Duplicated management or absent logging are not defining traits.
Question 13Hybrid Mesh Network Security
Which object type would an administrator use to define a remote branch subnet so it can be referenced consistently in rules across the mesh?
- A network object Correct answer.
- A gateway cluster object
- An OPSEC application
- A time object
Explanation
A network object represents a subnet and can be reused in rules on any gateway, keeping definitions consistent. Gateway clusters represent devices, OPSEC applications represent third-party integrations, and time objects constrain rule activation. Only the network object models the subnet.
Question 14Hybrid Mesh Network Security
An administrator installs policy to a mesh and one branch gateway reports installation failure while others succeed. What is the most appropriate first step?
- Disable policy enforcement on the successful gateways
- Reinstall policy to every gateway repeatedly until all succeed
- Review the installation error for that gateway and verify its connectivity and status Correct answer.
- Delete the failing gateway from the mesh permanently
Explanation
A single failing gateway points to an issue specific to that device, such as connectivity, version mismatch, or status problems. Reviewing the reported error and checking the gateway's reachability isolates the cause. Repeated reinstalls or destructive changes do not address the root cause.
Question 15Hybrid Mesh Network Security
Which statement correctly describes the relationship between the management server and gateway software versions in a supported Hybrid Mesh?
- Gateways must always run a newer version than management
- Version compatibility is irrelevant because policy is text-based
- Compatibility between management and gateway versions must be verified against supported combinations Correct answer.
- Management must always run a newer major version than every gateway
Explanation
Management and gateway versions must form a supported combination, which administrators verify before upgrading either side. Neither side is universally required to be newer. Compatibility matters because policy compilation and features depend on both versions.
Question 16Hybrid Mesh Network Security
What is the main security advantage of keeping the management interface reachable only from trusted administrative networks in a mesh deployment?
- It reduces exposure of the control plane to unauthorized access Correct answer.
- It encrypts all user traffic automatically
- It removes the need for gateway authentication
- It speeds up policy installation for branch gateways
Explanation
Restricting management access to trusted networks limits who can reach the control plane, reducing the risk of unauthorized policy changes. It does not accelerate installation, encrypt user traffic, or replace gateway authentication. Protecting the control plane is fundamental to mesh security.
Question 17Hybrid Mesh Network Security
A branch gateway in the mesh must inspect traffic destined for the internet and for headquarters. Which capability allows a single gateway to apply different rules to these flows?
- Disabling the management channel
- Using only implicit default rules
- Relying on log correlation
- Rule base ordering with source, destination, and service matching Correct answer.
Explanation
Rules match on source, destination, service, and other attributes, and are evaluated in order, so one gateway can apply distinct handling to internet-bound and headquarters-bound flows. Implicit rules alone cannot express this granularity. Log correlation is an analysis activity, not enforcement.
Question 18Hybrid Mesh Network Security
Why is it important that policy installation to mesh gateways be coordinated rather than performed ad hoc per device?
- To reduce the number of log entries generated
- To keep enforcement intent consistent and avoid transient gaps or conflicting rules across sites Correct answer.
- To eliminate the need for gateway clusters
- To allow gateways to share a single IP address
Explanation
Coordinated installation ensures every gateway converges on the intended policy, avoiding windows where sites enforce conflicting or outdated rules. Ad hoc per-device changes invite drift and gaps. Log volume, clustering, and addressing are separate concerns.
Question 19Hybrid Mesh Network Security
Which element authenticates a gateway when it first connects to the management server?
- A pre-shared initialization key or certificate established during gateway configuration Correct answer.
- The gateway's routing table
- The first user who logs in to the gateway
- The gateway's MAC address alone
Explanation
Initial trust between management and gateway is established with an initialization key or certificate configured on both sides. MAC addresses, user logins, and routing tables do not provide this authentication. Secure first contact is the foundation of the management channel.
Question 20Hybrid Mesh Network Security
An organization adds a new regional gateway to an existing mesh. Which sequence best reflects correct onboarding?
- Add the gateway to logging only and skip policy assignment
- Configure the gateway as a management server for the region
- Define the gateway object, establish secure communication, assign policy, then install Correct answer.
- Install a default policy first, then define the object later
Explanation
Onboarding requires defining the gateway object, establishing the secure management channel, assigning the appropriate policy, and then installing it. Installing before the object exists or skipping policy assignment leaves the device unmanaged. Promoting a gateway to management is a different architecture.
Question 21Hybrid Mesh Network Security
Which scenario best illustrates the analysis benefit of a mesh with distributed enforcement and centralized management?
- Disabling logging to reduce storage costs
- Allowing each branch to define independent policies without oversight
- Rebuilding every gateway from scratch after each alert
- Investigating an incident by correlating logs from multiple gateways while confirming a single policy baseline Correct answer.
Explanation
Centralized management provides a known policy baseline, and distributed logging provides multi-site evidence, so investigators can correlate events while knowing what each gateway should be enforcing. Rebuilding devices or disabling logging destroys evidence. Unsupervised local policy undermines the baseline.
Question 22Hybrid Mesh Network Security
A mesh administrator observes that a branch gateway is enforcing an older rule set than headquarters. Which explanation is most consistent with the architecture?
- The branch gateway is operating as a management server
- The management server cannot store more than one policy version
- Logging was enabled on the branch gateway
- The branch gateway did not successfully receive or install the latest policy package Correct answer.
Explanation
Gateways enforce whatever policy package they last installed, so an older rule set indicates the latest package was not successfully delivered or installed there. The management server can hold multiple versions, and logging or role changes do not explain stale enforcement. This is a classic drift symptom.
Question 23Hybrid Mesh Network Security
When designing a Hybrid Mesh, why should the management server be placed in a protected network segment rather than exposed to the internet?
- Because it inspects all user traffic inline
- Because it stores user browsing history
- Because it is the trust anchor for policy and its compromise would affect every gateway Correct answer.
- Because it must be reachable by every internet host
Explanation
The management server is the trust anchor that defines and distributes policy to all gateways, so its compromise could subvert the entire mesh. Placing it in a protected segment limits exposure. It is not an inline inspection point and does not need broad internet reachability.
Question 24Hybrid Mesh Network Security
Which combination best characterizes a correctly operating Hybrid Mesh?
- Independent per-site policies with no shared objects
- Centralized policy authority, distributed enforcement, secure management channels, and aggregated logging Correct answer.
- Single enforcement point with duplicated management servers at each branch
- Distributed policy authority, centralized enforcement, and disabled logging
Explanation
A healthy mesh combines a single policy authority, enforcement at each site, protected management channels, and centralized visibility through aggregated logs. Distributing policy authority or enforcing at one point contradicts the model. Independent policies without shared objects invite inconsistency.
Question 25Hybrid Mesh Network Security
An administrator must ensure a new mesh gateway can be managed even if its IP address changes during deployment. Which design choice best supports this?
- Hard-code the IP address in every rule that references the gateway
- Disable the management channel until the address is final
- Identify the gateway by a stable name and use dynamic addressing mechanisms supported by the management Correct answer.
- Rely on the MAC address as the only identifier
Explanation
Using a stable object name and supported dynamic addressing lets the gateway remain manageable as its address changes. Hard-coding addresses in rules creates breakage, and disabling management prevents onboarding. MAC addresses are not a reliable management identifier.
Question 26Hybrid Mesh Network Security
In a Hybrid Mesh deployment, which component holds the authoritative copy of security policy that gateways ultimately enforce?
- Each individual branch gateway
- The upstream internet router
- The local switch at headquarters
- The management server Correct answer.
Explanation
The management server is the single source of truth in a Hybrid Mesh: administrators author policy there and install it outward to gateways. Gateways hold only installed copies for enforcement and do not author the authoritative policy themselves.
Question 27Hybrid Mesh Network Security
Which term describes a mesh topology in which branch gateways can send traffic directly to one another without routing it through headquarters?
- Full mesh or partial mesh connectivity Correct answer.
- Spanning-tree forwarding
- Hub-and-spoke routing
- Single-gateway centralized inspection
Explanation
A mesh lets participating gateways establish direct paths between sites, so branch-to-branch traffic need not traverse a central hub. Hub-and-spoke and single-gateway designs force traffic through a central point instead.
Question 28Hybrid Mesh Network Security
What is the primary purpose of a VPN community in a Hybrid Mesh configuration?
- To define which gateways may establish encrypted tunnels with each other Correct answer.
- To balance traffic across multiple internet providers
- To schedule automatic policy backups
- To assign DHCP addresses to branch clients
Explanation
A VPN community groups gateways that are permitted to build encrypted tunnels among themselves, defining the trust and encryption relationships of the mesh. Address assignment, backups, and ISP load balancing are handled by other features.
Question 29Hybrid Mesh Network Security
Which encryption concept ensures that two mesh peers can validate each other's identity before any user traffic flows?
- Network address translation
- Certificate-based authentication of peer gateways Correct answer.
- Port aggregation
- Quality-of-service marking
Explanation
Peer gateways authenticate each other using certificates issued by a trusted authority, which proves identity before tunnel traffic is accepted. NAT, QoS marking, and link aggregation affect addressing or performance but do not authenticate peers.
Question 30Hybrid Mesh Network Security
A branch gateway in the mesh must inspect both internet-bound traffic and traffic headed to headquarters. Which design element allows it to apply different rules to those two flows?
- Separate VPN communities or directions with distinct policy rules Correct answer.
- Removing the branch from the mesh
- A single catch-all permit rule for all interfaces
- Disabling logging on the branch
Explanation
Distinct communities or traffic directions let the administrator attach different rule bases to internet-bound versus internal flows. A catch-all permit removes differentiation, and disabling logging or leaving the mesh does not create directional policy.
Question 31Hybrid Mesh Network Security
Why should policy installation to all gateways in a mesh be coordinated rather than performed independently per device?
- Because gateways cannot store more than one policy at a time
- So that enforcement remains consistent and tunnels do not reject traffic due to mismatched rules Correct answer.
- Because the management server can only reach one gateway per hour
- To reduce the number of certificates in the environment
Explanation
Coordinated installation keeps every gateway on a compatible rule set so that traffic permitted at one site is not dropped at another. Uncoordinated installs create mismatched enforcement across tunnels. The other options describe limitations that do not exist.
Question 32Hybrid Mesh Network Security
An administrator wants a compromised branch gateway to be unable to reach the management server's administrative services. Which control most directly limits that exposure?
- Restricting management access to defined administrative hosts and trusted networks Correct answer.
- Enabling QoS on the branch uplink
- Increasing the size of the connection table
- Adding more branch gateways to the mesh
Explanation
Limiting which hosts and networks may reach management services means a compromised branch cannot open administrative sessions even if it can route packets. Connection-table size, QoS, and mesh size do not restrict administrative reachability.
Question 33Hybrid Mesh Network Security
Which statement best explains why a Hybrid Mesh is described as combining distributed enforcement with centralized management?
- Management is distributed while enforcement happens only at headquarters
- Each site enforces locally while a central server defines and distributes policy Correct answer.
- Each site defines its own policy and reports summaries to a central server
- A single gateway enforces all policy for every site
Explanation
In a Hybrid Mesh, enforcement happens at each gateway close to the traffic, while policy authoring and distribution remain centralized. The other options invert or collapse one of those two roles.
Question 34Hybrid Mesh Network Security
A branch gateway loses connectivity to the management server but keeps passing traffic. What behavior explains continued enforcement?
- The gateway enforces the last policy it successfully installed Correct answer.
- The gateway borrows policy from a neighboring branch at runtime
- The gateway automatically disables all inspection
- The gateway reverts to a factory default permit-any rule
Explanation
Gateways store the last installed policy locally, so enforcement continues during a management outage. They do not fetch policy from peers, disable inspection, or fall back to permit-any by default.
Question 35Hybrid Mesh Network Security
Which management object would an administrator create to represent a headquarters network so that many rules across the mesh can reference it consistently?
- A log server object
- A network object containing the headquarters subnet Correct answer.
- An administrator account object
- A time object
Explanation
A network object holds the subnet definition and can be referenced by many rules, so changes propagate consistently. Log servers, time objects, and administrator accounts serve unrelated purposes.
Question 36Hybrid Mesh Network Security
During onboarding of a new regional gateway, which step must occur before the gateway can receive policy from the management server?
- The gateway must be established as a managed object and trusted by the server Correct answer.
- The gateway must be assigned a public DNS name
- The gateway must first be added to every VPN community as a satellite
- The gateway must export its configuration to headquarters
Explanation
A gateway must exist as a managed object and complete trust establishment with the server before policy can be installed. Community membership is configured later as needed, and exporting configuration or requiring public DNS is not a prerequisite.
Question 37Hybrid Mesh Network Security
A gateway's IP address changes during deployment. Which design choice keeps it manageable without re-creating the object?
- Identifying the gateway by a stable name or certificate rather than only by IP Correct answer.
- Removing the gateway from the mesh and re-adding it later
- Assigning a static route on every branch
- Disabling all logging until the address stabilizes
Explanation
Trust and object identity anchored to a stable name or certificate let the gateway reconnect even when its address changes. Disabling logging, removing the gateway, or adding routes does not preserve manageability across an address change.
Question 38Hybrid Mesh Network Security
Which outcome best demonstrates the analytical value of centralized logging across a mesh?
- Reducing the number of gateways required per region
- Eliminating the need for certificates between peers
- Correlating an event seen at one branch with related events at other sites in a single view Correct answer.
- Increasing tunnel throughput between branches
Explanation
Centralized logs let analysts stitch together events from multiple enforcement points into one timeline, which reveals cross-site attack patterns. Logging does not reduce gateway counts, replace certificates, or raise tunnel throughput.
Question 39Hybrid Mesh Network Security
What is the main reason the management server in a Hybrid Mesh should sit in a protected internal segment rather than be directly internet-facing?
- It controls policy for the entire mesh, so its compromise would affect every site Correct answer.
- It consumes too much bandwidth to be placed at the edge
- It cannot process encrypted connections at the edge
- It must be physically adjacent to every gateway
Explanation
Because the management server distributes policy to all gateways, compromising it could let an attacker push malicious policy everywhere. Placing it in a protected segment reduces that blast radius. Bandwidth, encryption capability, and physical adjacency are not the reason.
Question 40Hybrid Mesh Network Security
Which object type groups gateways that share a common encryption method and tunnel settings in a mesh deployment?
- A VPN community Correct answer.
- A user group
- A service object
- A log server
Explanation
A VPN community collects gateways that share encryption and tunnel parameters so they can build tunnels with one another. Service objects describe ports and protocols, user groups organize identities, and log servers receive records.
Question 41Hybrid Mesh Network Security
An administrator needs a branch to keep enforcing policy even if the management link flaps repeatedly. Which configuration supports that requirement?
- Disable the local policy store on the branch
- Configure the gateway to fetch policy from a peer branch on each reconnect
- Force the gateway to reboot when the management link drops
- Allow the gateway to retain and enforce its last installed policy during management outages Correct answer.
Explanation
Gateways retain their last installed policy and continue enforcing it while the management link is down. Peer-based policy fetching and disabling the local store are not supported designs, and forced reboots would cause outages.
Question 42Hybrid Mesh Network Security
Which statement about software versions between the management server and mesh gateways is most accurate?
- Gateways must run the exact same build as the management server at all times
- Gateways always run a newer version than the management server
- Version compatibility must be checked, since supported management-to-gateway version combinations are defined Correct answer.
- Version mismatch never affects policy installation
Explanation
Management and gateway versions must fall within supported compatibility ranges, which administrators verify before upgrading either side. Gateways are not always newer, mismatches can affect installation, and identical builds are not mandatory.
Question 43Hybrid Mesh Network Security
A branch gateway reports a policy installation failure while other gateways succeed. Which first step best isolates the cause?
- Immediately reinstall policy to every gateway in the mesh
- Replace the branch gateway hardware
- Delete the VPN community and rebuild it
- Review the installation error for that gateway and verify its connectivity and trust status Correct answer.
Explanation
A single-gateway failure usually points to that gateway's connectivity, trust, or local condition, so the error message and link status should be checked first. Reinstalling everywhere, replacing hardware, or rebuilding the community is premature and disruptive.
Question 44Hybrid Mesh Network Security
Why does distributed enforcement at branch gateways reduce exposure of internal traffic compared with backhauling everything to headquarters?
- It removes the need for any encryption between sites
- It guarantees that no branch can ever be compromised
- Traffic is inspected close to its source, so fewer internal segments carry uninspected flows Correct answer.
- It eliminates the need for a management server
Explanation
Inspecting at the branch means traffic is filtered before it crosses the WAN, limiting how far uninspected flows can travel. Encryption, management, and compromise prevention remain necessary regardless of where enforcement occurs.
Question 45Hybrid Mesh Network Security
An administrator observes that a branch enforces an older rule set than headquarters. Which explanation is most consistent with Hybrid Mesh behavior?
- The branch automatically reverted to a default policy
- The management server stores no policy history
- Policy was not successfully installed to that branch, so it kept its previous version Correct answer.
- Headquarters pushed policy only to internet-facing gateways
Explanation
A gateway keeps its last successfully installed policy, so an older rule set usually means the latest install did not reach it. Automatic reversion to defaults, selective push by role, and absence of policy history are not accurate explanations.
Question 46Hybrid Mesh Network Security
Which element authenticates a gateway when it first connects to the management server and establishes trust?
- The branch's default gateway address
- The gateway's MAC address alone
- The size of the gateway's routing table
- A certificate or initialization key issued for that gateway Correct answer.
Explanation
Trust establishment relies on a certificate or initialization key tied to the gateway's identity. MAC addresses, default gateway addresses, and routing-table size are not credentials and cannot prove identity.
Question 47Hybrid Mesh Network Security
A design team wants branch-to-branch traffic inspected without sending it through headquarters. Which mesh design decision supports that goal?
- Place all branches behind one shared NAT address
- Disable inspection on branch gateways and rely on endpoint tools
- Route all branch traffic through a single headquarters gateway
- Allow direct tunnels between branches with enforcement applied at each participating gateway Correct answer.
Explanation
Direct branch tunnels combined with local enforcement let traffic be inspected without a headquarters detour. Backhauling through one gateway, disabling branch inspection, or sharing a NAT address does not achieve distributed inspection.
Question 48Hybrid Mesh Network Security
Which logging consideration matters most when many branch gateways forward records to one central collector?
- Ensuring logs are stored only on the branch devices
- Ensuring logging is disabled during policy installation
- Ensuring every gateway uses the same public IP address
- Ensuring time synchronization so events from different sites can be correlated accurately Correct answer.
Explanation
Accurate correlation across sites depends on synchronized clocks, otherwise event ordering becomes unreliable. Shared public addresses, branch-only storage, and disabling logging during installs do not improve centralized analysis.
Question 49Hybrid Mesh Network Security
Which statement best describes how a gateway in a mesh handles traffic destined for a remote branch when a direct tunnel is unavailable?
- It silently drops all traffic with no logging
- It forwards the traffic unencrypted to any reachable peer
- It rewrites the destination address to its own
- It follows the configured routing and VPN topology to an alternate path defined by policy Correct answer.
Explanation
Routing and VPN topology determine the available path, and policy decides whether the alternate route is permitted, with logging recording the outcome. Silent drops, address rewriting, and unencrypted forwarding to arbitrary peers are not correct behaviors.
Question 50Hybrid Mesh Network Security
In a Hybrid Mesh deployment, the management server is placed in a protected internal segment and branch gateways connect to it over untrusted links. Which mechanism protects the management channel and authenticates the gateway during this connection?
- An implicit trust relationship based on the gateway's IP address being present in the management server's internal network range
- Plain HTTPS with no additional authentication because the management server sits behind a firewall
- A one-time password sent by email to the gateway administrator each time the gateway restarts
- A site-to-site VPN tunnel that carries only management traffic, with the gateway authenticated by a pre-shared secret or certificate Correct answer.
Explanation
Gateways in a Hybrid Mesh establish a secure, encrypted channel (typically a VPN tunnel) to the management server, and the gateway is authenticated using a pre-shared key or certificate during initial trust establishment. This ensures that only authorized gateways can receive policy and that management traffic crossing untrusted links remains confidential and integrity-protected.