10 free sample questions from a bank of 271, with the correct answers and explanations. No signup required — start practising right now.
C — Run cpview -t to open History mode and then press t to type the incident timestamp.
cpview -t / cpview --history opens the stored CPView database (in R82, /var/log/CPView_history/CPViewDB.dat) instead of the live counters.-t; it must be entered from inside History mode.[Jan...Dec] [01...31] [4-digit Year] [hh:mm:ss], and R81.10 and higher also accept partial values such as Jan 02.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.
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.R is the refresh-rate control, not the timestamp prompt.cpview -t is right, but R again opens the refresh-rate window instead of asking for a date and time.Keep the two keys separate: t = timestamp prompt, R = refresh rate. History mode is the only place t, + and - operate.
A — With a 120-second refresh interval, one press of + moves from 14:15:00 to 14:17:00.
+ advances to the next stored timestamp and - returns to the previous one.R key, not a fixed one-minute step.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.
- key produces, because it subtracts one refresh interval instead of adding one.Read the refresh rate before doing the arithmetic. + and - are relative to whatever R shows, while t jumps to an absolute date and time.
C — cpview --services stat reports the Database and SNMP service status without changing it.
cpview -s / cpview --services administers the CPView services that handle Database and SNMP activity.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.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.
on enables the services; it may change state and does not simply report it.off disables the services, which directly violates the requirement to preserve service state.Do not confuse --services (Database and SNMP) with --api_service (the CPView API). Both use on | off | stat, but they control different daemons.
C — With Management server only selected, the only permitted origin is mgmt_cli on the Management Server command line.
mgmt_cli is the local tool; mgmt_cli.exe is the SmartConsole-shipped Windows tool; Web services use https://<server>/web_api/.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.
mgmt_cli.exe runs on a remote Windows host, so the request does not originate on the Management Server.Remember the pairing: Management server only = local mgmt_cli only. Trusted Clients becomes relevant only after you widen access.
A — The administrator's Permission Profile must have Management API Login selected under its Management permissions.
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 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.
When an API login is refused, check in this order: api status, access setting, then Permission Profile > Management > Management API Login.
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.
api status prints an overall status and a Processes table with Name, State, PID and More Information columns.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.
Quote-level facts like the 200-Trusted-Clients threshold are worth memorizing verbatim; the exam tests the exact access mode plus the exact comparison.
C — Run Install Database on the remote Log Server, and install the policy on the gateway.
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.
Pair the verb with the object: Install Database = server objects; Install Policy = enforcing gateways. A log-destination change needs one of each.
D — Connect to each Log Server separately and open one log file at a time to search it.
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.
Index mode = unified view from the Management Server. Non-index mode = per-Log-Server, per-file. SmartEvent also requires indexing.
D — fw logswitch -h GW1 +case_01 copies the switched log locally and leaves it on GW1.
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.+ or -, it must follow the sign immediately.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.
-case_01 is parsed as the transfer-minus form followed by a name, which would delete the switched log on GW1.case_01 is the name of the log to switch, not a copy instruction, so nothing is copied locally.fw fetchlogs moves logs; it does not perform the log switch that creates the new active log and the named switched file.+ keeps the remote copy, - removes it, and the name is glued to the sign: +case_01, not + case_01.
A — cp_conf sic state displays the current SIC trust state without touching the key or services.
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.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.
cp_conf sic init TempKey resets the one-time activation key to TempKey and, without norestart, restarts Check Point services, breaking the preservation requirement.init TempKey norestart still replaces the activation key even though it skips the service restart.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.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.