Fortinet FCP_FAZ_AN-7.6 Practice Test 88
Question 870
A playbook suddenly fails after an API credential expires and security staff propose storing the password in logs. The observed fault is: Overprivileged or expired connector credentials create compromise risk and failed responses. What corrective action restores the target behavior with validation?
- The corrective action is to rotate or rescope credentials and retest approved and denied actions.
- The corrective action is to disable authentication to avoid expired credentials.
- The corrective action is to store API tokens in public incident comments for convenient troubleshooting.
- The corrective action is to give every connector global super admin without task analysis.
Explanation
Correct Answer
A:Recheck credential scope, API authorization error, secret storage, rotation log and action test.
Incorrect Answers
B:Disable authentication to avoid expired credentials. Overprivileged or expired connector credentials create compromise risk and failed responses. Instead, rotate or rescope credentials and retest approved and denied actions.
C:Store API tokens in public incident comments for convenient troubleshooting. Overprivileged or expired connector credentials create compromise risk and failed responses. Instead, rotate or rescope credentials and retest approved and denied actions.
D:Give every connector global super admin without task analysis. Overprivileged or expired connector credentials create compromise risk and failed responses. Instead, rotate or rescope credentials and retest approved and denied actions.
Question 871
A newly added external connector exists in inventory but its playbook tasks cannot contact the service. Which FortiAnalyzer analyst action is most appropriate?
- Assume listing a connector in the GUI proves all remote actions will succeed.
- Turn off TLS verification permanently to conceal a wrong certificate.
- Change the playbook name instead of testing endpoint reachability.
- Verify supported connector configuration, enablement, service reachability and authentication independently.
Explanation
Correct Answer
D:Connector registration is not identical to a healthy authenticated path for performing actions. This is the targeted correction for connector enablement and reachability diagnosis.
Incorrect Answers
A:A visible connector object can still fail due to disabled state or network transport. Use verify supported connector configuration, enablement, service reachability and authentication independently.
B:Turn off TLS verification permanently to conceal a wrong certificate. Connector registration is not identical to a healthy authenticated path for performing actions. Relevant observations are connector enabled state, endpoint route, TLS handshake, API response and task output.
C:A visible connector object can still fail due to disabled state or network transport. The supported correction is verify supported connector configuration, enablement, service reachability and authentication independently.
Question 872
A newly added external connector exists in inventory but its playbook tasks cannot contact the service. Which collection of records directly tests the suspected mechanism?
- An automation playbook name with no job history or target outcome.
- A connector icon without authorization or current API response.
- An unrelated incident status with no matching event or task audit.
- Connector enabled state, endpoint route, TLS handshake, API response and task output.
Explanation
Correct Answer
D:Connector registration is not identical to a healthy authenticated path for performing actions. These observations directly test connector enablement and reachability diagnosis under the actual system state.
Incorrect Answers
A:An automation playbook name with no job history or target outcome. The relevant evidence is connector enabled state, endpoint route, TLS handshake, API response and task output. Connector registration is not identical to a healthy authenticated path for performing actions.
B:A connector icon without authorization or current API response. The relevant evidence is connector enabled state, endpoint route, TLS handshake, API response and task output. Connector registration is not identical to a healthy authenticated path for performing actions.
C:An unrelated incident status with no matching event or task audit. The relevant evidence is connector enabled state, endpoint route, TLS handshake, API response and task output. Connector registration is not identical to a healthy authenticated path for performing actions.
Question 873
A newly added external connector exists in inventory but its playbook tasks cannot contact the service. Which implementation principle supports the intended approach?
- A saved playbook without an eligible trigger automatically performs all tasks.
- An incident marked resolved proves a remote firewall policy change succeeded.
- Connector registration is not identical to a healthy authenticated path for performing actions.
- A delivered notification email always means the remote endpoint was quarantined.
Explanation
Correct Answer
C:Verification depends on connector enabled state, endpoint route, TLS handshake, API response and task output. This is why verify supported connector configuration, enablement, service reachability and authentication independently.
Incorrect Answers
A:A saved playbook without an eligible trigger automatically performs all tasks. That generalization is incorrect in the context of connector enablement and reachability diagnosis. The relevant behavior is connector registration is not identical to a healthy authenticated path for performing actions. Check connector enabled state, endpoint route, TLS handshake, API response and task output.
B:An incident marked resolved proves a remote firewall policy change succeeded. That generalization is incorrect in the context of connector enablement and reachability diagnosis. The relevant behavior is connector registration is not identical to a healthy authenticated path for performing actions. Check connector enabled state, endpoint route, TLS handshake, API response and task output.
D:A delivered notification email always means the remote endpoint was quarantined. That generalization is incorrect in the context of connector enablement and reachability diagnosis. The relevant behavior is connector registration is not identical to a healthy authenticated path for performing actions. Check connector enabled state, endpoint route, TLS handshake, API response and task output.
Question 874
A newly added external connector exists in inventory but its playbook tasks cannot contact the service. An operator instead chooses this incorrect shortcut: Assume listing a connector in the GUI proves all remote actions will succeed. What technical weakness does this incorrect change introduce?
- An accurate incident assignment caused the missing log source.
- Reviewing the playbook job result caused the original malicious event.
- A visible connector object can still fail due to disabled state or network transport.
- The only effect is a cosmetic incident title change.
Explanation
Correct Answer
C:The intended preventive choice is verify supported connector configuration, enablement, service reachability and authentication independently. Connector registration is not identical to a healthy authenticated path for performing actions.
Incorrect Answers
A:This does not account for the actual connector enablement and reachability diagnosis weakness. The more relevant failure is a visible connector object can still fail due to disabled state or network transport.
B:This does not account for the actual connector enablement and reachability diagnosis weakness. Confirm with connector enabled state, endpoint route, TLS handshake, API response and task output.
D:This does not account for the actual connector enablement and reachability diagnosis weakness. The only effect is a cosmetic incident title change.
Question 875
A newly added external connector exists in inventory but its playbook tasks cannot contact the service. The observed fault is: A visible connector object can still fail due to disabled state or network transport. What corrective action restores the target behavior with validation?
- Restore connector connectivity or credentials and verify a harmless test call.
- Turn off TLS verification permanently to conceal a wrong certificate.
- Change the playbook name instead of testing endpoint reachability.
- Assume listing a connector in the GUI proves all remote actions will succeed.
Explanation
Correct Answer
A:This fixes the described operational problem with observable validation. Connector registration is not identical to a healthy authenticated path for performing actions.
Incorrect Answers
B:Turn off TLS verification permanently to conceal a wrong certificate. A visible connector object can still fail due to disabled state or network transport. Instead, restore connector connectivity or credentials and verify a harmless test call.
C:Change the playbook name instead of testing endpoint reachability. A visible connector object can still fail due to disabled state or network transport. Instead, restore connector connectivity or credentials and verify a harmless test call.
D:Assume listing a connector in the GUI proves all remote actions will succeed. A visible connector object can still fail due to disabled state or network transport. Instead, restore connector connectivity or credentials and verify a harmless test call.
Question 876
A fabric automation connector reports offline after a network route change despite correct credentials. What is the BEST supported implementation or corrective action?
- For this FortiAnalyzer investigation, turn off TLS verification permanently to conceal a wrong certificate.
- For this FortiAnalyzer investigation, change the playbook name instead of testing endpoint reachability.
- For this FortiAnalyzer investigation, assume listing a connector in the GUI proves all remote actions will succeed.
- For this FortiAnalyzer investigation, verify supported connector configuration, enablement, service reachability and authentication independently.
Explanation
Correct Answer
D:Connector registration is not identical to a healthy authenticated path for performing actions. Verify using connector enabled state, endpoint route, TLS handshake, API response and task output.
Incorrect Answers
A:Turn off TLS verification permanently to conceal a wrong certificate. Connector registration is not identical to a healthy authenticated path for performing actions. Relevant observations are connector enabled state, endpoint route, TLS handshake, API response and task output.
B:A visible connector object can still fail due to disabled state or network transport. Change the playbook name instead of testing endpoint reachability.
C:A visible connector object can still fail due to disabled state or network transport. This change does not provide the specified control.
Question 877
A fabric automation connector reports offline after a network route change despite correct credentials. Which diagnostic evidence BEST verifies the intended outcome?
- The supporting evidence is a severity label without source evidence and affected asset identity.
- The supporting evidence is an automation playbook name with no job history or target outcome.
- The supporting evidence is connector enabled state, endpoint route, TLS handshake, API response and task output.
- The supporting evidence is a connector icon without authorization or current API response.
Explanation
Correct Answer
C:Connector registration is not identical to a healthy authenticated path for performing actions. The planned operation is verify supported connector configuration, enablement, service reachability and authentication independently.
Incorrect Answers
A:A severity label without source evidence and affected asset identity. The relevant evidence is connector enabled state, endpoint route, TLS handshake, API response and task output. Connector registration is not identical to a healthy authenticated path for performing actions.
B:An automation playbook name with no job history or target outcome. The relevant evidence is connector enabled state, endpoint route, TLS handshake, API response and task output. Connector registration is not identical to a healthy authenticated path for performing actions.
D:A connector icon without authorization or current API response. The relevant evidence is connector enabled state, endpoint route, TLS handshake, API response and task output. Connector registration is not identical to a healthy authenticated path for performing actions.
Question 878
A fabric automation connector reports offline after a network route change despite correct credentials. Which technical principle BEST explains this result?
- The governing concept is that a delivered notification email always means the remote endpoint was quarantined.
- The governing concept is that a saved playbook without an eligible trigger automatically performs all tasks.
- The governing concept is that connector registration is not identical to a healthy authenticated path for performing actions.
- The governing concept is that a connector listed in inventory always has valid permissions and network reachability.
Explanation
Correct Answer
C:Verification depends on connector enabled state, endpoint route, TLS handshake, API response and task output. Connector registration is not identical to a healthy authenticated path for performing actions.
Incorrect Answers
A:A delivered notification email always means the remote endpoint was quarantined. That generalization is incorrect in the context of connector enablement and reachability diagnosis. The relevant behavior is connector registration is not identical to a healthy authenticated path for performing actions. Check connector enabled state, endpoint route, TLS handshake, API response and task output.
B:A saved playbook without an eligible trigger automatically performs all tasks. That generalization is incorrect in the context of connector enablement and reachability diagnosis. The relevant behavior is connector registration is not identical to a healthy authenticated path for performing actions. Check connector enabled state, endpoint route, TLS handshake, API response and task output.
D:A connector listed in inventory always has valid permissions and network reachability. That generalization is incorrect in the context of connector enablement and reachability diagnosis. The relevant behavior is connector registration is not identical to a healthy authenticated path for performing actions. Check connector enabled state, endpoint route, TLS handshake, API response and task output.
Question 879
A fabric automation connector reports offline after a network route change despite correct credentials. An operator instead chooses this incorrect shortcut: Assume listing a connector in the GUI proves all remote actions will succeed. What material failure follows from the mistaken shortcut?
- The material failure is that the only effect is a cosmetic incident title change.
- The material failure is that an approved narrow connector scope caused every unrelated Internet outage.
- The material failure is that a visible connector object can still fail due to disabled state or network transport.
- The material failure is that reviewing the playbook job result caused the original malicious event.
Explanation
Correct Answer
C:The intended preventive choice is verify supported connector configuration, enablement, service reachability and authentication independently. A visible connector object can still fail due to disabled state or network transport.
Incorrect Answers
A:This does not account for the actual connector enablement and reachability diagnosis weakness. In this specific situation, a fabric automation connector reports offline after a network route change despite correct credentials.
B:This does not account for the actual connector enablement and reachability diagnosis weakness. An approved narrow connector scope caused every unrelated Internet outage.
D:This does not account for the actual connector enablement and reachability diagnosis weakness. Reviewing the playbook job result caused the original malicious event.
Question 880
A fabric automation connector reports offline after a network route change despite correct credentials. The observed fault is: A visible connector object can still fail due to disabled state or network transport. Which controlled recovery BEST addresses this failure?
- The corrective action is to change the playbook name instead of testing endpoint reachability.
- The corrective action is to restore connector connectivity or credentials and verify a harmless test call.
- The corrective action is to assume listing a connector in the GUI proves all remote actions will succeed.
- The corrective action is to turn off TLS verification permanently to conceal a wrong certificate.
Explanation
Correct Answer
B:Recheck connector enabled state, endpoint route, TLS handshake, API response and task output.
Incorrect Answers
A:Change the playbook name instead of testing endpoint reachability. A visible connector object can still fail due to disabled state or network transport. Instead, restore connector connectivity or credentials and verify a harmless test call.
C:Assume listing a connector in the GUI proves all remote actions will succeed. A visible connector object can still fail due to disabled state or network transport. Instead, restore connector connectivity or credentials and verify a harmless test call.
D:Turn off TLS verification permanently to conceal a wrong certificate. A visible connector object can still fail due to disabled state or network transport. Instead, restore connector connectivity or credentials and verify a harmless test call.
