Sign in
Home/Check Point/Check Point Certified Troubleshooting Expert – R82 (CCTE)/Free questions

Check Point Certified Troubleshooting Expert – R82 (CCTE) — Free Practice Questions

10 free sample questions from a bank of 271, with the correct answers and explanations. No signup required — start practising right now.

1An administrator is investigating an earlier CPU spike on an R82 Security Gateway. The gateway supports CPView history, and its database contains the relevant samples. The administrator wants to open the recorded data and enter the incident timestamp directly. Which workflow meets this requirement?
  • Start cpview, then press T/t to enter the incident timestamp.
  • Start cpview, then press R to enter the incident timestamp.
  • Start cpview -t, then press T/t to enter the incident timestamp.
  • Start cpview -t, then press R to enter the incident timestamp.
Answer: C

The short version

C — Run cpview -t to open History mode and then press t to type the incident timestamp.

Key concepts in this question

  • cpview -t / cpview --history opens the stored CPView database (in R82, /var/log/CPView_history/CPViewDB.dat) instead of the live counters.
  • From R80.30 onward the timestamp is no longer accepted as a command-line argument to -t; it must be entered from inside History mode.
  • The accepted format is [Jan...Dec] [01...31] [4-digit Year] [hh:mm:ss], and R81.10 and higher also accept partial values such as Jan 02.

Why C is correct

sk101878 states that cpview -t "Shows the data in the History mode - either the oldest available data, or the data for the specified timestamp" and then instructs: "In CPview, press the t key and enter the applicable date and time." sk163804 confirms the changed behaviour: the old cpview -t <timestamp> form no longer lands on the requested time, and the documented procedure is to run cpview -t, press t, and enter the date. Only option C uses both the correct startup flag and the correct in-session key.

Why the others are wrong

  • A. Plain cpview opens the live view of current statistics; there is no recorded timeline to jump into, so pressing t does not reach the stored samples.
  • B. The startup command is right but R is the refresh-rate control, not the timestamp prompt.
  • D. cpview -t is right, but R again opens the refresh-rate window instead of asking for a date and time.

156-588 exam tip

Keep the two keys separate: t = timestamp prompt, R = refresh rate. History mode is the only place t, + and - operate.

2In CPView history mode, the displayed time is 14:15:00. The administrator has set the history refresh interval with R to 120 seconds. Assume the required snapshots are available and no date boundary is crossed. What time should one press of + select?
  • 14:17:00
  • 14:16:00
  • 14:15:02
  • 14:13:00
Answer: A

The short version

A — With a 120-second refresh interval, one press of + moves from 14:15:00 to 14:17:00.

Key concepts in this question

  • In History mode, + advances to the next stored timestamp and - returns to the previous one.
  • The step size is the refresh rate currently configured with the R key, not a fixed one-minute step.
  • The default refresh rate is 2 seconds, but the question has already changed it to 120 seconds.

Why A is correct

The key table in sk101878 defines + as "Goes to the next timestamp. The next timestamp is equal to the current timestamp plus the refresh rate (see the R key)." With R set to 120 seconds, each press moves two minutes: 14:15:00 + 00:02:00 = 14:17:00. No date boundary is crossed and the snapshots exist, so the jump is valid.

Why the others are wrong

  • B. 14:16:00 would be correct only if the refresh rate were 60 seconds; nothing in the scenario sets it to one minute.
  • C. 14:15:02 applies the factory default of two seconds and ignores the stated 120-second setting.
  • D. 14:13:00 is what the - key produces, because it subtracts one refresh interval instead of adding one.

156-588 exam tip

Read the refresh rate before doing the arithmetic. + and - are relative to whatever R shows, while t jumps to an absolute date and time.

3On an R82 Security Gateway, an engineer must check whether the CPView services responsible for Database and SNMP activity are running. The task permits a status query only; service state must be preserved. Which command meets the requirement?
  • cpview --services on
  • cpview --services off
  • cpview --services stat
Answer: C

The short version

C — cpview --services stat reports the Database and SNMP service status without changing it.

Key concepts in this question

  • cpview -s / cpview --services administers the CPView services that handle Database and SNMP activity.
  • The accepted arguments are on, off, stat and export.
  • stat is the read-only query; on and off toggle the services, and export writes the current CPView database to a file.

