nerdexam
Check_Point

156-215.80 · Question #406

When connected to the Check Point R80 Management Server using the SmartConsole the first administrator to connect has a lock on:

The correct answer is D. Only the objects being modified in his session of the Management Database and other. In R80, Check Point replaced full-database locking with per-session object locking, allowing multiple administrators to work concurrently on different objects simultaneously.

Security Policy Management

Question

When connected to the Check Point R80 Management Server using the SmartConsole the first administrator to connect has a lock on:

Options

  • AOnly the objects being modified in the Management Database and other administrators can
  • BThe entire Management Database and other administrators can connect to make changes only if
  • CThe entire Management Database and all sessions and other administrators can connect only as
  • DOnly the objects being modified in his session of the Management Database and other

How the community answered

(45 responses)
  • A
    2% (1)
  • B
    9% (4)
  • C
    2% (1)
  • D
    87% (39)

Why each option

In R80, Check Point replaced full-database locking with per-session object locking, allowing multiple administrators to work concurrently on different objects simultaneously.

AOnly the objects being modified in the Management Database and other administrators can

This describes a per-object lock but omits the session scope qualifier and misrepresents concurrent admin capabilities, making it an incomplete and inaccurate description of R80 behavior.

BThe entire Management Database and other administrators can connect to make changes only if

Locking the entire Management Database is the legacy pre-R80 behavior; R80 specifically introduced per-session object locking to replace this restrictive model.

CThe entire Management Database and all sessions and other administrators can connect only as

Restricting all other administrators to read-only access is the old single-admin lock model and does not reflect R80's concurrent session architecture.

DOnly the objects being modified in his session of the Management Database and otherCorrect

R80 introduced a collaborative multi-administrator model where each session acquires locks only on the specific objects or rules being actively edited within that session. Other administrators can connect simultaneously and modify different objects without conflict, which is a fundamental architectural change from the single-admin lock model used in versions prior to R80.

Concept tested: R80 concurrent administrator sessions and per-session object locking

Source: https://sc1.checkpoint.com/documents/R80.40/WebAdminGuides/EN/CP_R80.40_SecurityManagement_AdminGuide/Content/Topics-SMAG/Working-with-Sessions.htm

Topics

#SmartConsole sessions#concurrent administrators#management database lock#write permission

Community Discussion

No community discussion yet for this question.

Sign up to join the discussion
Full 156-215.80 Practice