A FortiSOAR developer is building a connector for a REST API that requires OAuth 2.0 authentication. The connector schema must support token refresh. What is the best way to implement this?

Use the access token only and ignore expiration

Require the user to manually update the token in the playbook

Store the refresh token in the connector configuration and implement a token refresh method

Hardcode the access token in the connector code

A FortiSOAR playbook sends a JSON-RPC request with an 'id' of 5. The response returns with an 'id' of 5 and a 'result' field. What does this indicate?

The response is a successful result for the request with id 5

The response is an error because it includes an id

The server ignored the request and returned a default response

The request was a notification and no response is expected

A FortiSOAR developer is testing a new connector that calls a REST API. The connector works in the development environment but fails in production with HTTP 403 Forbidden. What is the most likely cause?

The production API key lacks the required permissions

The production environment uses a different HTTP method

The production API endpoint is different

A FortiSOAR playbook calls a JSON-RPC method that returns an error. The response includes an error object with code -32601 and message 'Method not found'. What does this indicate?

The client is not authorized to call the method

The request was malformed and could not be parsed

The server encountered an internal error

The requested method does not exist on the server

A FortiSOAR environment has a connector that uses a REST API. The API changes its response format, breaking the connector. What is the best way to prevent this in the future?

Implement versioning in the connector to handle different response formats

Avoid using connectors and use direct API calls

Hardcode the expected response format

FortinetNSE 6 - FortiSOAR Analyst

Domain 4Objective 3

Compare REST API and JSON-RPC API NSE6-FORTISOAR-ANALYST Practice Questions (Page 1)

Part of the APIs and Connectors domain, which accounts for 15-25% of the NSE6-FORTISOAR-ANALYST exam.

25questions here

5free pages

3concepts

15-25%of the exam

Questions 1–5

1expert · hard
A FortiSOAR developer is building a connector for a REST API that requires OAuth 2.0 authentication. The connector schema must support token refresh. What is the best way to implement this?
Select an answer first
2application · medium
A FortiSOAR playbook sends a JSON-RPC request with an 'id' of 5. The response returns with an 'id' of 5 and a 'result' field. What does this indicate?
Select an answer first
3expert · hard
A FortiSOAR developer is testing a new connector that calls a REST API. The connector works in the development environment but fails in production with HTTP 403 Forbidden. What is the most likely cause?
Select an answer first
4application · medium
A FortiSOAR playbook calls a JSON-RPC method that returns an error. The response includes an error object with code -32601 and message 'Method not found'. What does this indicate?
Select an answer first
5expert · hard
A FortiSOAR environment has a connector that uses a REST API. The API changes its response format, breaking the connector. What is the best way to prevent this in the future?
Select an answer first

Finished these 5 questions?

Review the revealed explanations, or continue through the curriculum.

Next 5 questions →Back to NSE6-FORTISOAR-ANALYST

Free Basic Practice is a study aid with revealable answers — not a scored exam. Examers.io is independent and not affiliated with or endorsed by Fortinet. “NSE6-FORTISOAR-ANALYST” is a trademark of its owner, used for identification only.