156-215.80 · Question #335
Which method below is NOT one of the ways to communicate using the Management API's?
The correct answer is D. Sending API commands over an http connection using web-services. The Check Point Management API supports three methods of communication, but plain HTTP web-service connections are not one of them - only HTTPS is permitted.
Question
Which method below is NOT one of the ways to communicate using the Management API's?
Options
- ATyping API commands using the "mgmt_cli" command
- BTyping API commands from a dialog box inside the SmartConsole GUI application
- CTyping API commands using Gaia's secure shell (clash)19+
- DSending API commands over an http connection using web-services
How the community answered
(57 responses)- A5% (3)
- B2% (1)
- C2% (1)
- D91% (52)
Why each option
The Check Point Management API supports three methods of communication, but plain HTTP web-service connections are not one of them - only HTTPS is permitted.
mgmt_cli is an official Check Point CLI tool installed on the management server and is a fully documented API communication method.
SmartConsole includes a built-in API terminal dialog that lets administrators run Management API commands interactively from within the GUI.
Gaia's clish (the Gaia OS secure shell environment) supports running mgmt_cli API commands directly, making it a valid communication method.
The Check Point Management API requires all web-service calls to use HTTPS to protect session tokens and management data in transit; plain unencrypted HTTP is explicitly not supported. Permitting HTTP would expose credentials and policy configurations to interception. The three valid methods are the mgmt_cli tool, the SmartConsole GUI API terminal, and Gaia's clish shell.
Concept tested: Check Point Management API supported communication methods
Source: https://sc1.checkpoint.com/documents/latest/APIs/
Topics
Community Discussion
No community discussion yet for this question.