Why C is correct

sk101878 lists cpview -s {on | off | stat} / cpview --services {on | off | stat} and defines them as "Administration of the CPView services that are responsible for the Database and SNMP activity", with stat meaning "Shows the status of the CPView services". A successful query prints a line such as CPView services running. Because the task allows only a status query and requires service state to be preserved, the read-only stat form is the only fit.

Why the others are wrong

  • A. on enables the services; it may change state and does not simply report it.
  • B. off disables the services, which directly violates the requirement to preserve service state.

156-588 exam tip

Do not confuse --services (Database and SNMP) with --api_service (the CPView API). Both use on | off | stat, but they control different daemons.

4The Management API access setting on an R82 Management Server is Management server only. An administrator needs to send an API request without changing this setting. Which request origin is permitted by that access mode?
  • A SmartConsole client sending the request through its API interface.
  • A remote Windows computer running a copied mgmt_cli.exe utility.
  • The mgmt_cli utility running on the Management Server command line.
  • A remote workstation using Web services, provided its IP address is a Trusted Client.
Answer: C

The short version

C — With Management server only selected, the only permitted origin is mgmt_cli on the Management Server command line.

Key concepts in this question

  • The Management API access setting has three values: Management server only, All IP addresses that can be used for GUI clients, and All IP addresses.
  • The setting controls which clients may reach the API Server; it is independent of the administrator's permission profile.
  • mgmt_cli is the local tool; mgmt_cli.exe is the SmartConsole-shipped Windows tool; Web services use https://<server>/web_api/.

Why C is correct

The R82 Security Management/CLI guide, in "Configuring Access Settings", says of Management server only: "Only the Management Server itself can connect to the API Server. This option only lets you use the mgmt_cli utility on the Management Server command line to send API requests. You cannot use SmartConsole or Web services to send API requests." That is precisely a local mgmt_cli invocation, so no setting change is needed.

Why the others are wrong

  • A. SmartConsole-originated API requests require one of the two broader access settings; the guide explicitly excludes SmartConsole under Management server only.
  • B. A copied mgmt_cli.exe runs on a remote Windows host, so the request does not originate on the Management Server.
  • D. Web services from a remote workstation are excluded, and a Trusted Client entry only matters for the "All IP addresses that can be used for GUI clients" mode.

156-588 exam tip

Remember the pairing: Management server only = local mgmt_cli only. Trusted Clients becomes relevant only after you widen access.

5An R82 administrator is checking prerequisites for another administrator to log in with mgmt_cli. The API service has passed its readiness check, the request origin is allowed, and the authentication details have been verified. The remaining check concerns the Permission Profile assigned to that administrator. Which permission must be selected in that profile?
  • Management API Login in the profile's Management permissions.
  • The workstation address in Trusted Clients.
  • Automatic start in Management API startup settings.
  • Logging & Status on the Management Server object.
Answer: A

The short version

A — The administrator's Permission Profile must have Management API Login selected under its Management permissions.

Key concepts in this question

  • Three independent gates must pass before mgmt_cli login works: the API Server must be running and ready, the access setting must allow the request origin, and the administrator's profile must allow API access.
  • The profile check is done per Administrator object: General page > Permission Profile > eye icon > Management.
  • The required permission is literally named "Management API Login".

Why A is correct

The R82 API deployment procedure ends with: "In the object of each applicable Administrator, make sure the assigned Permission Profile allows access to Management API... In the left panel, click Management. The permission Management API Login has to be selected. If it is not selected, then close this window and edit this Permission Profile object." The scenario has already cleared the service-readiness, origin and authentication checks, so the remaining gate is that profile permission.

Why the others are wrong

  • B. Trusted Clients affects the request origin, which the scenario says is already allowed; it is not a profile permission.
  • C. Automatic start is a startup setting for the API Server process, not an authorization check on an administrator.
  • D. Logging & Status is a blade enabled on the server object for logging, unrelated to API login rights.

156-588 exam tip

When an API login is refused, check in this order: api status, access setting, then Permission Profile > Management > Management API Login.

