Fortinet FCP_FAZ_AN-7.6 Practice Test 15
Question 140
An SOC workload has daily bursts exceeding planned log storage despite normal average volume. The observed fault is: Underestimated peak rates can prematurely evict evidence needed for investigations. Which remediation best corrects the root cause?
- The corrective action is to adjust quotas or capacity with monitoring and confirm coverage over representative peak days.
- The corrective action is to increase the browser session timeout as a substitute for storage capacity.
- The corrective action is to assume the number of managed devices directly equals log bytes per day.
- The corrective action is to disable all log retention alerts so capacity appears stable.
Explanation
Correct Answer
A:Recheck log rate trend, disk capacity, quota assignments, retention rollover and projected days.
Incorrect Answers
B:Increase the browser session timeout as a substitute for storage capacity. Underestimated peak rates can prematurely evict evidence needed for investigations. Instead, adjust quotas or capacity with monitoring and confirm coverage over representative peak days.
C:Assume the number of managed devices directly equals log bytes per day. Underestimated peak rates can prematurely evict evidence needed for investigations. Instead, adjust quotas or capacity with monitoring and confirm coverage over representative peak days.
D:Disable all log retention alerts so capacity appears stable. Underestimated peak rates can prematurely evict evidence needed for investigations. Instead, adjust quotas or capacity with monitoring and confirm coverage over representative peak days.
Question 141
A downstream SOC service is unavailable and forwarded logs exceed the local buffer. Which administrator action meets the documented requirement?
- Assume a forwarding cache preserves infinite log history.
- Disable source collection because the downstream peer is temporarily unreachable.
- Change the remote service display name instead of testing its receive path.
- Configure supported log forwarding and an adequately sized cache matched to outages and measured log volume.
Explanation
Correct Answer
D:Verify using forwarding peer status, buffer size, queue saturation, dropped log counters and resume tests. This is the targeted correction for log forwarding destination and cache during disconnection.
Incorrect Answers
A:A full cache may drop records during prolonged downstream disconnects. Use configure supported log forwarding and an adequately sized cache matched to outages and measured log volume.
B:Disable source collection because the downstream peer is temporarily unreachable. Forwarding resilience is bounded by cache capacity and source ingestion rate. Relevant observations are forwarding peer status, buffer size, queue saturation, dropped log counters and resume tests.
C:A full cache may drop records during prolonged downstream disconnects. The supported correction is configure supported log forwarding and an adequately sized cache matched to outages and measured log volume.
Question 142
A downstream SOC service is unavailable and forwarded logs exceed the local buffer. Which observations should the engineer inspect before declaring success?
- An old inventory list without original event time and device attribution.
- A Fabric dashboard screenshot from a different ADOM with no source records.
- Forwarding peer status, buffer size, queue saturation, dropped log counters and resume tests.
- A single unrelated ping to the management interface.
Explanation
Correct Answer
C:These observations directly test log forwarding destination and cache during disconnection under the actual system state. Forwarding resilience is bounded by cache capacity and source ingestion rate.
Incorrect Answers
A:An old inventory list without original event time and device attribution. The relevant evidence is forwarding peer status, buffer size, queue saturation, dropped log counters and resume tests. Forwarding resilience is bounded by cache capacity and source ingestion rate.
B:A Fabric dashboard screenshot from a different ADOM with no source records. The relevant evidence is forwarding peer status, buffer size, queue saturation, dropped log counters and resume tests. Forwarding resilience is bounded by cache capacity and source ingestion rate.
D:A single unrelated ping to the management interface. The relevant evidence is forwarding peer status, buffer size, queue saturation, dropped log counters and resume tests. Forwarding resilience is bounded by cache capacity and source ingestion rate.
Question 143
A downstream SOC service is unavailable and forwarded logs exceed the local buffer. Which platform statement is MOST accurate for this scenario?
- Forwarding resilience is bounded by cache capacity and source ingestion rate.
- 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.
Explanation
Correct Answer
A:Verification depends on forwarding peer status, buffer size, queue saturation, dropped log counters and resume tests. This is why configure supported log forwarding and an adequately sized cache matched to outages and measured log volume.
Incorrect Answers
B:That generalization is incorrect in the context of log forwarding destination and cache during disconnection. The relevant behavior is forwarding resilience is bounded by cache capacity and source ingestion rate.
C:That generalization is incorrect in the context of log forwarding destination and cache during disconnection. Check forwarding peer status, buffer size, queue saturation, dropped log counters and resume tests.
D:That generalization is incorrect in the context of log forwarding destination and cache during disconnection. A visible device inventory object guarantees current threat log delivery.
Question 144
A downstream SOC service is unavailable and forwarded logs exceed the local buffer. An operator instead chooses this incorrect shortcut: Assume a forwarding cache preserves infinite log history. Which consequence BEST explains the flaw in the proposed change?
- 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.
- A full cache may drop records during prolonged downstream disconnects.
Explanation
Correct Answer
D:The intended preventive choice is configure supported log forwarding and an adequately sized cache matched to outages and measured log volume. Forwarding resilience is bounded by cache capacity and source ingestion rate.
Incorrect Answers
A:This does not account for the actual log forwarding destination and cache during disconnection weakness. The more relevant failure is a full cache may drop records during prolonged downstream disconnects.
B:This does not account for the actual log forwarding destination and cache during disconnection weakness. Confirm with forwarding peer status, buffer size, queue saturation, dropped log counters and resume tests.
C:This does not account for the actual log forwarding destination and cache during disconnection weakness. Reading the Fabric member inventory caused the original log ingestion outage.
Question 145
A downstream SOC service is unavailable and forwarded logs exceed the local buffer. The observed fault is: A full cache may drop records during prolonged downstream disconnects. Which remediation best corrects the root cause?
- Disable source collection because the downstream peer is temporarily unreachable.
- Restore forwarding and compare source and receiver coverage while recalculating buffer sizing.
- Change the remote service display name instead of testing its receive path.
- Assume a forwarding cache preserves infinite log history.
Explanation
Correct Answer
B:This fixes the described operational problem with observable validation. Forwarding resilience is bounded by cache capacity and source ingestion rate.
Incorrect Answers
A:Disable source collection because the downstream peer is temporarily unreachable. A full cache may drop records during prolonged downstream disconnects. Instead, restore forwarding and compare source and receiver coverage while recalculating buffer sizing.
C:Change the remote service display name instead of testing its receive path. A full cache may drop records during prolonged downstream disconnects. Instead, restore forwarding and compare source and receiver coverage while recalculating buffer sizing.
D:Assume a forwarding cache preserves infinite log history. A full cache may drop records during prolonged downstream disconnects. Instead, restore forwarding and compare source and receiver coverage while recalculating buffer sizing.
Question 146
A security team has a forwarding outage and expects unlimited replay of messages from a fixed cache. Which FortiAnalyzer analyst action is most appropriate?
- For this FortiAnalyzer investigation, configure supported log forwarding and an adequately sized cache matched to outages and measured log volume.
- For this FortiAnalyzer investigation, disable source collection because the downstream peer is temporarily unreachable.
- For this FortiAnalyzer investigation, change the remote service display name instead of testing its receive path.
- For this FortiAnalyzer investigation, assume a forwarding cache preserves infinite log history.
Explanation
Correct Answer
A:Verify using forwarding peer status, buffer size, queue saturation, dropped log counters and resume tests. Forwarding resilience is bounded by cache capacity and source ingestion rate.
Incorrect Answers
B:Disable source collection because the downstream peer is temporarily unreachable. Forwarding resilience is bounded by cache capacity and source ingestion rate. Relevant observations are forwarding peer status, buffer size, queue saturation, dropped log counters and resume tests.
C:A full cache may drop records during prolonged downstream disconnects. Change the remote service display name instead of testing its receive path.
D:A full cache may drop records during prolonged downstream disconnects. This change does not provide the specified control.
Question 147
A security team has a forwarding outage and expects unlimited replay of messages from a fixed cache. Which collection of records directly tests the suspected mechanism?
- The supporting evidence is an appliance name without any current log delivery or synchronization state.
- The supporting evidence is forwarding peer status, buffer size, queue saturation, dropped log counters and resume tests.
- The supporting evidence is an old inventory list without original event time and device attribution.
- The supporting evidence is a Fabric dashboard screenshot from a different ADOM with no source records.
Explanation
Correct Answer
B:These observations directly test log forwarding destination and cache during disconnection under the actual system state. The planned operation is configure supported log forwarding and an adequately sized cache matched to outages and measured log volume.
Incorrect Answers
A:An appliance name without any current log delivery or synchronization state. The relevant evidence is forwarding peer status, buffer size, queue saturation, dropped log counters and resume tests. Forwarding resilience is bounded by cache capacity and source ingestion rate.
C:An old inventory list without original event time and device attribution. The relevant evidence is forwarding peer status, buffer size, queue saturation, dropped log counters and resume tests. Forwarding resilience is bounded by cache capacity and source ingestion rate.
D:A Fabric dashboard screenshot from a different ADOM with no source records. The relevant evidence is forwarding peer status, buffer size, queue saturation, dropped log counters and resume tests. Forwarding resilience is bounded by cache capacity and source ingestion rate.
Question 148
A security team has a forwarding outage and expects unlimited replay of messages from a fixed cache. Which implementation principle supports the intended approach?
- The governing concept is that forwarding resilience is bounded by cache capacity and source ingestion rate.
- The governing concept is that a visible device inventory object guarantees current threat log delivery.
- 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
A:Verification depends on forwarding peer status, buffer size, queue saturation, dropped log counters and resume tests.
Incorrect Answers
B:That generalization is incorrect in the context of log forwarding destination and cache during disconnection.
C:That generalization is incorrect in the context of log forwarding destination and cache during disconnection. Fabric supervisor visibility proves it can edit every member and launch all member playbooks.
D:That generalization is incorrect in the context of log forwarding destination and cache during disconnection. Every raw log record is already normalized with identical fields across all sources.
Question 149
A security team has a forwarding outage and expects unlimited replay of messages from a fixed cache. An operator instead chooses this incorrect shortcut: Assume a forwarding cache preserves infinite log history. What technical weakness does this incorrect change introduce?
- 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 a full cache may drop records during prolonged downstream disconnects.
Explanation
Correct Answer
D:The intended preventive choice is configure supported log forwarding and an adequately sized cache matched to outages and measured log volume. A full cache may drop records during prolonged downstream disconnects.
Incorrect Answers
A:This does not account for the actual log forwarding destination and cache during disconnection weakness.
B:This does not account for the actual log forwarding destination and cache during disconnection weakness. The only impact is a harmless dashboard background color.
C:This does not account for the actual log forwarding destination and cache during disconnection weakness. An authorized review of ADOM permissions caused every unrelated FortiGate failure.
Question 150
A security team has a forwarding outage and expects unlimited replay of messages from a fixed cache. The observed fault is: A full cache may drop records during prolonged downstream disconnects. What corrective action restores the target behavior with validation?
- The corrective action is to change the remote service display name instead of testing its receive path.
- The corrective action is to restore forwarding and compare source and receiver coverage while recalculating buffer sizing.
- The corrective action is to assume a forwarding cache preserves infinite log history.
- The corrective action is to disable source collection because the downstream peer is temporarily unreachable.
Explanation
Correct Answer
B:Recheck forwarding peer status, buffer size, queue saturation, dropped log counters and resume tests.
Incorrect Answers
A:Change the remote service display name instead of testing its receive path. A full cache may drop records during prolonged downstream disconnects. Instead, restore forwarding and compare source and receiver coverage while recalculating buffer sizing.
C:Assume a forwarding cache preserves infinite log history. A full cache may drop records during prolonged downstream disconnects. Instead, restore forwarding and compare source and receiver coverage while recalculating buffer sizing.
D:Disable source collection because the downstream peer is temporarily unreachable. A full cache may drop records during prolonged downstream disconnects. Instead, restore forwarding and compare source and receiver coverage while recalculating buffer sizing.