Fortinet FCP_FAZ_AN-7.6 Practice Test 5
Question 40
A multisite SOC design promises direct member configuration editing through the read-focused Fabric supervisor. The observed fault is: Assuming the supervisor can execute unsupported remote member changes can leave containment actions unperformed. Which controlled recovery BEST addresses this failure?
- The corrective action is to replace device-side action evidence with a central dashboard screenshot.
- The corrective action is to mark the playbook successful merely because the central incident is visible.
- The corrective action is to grant a read-only supervisor operator permission to edit all member devices.
- The corrective action is to run the response from a supported member context and verify the device-side result.
Explanation
Correct Answer
D:Recheck supervisor role and module permissions, member automation console and action audit trail.
Incorrect Answers
A:Replace device-side action evidence with a central dashboard screenshot. Assuming the supervisor can execute unsupported remote member changes can leave containment actions unperformed. Instead, run the response from a supported member context and verify the device-side result.
B:Mark the playbook successful merely because the central incident is visible. Assuming the supervisor can execute unsupported remote member changes can leave containment actions unperformed. Instead, run the response from a supported member context and verify the device-side result.
C:Grant a read-only supervisor operator permission to edit all member devices. Assuming the supervisor can execute unsupported remote member changes can leave containment actions unperformed. Instead, run the response from a supported member context and verify the device-side result.
Question 41
A managed security provider needs separate customer log views within one regional FortiAnalyzer. What is the BEST supported implementation or corrective action?
- Disable all ADOM separation because tenant log names look different.
- Move devices into another customer ADOM solely to fix a missing menu item.
- Use a dashboard widget title as an enforceable access control boundary.
- Configure ADOM-specific device assignment and administrator scoping appropriate to the tenant boundary.
Explanation
Correct Answer
D:Verify using Device Manager ADOM membership, administrator scope, authorized devices and positive-negative log access tests. This is the targeted correction for Fabric member ADOM and device scope isolation.
Incorrect Answers
A:Disable all ADOM separation because tenant log names look different. Putting multiple unrelated customers in an unrestricted context may expose logs to unintended analysts. Use configure ADOM-specific device assignment and administrator scoping appropriate to the tenant boundary.
B:Move devices into another customer ADOM solely to fix a missing menu item. ADOM boundaries organize device data and administrative visibility for distinct operational contexts. Relevant observations are Device Manager ADOM membership, administrator scope, authorized devices and positive-negative log access tests.
C:Use a dashboard widget title as an enforceable access control boundary. This leaves the operational requirement unresolved. Putting multiple unrelated customers in an unrestricted context may expose logs to unintended analysts. The supported correction is configure ADOM-specific device assignment and administrator scoping appropriate to the tenant boundary.
Question 42
A managed security provider needs separate customer log views within one regional FortiAnalyzer. Which diagnostic evidence BEST verifies the intended outcome?
- An old inventory list without original event time and device attribution.
- Device Manager ADOM membership, administrator scope, authorized devices and positive-negative log access tests.
- A Fabric dashboard screenshot from a different ADOM with no source records.
- A single unrelated ping to the management interface.
Explanation
Correct Answer
B:These observations directly test Fabric member ADOM and device scope isolation under the actual system state. ADOM boundaries organize device data and administrative visibility for distinct operational contexts.
Incorrect Answers
A:An old inventory list without original event time and device attribution. The relevant evidence is Device Manager ADOM membership, administrator scope, authorized devices and positive-negative log access tests. ADOM boundaries organize device data and administrative visibility for distinct operational contexts.
C:A Fabric dashboard screenshot from a different ADOM with no source records. The relevant evidence is Device Manager ADOM membership, administrator scope, authorized devices and positive-negative log access tests. ADOM boundaries organize device data and administrative visibility for distinct operational contexts.
D:A single unrelated ping to the management interface. The relevant evidence is Device Manager ADOM membership, administrator scope, authorized devices and positive-negative log access tests. ADOM boundaries organize device data and administrative visibility for distinct operational contexts.
Question 43
A managed security provider needs separate customer log views within one regional FortiAnalyzer. Which technical principle BEST explains this result?
- Fabric supervisor visibility proves it can edit every member and launch all member playbooks.
- Any FortiAI suggestion is confirmed without source log evidence.
- A visible device inventory object guarantees current threat log delivery.
- ADOM boundaries organize device data and administrative visibility for distinct operational contexts.
Explanation
Correct Answer
D:Verification depends on Device Manager ADOM membership, administrator scope, authorized devices and positive-negative log access tests. This is why configure ADOM-specific device assignment and administrator scoping appropriate to the tenant boundary.
Incorrect Answers
A:That generalization is incorrect in the context of Fabric member ADOM and device scope isolation. The relevant behavior is ADOM boundaries organize device data and administrative visibility for distinct operational contexts.
B:That generalization is incorrect in the context of Fabric member ADOM and device scope isolation. Check Device Manager ADOM membership, administrator scope, authorized devices and positive-negative log access tests.
C:That generalization is incorrect in the context of Fabric member ADOM and device scope isolation.
Question 44
A managed security provider needs separate customer log views within one regional FortiAnalyzer. An operator instead chooses this incorrect shortcut: Disable all ADOM separation because tenant log names look different. What material failure follows from the mistaken shortcut?
- Maintaining source device provenance itself destroyed the archived log.
- An authorized review of ADOM permissions caused every unrelated FortiGate failure.
- Reading the Fabric member inventory caused the original log ingestion outage.
- Putting multiple unrelated customers in an unrestricted context may expose logs to unintended analysts.
Explanation
Correct Answer
D:The intended preventive choice is configure ADOM-specific device assignment and administrator scoping appropriate to the tenant boundary. ADOM boundaries organize device data and administrative visibility for distinct operational contexts.
Incorrect Answers
A:This does not account for the actual Fabric member ADOM and device scope isolation weakness. The more relevant failure is putting multiple unrelated customers in an unrestricted context may expose logs to unintended analysts.
B:This does not account for the actual Fabric member ADOM and device scope isolation weakness. Confirm with Device Manager ADOM membership, administrator scope, authorized devices and positive-negative log access tests.
C:This does not account for the actual Fabric member ADOM and device scope isolation weakness.
Question 45
A managed security provider needs separate customer log views within one regional FortiAnalyzer. The observed fault is: Putting multiple unrelated customers in an unrestricted context may expose logs to unintended analysts. Which controlled recovery BEST addresses this failure?
- Move devices into another customer ADOM solely to fix a missing menu item.
- Correct ADOM assignments and verify scoped access with representative users.
- Use a dashboard widget title as an enforceable access control boundary.
- Disable all ADOM separation because tenant log names look different.
Explanation
Correct Answer
B:ADOM boundaries organize device data and administrative visibility for distinct operational contexts.
Incorrect Answers
A: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.
C: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.
D: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.
Question 46
An analyst is moved to another ADOM and unexpectedly loses visibility into previously assigned security devices. Which configuration decision most directly resolves this situation?
- For this FortiAnalyzer investigation, move devices into another customer ADOM solely to fix a missing menu item.
- For this FortiAnalyzer investigation, configure ADOM-specific device assignment and administrator scoping appropriate to the tenant boundary.
- For this FortiAnalyzer investigation, use a dashboard widget title as an enforceable access control boundary.
- For this FortiAnalyzer investigation, disable all ADOM separation because tenant log names look different.
Explanation
Correct Answer
B:Verify using Device Manager ADOM membership, administrator scope, authorized devices and positive-negative log access tests. ADOM boundaries organize device data and administrative visibility for distinct operational contexts.
Incorrect Answers
A:Move devices into another customer ADOM solely to fix a missing menu item. ADOM boundaries organize device data and administrative visibility for distinct operational contexts. Relevant observations are Device Manager ADOM membership, administrator scope, authorized devices and positive-negative log access tests.
C:Use a dashboard widget title as an enforceable access control boundary. This leaves the operational requirement unresolved. Putting multiple unrelated customers in an unrestricted context may expose logs to unintended analysts. The supported correction is configure ADOM-specific device assignment and administrator scoping appropriate to the tenant boundary.
D:Disable all ADOM separation because tenant log names look different. Putting multiple unrelated customers in an unrestricted context may expose logs to unintended analysts. Use configure ADOM-specific device assignment and administrator scoping appropriate to the tenant boundary.
Question 47
An analyst is moved to another ADOM and unexpectedly loses visibility into previously assigned security devices. What evidence most strongly confirms the operational condition?
- The supporting evidence is an appliance name without any current log delivery or synchronization state.
- The supporting evidence is an old inventory list without original event time and device attribution.
- The supporting evidence is Device Manager ADOM membership, administrator scope, authorized devices and positive-negative log access tests.
- The supporting evidence is a Fabric dashboard screenshot from a different ADOM with no source records.
Explanation
Correct Answer
C:These observations directly test Fabric member ADOM and device scope isolation under the actual system state. The planned operation is configure ADOM-specific device assignment and administrator scoping appropriate to the tenant boundary.
Incorrect Answers
A:An appliance name without any current log delivery or synchronization state. The relevant evidence is Device Manager ADOM membership, administrator scope, authorized devices and positive-negative log access tests. ADOM boundaries organize device data and administrative visibility for distinct operational contexts.
B:An old inventory list without original event time and device attribution. The relevant evidence is Device Manager ADOM membership, administrator scope, authorized devices and positive-negative log access tests. ADOM boundaries organize device data and administrative visibility for distinct operational contexts.
D:A Fabric dashboard screenshot from a different ADOM with no source records. The relevant evidence is Device Manager ADOM membership, administrator scope, authorized devices and positive-negative log access tests. ADOM boundaries organize device data and administrative visibility for distinct operational contexts.
Question 48
An analyst is moved to another ADOM and unexpectedly loses visibility into previously assigned security devices. What FortiAnalyzer behavior explains the correct decision?
- The governing concept is that a visible device inventory object guarantees current threat log delivery.
- The governing concept is that ADOM boundaries organize device data and administrative visibility for distinct operational contexts.
- The governing concept is that Fabric supervisor visibility proves it can edit every member and launch all member playbooks.
- The governing concept is that every raw log record is already normalized with identical fields across all sources.
Explanation
Correct Answer
B:Verification depends on Device Manager ADOM membership, administrator scope, authorized devices and positive-negative log access tests.
Incorrect Answers
A:That generalization is incorrect in the context of Fabric member ADOM and device scope isolation. A visible device inventory object guarantees current threat log delivery.
C:That generalization is incorrect in the context of Fabric member ADOM and device scope isolation. Fabric supervisor visibility proves it can edit every member and launch all member playbooks.
D:That generalization is incorrect in the context of Fabric member ADOM and device scope isolation. Every raw log record is already normalized with identical fields across all sources.
Question 49
An analyst is moved to another ADOM and unexpectedly loses visibility into previously assigned security devices. An operator instead chooses this incorrect shortcut: Disable all ADOM separation because tenant log names look different. Which resulting risk should the reviewer identify?
- The material failure is that reading the Fabric member inventory caused the original log ingestion outage.
- The material failure is that the only impact is a harmless dashboard background color.
- The material failure is that an authorized review of ADOM permissions caused every unrelated FortiGate failure.
- The material failure is that putting multiple unrelated customers in an unrestricted context may expose logs to unintended analysts.
Explanation
Correct Answer
D:The intended preventive choice is configure ADOM-specific device assignment and administrator scoping appropriate to the tenant boundary.
Incorrect Answers
A:This does not account for the actual Fabric member ADOM and device scope isolation weakness. Reading the Fabric member inventory caused the original log ingestion outage.
B:This does not account for the actual Fabric member ADOM and device scope isolation weakness. The only impact is a harmless dashboard background color.
C:This does not account for the actual Fabric member ADOM and device scope isolation weakness. An authorized review of ADOM permissions caused every unrelated FortiGate failure.
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.