6An R82 administrator is reviewing the documented note for the API process row in the Processes table of api status. Which access-setting and Trusted Clients combination does the guide specifically identify as one in which that row may show Stopped?
  • All IP addresses that can be used for GUI clients, with more than 200 Trusted Clients.
  • All IP addresses, with more than 200 Trusted Clients.
  • Management server only, with more than 200 Trusted Clients.
  • All IP addresses that can be used for GUI clients, with 200 or fewer Trusted Clients.
Answer: A

The short version

A — The guide names "All IP addresses that can be used for GUI clients" with more than 200 Trusted Clients as the case where the API row may show Stopped.

Key concepts in this question

  • api status prints an overall status and a Processes table with Name, State, PID and More Information columns.
  • The overall status can read Started and the readiness test can pass while the individual API process row reads Stopped.
  • The note is an exception to the normal expectation that the API row shows running.

Why A is correct

The R82 "Managing Security through API" topic states: "The output of this command may show the state of the API process as Stopped when the API access is set to All IP addresses that can be used for GUI clients, and more than 200 Trusted Clients are configured", followed by the sample API Stopped ... row. Both conditions are required together, and option A reproduces both exactly: that specific access mode and a Trusted Clients count above 200.

Why the others are wrong

  • B. "All IP addresses" is a different access mode; the note is tied to the GUI-clients mode, not the unrestricted mode.
  • C. Management server only is not the mode named in the note.
  • D. The threshold in the guide is more than 200, not 200 or fewer; with a small Trusted Clients list the row is not expected to show Stopped.

156-588 exam tip

Quote-level facts like the 200-Trusted-Clients threshold are worth memorizing verbatim; the exam tests the exact access mode plus the exact comparison.

7An administrator changes a gateway's configured Log Server to a dedicated remote Log Server and publishes the SmartConsole session. The administrator is identifying the documented deployment actions for the Log Server and the gateway. Which pairing assigns the actions to the correct targets?
  • Install Database on both the remote Log Server and the gateway.
  • Install Database on the gateway; install the gateway policy on the remote Log Server.
  • Install Database on the remote Log Server; install the policy on the gateway.
  • Install the gateway policy on both the remote Log Server and the gateway.
Answer: C

The short version

C — Run Install Database on the remote Log Server, and install the policy on the gateway.

Key concepts in this question

  • Changing a gateway's Log Server object touches two different targets: the Log Server database and the Security Gateway policy.
  • Install Database pushes object and log-server configuration to the server that holds it.
  • Installing a policy pushes the gateway's logging destination and rule base to the gateway itself.

Why C is correct

The R82 Logging and Monitoring guide's "Deploying Logging" page lists what requires Install Database: "You must execute the Install Database function on the remote Log Server when you: ... Change a Security Gateway's Log Server." The same page's "Configuring the Security Gateways for Logging" procedure ends with steps 6 and 7: "Publish the SmartConsole session. Install a policy on the Security Gateway." So the database action belongs to the remote Log Server and the policy action belongs to the gateway, which is exactly the pairing in C.

Why the others are wrong

  • A. Installing the database on both targets is unnecessary; the gateway does not hold the Log Server database.
  • B. This reverses the targets: the gateway does not receive Install Database, and the Log Server does not receive the gateway policy.
  • D. Installing the gateway policy on the Log Server is meaningless because the Log Server enforces no access policy for this change.

156-588 exam tip

Pair the verb with the object: Install Database = server objects; Install Policy = enforcing gateways. A log-destination change needs one of each.

8Two R82 Log Servers have log indexing disabled. An investigator wants to search their existing logs in SmartConsole using this non-index mode. Which search approach matches the documented limitation?
  • Connect to each Log Server separately; each search examines all of that server's files together.
  • Connect to either Log Server; it automatically searches all files on both servers.
  • Connect to the Management Server and search both servers' files in one unified indexed view.
  • Connect to each Log Server separately and select one log file at a time for the search.
Answer: D

The short version

D — Connect to each Log Server separately and open one log file at a time to search it.

Key concepts in this question

  • Log indexing is what gives SmartConsole a unified, fast query across all log files and servers.
  • Non-index mode saves disk space and CPU but removes that unified view.
  • The guide's workaround is to attach SmartConsole directly to a Log Server and use File > Open Log File.

Why D is correct

