Fortinet FCP_FAZ_AN-7.6 Practice Test 6
Question 50
An analyst is moved to another ADOM and unexpectedly loses visibility into previously assigned security devices. The observed fault is: Putting multiple unrelated customers in an unrestricted context may expose logs to unintended analysts. How should the administrator restore and verify the intended state?
- The corrective action is to use a dashboard widget title as an enforceable access control boundary.
- The corrective action is to disable all ADOM separation because tenant log names look different.
- The corrective action is to move devices into another customer ADOM solely to fix a missing menu item.
- The corrective action is to correct ADOM assignments and verify scoped access with representative users.
Explanation
Correct Answer
D:Recheck Device Manager ADOM membership, administrator scope, authorized devices and positive-negative log access tests.
Incorrect Answers
A:Use a dashboard widget title as an enforceable access control boundary. Putting multiple unrelated customers in an unrestricted context may expose logs to unintended analysts. Instead, correct ADOM assignments and verify scoped access with representative users.
B:Disable all ADOM separation because tenant log names look different. Putting multiple unrelated customers in an unrestricted context may expose logs to unintended analysts. Instead, correct ADOM assignments and verify scoped access with representative users.
C:Move devices into another customer ADOM solely to fix a missing menu item. Putting multiple unrelated customers in an unrestricted context may expose logs to unintended analysts. Instead, correct ADOM assignments and verify scoped access with representative users.
Question 51
A new FortiGate produces traffic but has no records in FortiAnalyzer Log View. Which configuration decision most directly resolves this situation?
- Assume enabling FortiGate firewall policies automatically exports every log.
- Configure the FortiGate logging destination and authorize the correct device on the intended FortiAnalyzer.
- Block the FortiAnalyzer receive path while troubleshooting missing logs.
- Register an unrelated device serial and call the replacement authorized.
Explanation
Correct Answer
B:Verify using FortiGate logging settings, collector address, device registration, receive counters and sample traffic log. Central logging requires sender configuration, network reachability and appropriate collector device authorization.
Incorrect Answers
A:A successful FortiGate policy match does not prove the event reached the FortiAnalyzer. Use configure the FortiGate logging destination and authorize the correct device on the intended FortiAnalyzer.
C:Block the FortiAnalyzer receive path while troubleshooting missing logs. Central logging requires sender configuration, network reachability and appropriate collector device authorization. Relevant observations are FortiGate logging settings, collector address, device registration, receive counters and sample traffic log.
D:A successful FortiGate policy match does not prove the event reached the FortiAnalyzer. The supported correction is configure the FortiGate logging destination and authorize the correct device on the intended FortiAnalyzer.
Question 52
A new FortiGate produces traffic but has no records in FortiAnalyzer Log View. What evidence most strongly confirms the operational condition?
- An appliance name without any current log delivery or synchronization state.
- A marketing diagram with no member API or device log evidence.
- A Fabric dashboard screenshot from a different ADOM with no source records.
- FortiGate logging settings, collector address, device registration, receive counters and sample traffic log.
Explanation
Correct Answer
D:The planned operation is configure the FortiGate logging destination and authorize the correct device on the intended FortiAnalyzer. Central logging requires sender configuration, network reachability and appropriate collector device authorization.
Incorrect Answers
A:An appliance name without any current log delivery or synchronization state. The relevant evidence is FortiGate logging settings, collector address, device registration, receive counters and sample traffic log. Central logging requires sender configuration, network reachability and appropriate collector device authorization.
B:A marketing diagram with no member API or device log evidence. The relevant evidence is FortiGate logging settings, collector address, device registration, receive counters and sample traffic log. Central logging requires sender configuration, network reachability and appropriate collector device authorization.
C:A Fabric dashboard screenshot from a different ADOM with no source records. The relevant evidence is FortiGate logging settings, collector address, device registration, receive counters and sample traffic log. Central logging requires sender configuration, network reachability and appropriate collector device authorization.
Question 53
A new FortiGate produces traffic but has no records in FortiAnalyzer Log View. What FortiAnalyzer behavior explains the correct decision?
- An ADOM display name alone enforces all necessary tenant permissions.
- Central logging requires sender configuration, network reachability and appropriate collector device authorization.
- Fabric supervisor visibility proves it can edit every member and launch all member playbooks.
- Every raw log record is already normalized with identical fields across all sources.
Explanation
Correct Answer
B:Verification depends on FortiGate logging settings, collector address, device registration, receive counters and sample traffic log. This is why configure the FortiGate logging destination and authorize the correct device on the intended FortiAnalyzer.
Incorrect Answers
A:An ADOM display name alone enforces all necessary tenant permissions. That generalization is incorrect in the context of FortiGate logging destination and authorization. The relevant behavior is central logging requires sender configuration, network reachability and appropriate collector device authorization. Check FortiGate logging settings, collector address, device registration, receive counters and sample traffic log.
C:Fabric supervisor visibility proves it can edit every member and launch all member playbooks. That generalization is incorrect in the context of FortiGate logging destination and authorization. The relevant behavior is central logging requires sender configuration, network reachability and appropriate collector device authorization. Check FortiGate logging settings, collector address, device registration, receive counters and sample traffic log.
D:Every raw log record is already normalized with identical fields across all sources. That generalization is incorrect in the context of FortiGate logging destination and authorization. The relevant behavior is central logging requires sender configuration, network reachability and appropriate collector device authorization. Check FortiGate logging settings, collector address, device registration, receive counters and sample traffic log.
Question 54
A new FortiGate produces traffic but has no records in FortiAnalyzer Log View. An operator instead chooses this incorrect shortcut: Assume enabling FortiGate firewall policies automatically exports every log. Which resulting risk should the reviewer identify?
- Reading the Fabric member inventory caused the original log ingestion outage.
- The only impact is a harmless dashboard background color.
- A successful FortiGate policy match does not prove the event reached the FortiAnalyzer.
- An accurate timestamp created all synchronization errors in the member.
Explanation
Correct Answer
C:The intended preventive choice is configure the FortiGate logging destination and authorize the correct device on the intended FortiAnalyzer. Central logging requires sender configuration, network reachability and appropriate collector device authorization.
Incorrect Answers
A:This does not account for the actual FortiGate logging destination and authorization weakness. The more relevant failure is a successful FortiGate policy match does not prove the event reached the FortiAnalyzer.
B:This does not account for the actual FortiGate logging destination and authorization weakness. Confirm with FortiGate logging settings, collector address, device registration, receive counters and sample traffic log.
D:This does not account for the actual FortiGate logging destination and authorization weakness.
Question 55
A new FortiGate produces traffic but has no records in FortiAnalyzer Log View. The observed fault is: A successful FortiGate policy match does not prove the event reached the FortiAnalyzer. How should the administrator restore and verify the intended state?
- Repair sender or registration settings and trace one test log end to end.
- Block the FortiAnalyzer receive path while troubleshooting missing logs.
- Register an unrelated device serial and call the replacement authorized.
- Assume enabling FortiGate firewall policies automatically exports every log.
Explanation
Correct Answer
A:Central logging requires sender configuration, network reachability and appropriate collector device authorization.
Incorrect Answers
B:Block the FortiAnalyzer receive path while troubleshooting missing logs. A successful FortiGate policy match does not prove the event reached the FortiAnalyzer. Instead, repair sender or registration settings and trace one test log end to end.
C:Register an unrelated device serial and call the replacement authorized. A successful FortiGate policy match does not prove the event reached the FortiAnalyzer. Instead, repair sender or registration settings and trace one test log end to end.
D:Assume enabling FortiGate firewall policies automatically exports every log. A successful FortiGate policy match does not prove the event reached the FortiAnalyzer. Instead, repair sender or registration settings and trace one test log end to end.
Question 56
A branch FortiGate was replaced and the replacement sends logs to an old collector address. Which administrator action meets the documented requirement?
- For this FortiAnalyzer investigation, block the FortiAnalyzer receive path while troubleshooting missing logs.
- For this FortiAnalyzer investigation, register an unrelated device serial and call the replacement authorized.
- For this FortiAnalyzer investigation, assume enabling FortiGate firewall policies automatically exports every log.
- For this FortiAnalyzer investigation, configure the FortiGate logging destination and authorize the correct device on the intended FortiAnalyzer.
Explanation
Correct Answer
D:Verify using FortiGate logging settings, collector address, device registration, receive counters and sample traffic log. This is the targeted correction for FortiGate logging destination and authorization.
Incorrect Answers
A:Block the FortiAnalyzer receive path while troubleshooting missing logs. Central logging requires sender configuration, network reachability and appropriate collector device authorization. Relevant observations are FortiGate logging settings, collector address, device registration, receive counters and sample traffic log.
B:A successful FortiGate policy match does not prove the event reached the FortiAnalyzer. Register an unrelated device serial and call the replacement authorized.
C:A successful FortiGate policy match does not prove the event reached the FortiAnalyzer. This change does not provide the specified control.
Question 57
A branch FortiGate was replaced and the replacement sends logs to an old collector address. Which observations should the engineer inspect before declaring success?
- The supporting evidence is a single unrelated ping to the management interface.
- The supporting evidence is FortiGate logging settings, collector address, device registration, receive counters and sample traffic log.
- The supporting evidence is an appliance name without any current log delivery or synchronization state.
- The supporting evidence is a marketing diagram with no member API or device log evidence.
Explanation
Correct Answer
B:The planned operation is configure the FortiGate logging destination and authorize the correct device on the intended FortiAnalyzer. These observations directly test FortiGate logging destination and authorization under the actual system state.
Incorrect Answers
A:A single unrelated ping to the management interface. The relevant evidence is FortiGate logging settings, collector address, device registration, receive counters and sample traffic log. Central logging requires sender configuration, network reachability and appropriate collector device authorization.
C:An appliance name without any current log delivery or synchronization state. The relevant evidence is FortiGate logging settings, collector address, device registration, receive counters and sample traffic log. Central logging requires sender configuration, network reachability and appropriate collector device authorization.
D:A marketing diagram with no member API or device log evidence. The relevant evidence is FortiGate logging settings, collector address, device registration, receive counters and sample traffic log. Central logging requires sender configuration, network reachability and appropriate collector device authorization.
Question 58
A branch FortiGate was replaced and the replacement sends logs to an old collector address. Which platform statement is MOST accurate for this scenario?
- The governing concept is that every raw log record is already normalized with identical fields across all sources.
- The governing concept is that central logging requires sender configuration, network reachability and appropriate collector device authorization.
- The governing concept is that an ADOM display name alone enforces all necessary tenant permissions.
- The governing concept is that any FortiAI suggestion is confirmed without source log evidence.
Explanation
Correct Answer
B:Verification depends on FortiGate logging settings, collector address, device registration, receive counters and sample traffic log. Central logging requires sender configuration, network reachability and appropriate collector device authorization.
Incorrect Answers
A:Every raw log record is already normalized with identical fields across all sources. That generalization is incorrect in the context of FortiGate logging destination and authorization. The relevant behavior is central logging requires sender configuration, network reachability and appropriate collector device authorization. Check FortiGate logging settings, collector address, device registration, receive counters and sample traffic log.
C:An ADOM display name alone enforces all necessary tenant permissions. That generalization is incorrect in the context of FortiGate logging destination and authorization. The relevant behavior is central logging requires sender configuration, network reachability and appropriate collector device authorization. Check FortiGate logging settings, collector address, device registration, receive counters and sample traffic log.
D:Any FortiAI suggestion is confirmed without source log evidence. That generalization is incorrect in the context of FortiGate logging destination and authorization. The relevant behavior is central logging requires sender configuration, network reachability and appropriate collector device authorization. Check FortiGate logging settings, collector address, device registration, receive counters and sample traffic log.
Question 59
A branch FortiGate was replaced and the replacement sends logs to an old collector address. An operator instead chooses this incorrect shortcut: Assume enabling FortiGate firewall policies automatically exports every log. Which consequence BEST explains the flaw in the proposed change?
- The material failure is that an accurate timestamp created all synchronization errors in the member.
- The material failure is that a successful FortiGate policy match does not prove the event reached the FortiAnalyzer.
- The material failure is that maintaining source device provenance itself destroyed the archived log.
- The material failure is that the only impact is a harmless dashboard background color.
Explanation
Correct Answer
B:The intended preventive choice is configure the FortiGate logging destination and authorize the correct device on the intended FortiAnalyzer. A successful FortiGate policy match does not prove the event reached the FortiAnalyzer.
Incorrect Answers
A:This does not account for the actual FortiGate logging destination and authorization weakness. An accurate timestamp created all synchronization errors in the member.
C:This does not account for the actual FortiGate logging destination and authorization weakness. Maintaining source device provenance itself destroyed the archived log.
D:This does not account for the actual FortiGate logging destination and authorization weakness. The only impact is a harmless dashboard background color.
Question 60
A branch FortiGate was replaced and the replacement sends logs to an old collector address. The observed fault is: A successful FortiGate policy match does not prove the event reached the FortiAnalyzer. Which remediation best corrects the root cause?
- The corrective action is to register an unrelated device serial and call the replacement authorized.
- The corrective action is to repair sender or registration settings and trace one test log end to end.
- The corrective action is to assume enabling FortiGate firewall policies automatically exports every log.
- The corrective action is to block the FortiAnalyzer receive path while troubleshooting missing logs.
Explanation
Correct Answer
B:Recheck FortiGate logging settings, collector address, device registration, receive counters and sample traffic log.
Incorrect Answers
A:Register an unrelated device serial and call the replacement authorized. A successful FortiGate policy match does not prove the event reached the FortiAnalyzer. Instead, repair sender or registration settings and trace one test log end to end.
C:Assume enabling FortiGate firewall policies automatically exports every log. A successful FortiGate policy match does not prove the event reached the FortiAnalyzer. Instead, repair sender or registration settings and trace one test log end to end.
D:Block the FortiAnalyzer receive path while troubleshooting missing logs. A successful FortiGate policy match does not prove the event reached the FortiAnalyzer. Instead, repair sender or registration settings and trace one test log end to end.