The R82 "Deploying Logging" page, under "Disabling Log Indexing", states: "When log indexing is disabled, you must connect with SmartConsole to each Log Server separately to query its logs. When you connect to the Management Server you do not get a unified view of all logs, as in index mode. On each Log Server, the search is done on one log file at a time." It then documents Logs & Events > Logs > Options > File > Open Log File to pick a file. Option D restates both restrictions: separate connections and one file per search.

Why the others are wrong

  • A. Connecting separately is right, but the search is not across all of that server's files at once; it is one file at a time.
  • B. A single Log Server never automatically searches another server's files; there is no cross-server query without indexing.
  • C. Connecting to the Management Server is precisely what does not give a unified view in non-index mode.

156-588 exam tip

Index mode = unified view from the Management Server. Non-index mode = per-Log-Server, per-file. SmartEvent also requires indexing.

9From an R82 Management Server, an engineer must rotate the active Security log on managed gateway GW1 and copy that newly switched log to the Management Server. The switched file must remain on GW1 as well. SIC is established, and the new name case_01 does not collide with an existing log name. Which command requests the required retention behavior?
  • fw logswitch -h GW1 -case_01
  • fw logswitch -h GW1 case_01
  • fw fetchlogs -f fw.log GW1
  • fw logswitch -h GW1 +case_01
Answer: D

The short version

D — fw logswitch -h GW1 +case_01 copies the switched log locally and leaves it on GW1.

Key concepts in this question

  • fw logswitch closes, renames and recreates the active log on the target.
  • -h <Target> selects the remote server and requires established SIC trust.
  • + copies the switched log to $FWDIR/log/ locally; - transfers it and deletes the remote copy.
  • If a switched-log name is supplied with + or -, it must follow the sign immediately.

Why D is correct

The R82 CLI Reference entry for fw logswitch defines + as: "Specifies to copy the active log from the remote server to the local server", noting that "If you specify the name of the switched log file, you must write it immediately after this + (plus) parameter." Only - deletes the switched file on the remote server. The example fw logswitch -h MyGW + shows the remote file 2018-06-13_185451.log still present on the gateway while MyGW__2018-06-13_185451.log appears on the management server. Option D therefore produces both required effects with a non-colliding name.

Why the others are wrong

  • A. -case_01 is parsed as the transfer-minus form followed by a name, which would delete the switched log on GW1.
  • B. A bare case_01 is the name of the log to switch, not a copy instruction, so nothing is copied locally.
  • C. fw fetchlogs moves logs; it does not perform the log switch that creates the new active log and the named switched file.

156-588 exam tip

+ keeps the remote copy, - removes it, and the name is glued to the sign: +case_01, not + case_01.

10On a standard R82 Security Gateway, an engineer needs to inspect the current SIC trust state. The activation key, certificate trust, and service state must be preserved. Which command is appropriate?
  • cp_conf sic state
  • cp_conf sic init TempKey
  • cp_conf sic init TempKey norestart
  • cp_conf sic cert_pull MGMT1 DynamicGW
Answer: A

The short version

A — cp_conf sic state displays the current SIC trust state without touching the key or services.

Key concepts in this question

  • cp_conf sic on a Security Gateway has three operations: state, init [norestart], and cert_pull.
  • state is read-only and prints a line such as Trust State: Trust established.
  • init resets the one-time activation key and, by default, restarts Check Point services.

Why A is correct

The R82 CLI Reference entry for cp_conf sic lists state with the description "Shows the current state of the SIC Trust" and gives the example output Trust State: Trust established. Because the task requires preserving the activation key, certificate trust and service state, only the read-only query qualifies; it reads the existing trust relationship and changes nothing.

Why the others are wrong

  • B. cp_conf sic init TempKey resets the one-time activation key to TempKey and, without norestart, restarts Check Point services, breaking the preservation requirement.
  • C. init TempKey norestart still replaces the activation key even though it skips the service restart.
  • D. cp_conf sic cert_pull is the DAIP recovery path that pulls a certificate from the Management Server; it alters trust material and is not a status query.

156-588 exam tip

Separate observation from mutation: state observes, init rewrites the key, cert_pull fetches a certificate for DAIP gateways.

Want the full bank of 271 questions for Check Point Certified Troubleshooting Expert – R82 (CCTE)? See all practice exams.