Question 620
An emergency change is proposed for: Operations tries to compare two branches' user traffic but one is managed through a FortiGate secure edge and the other uses FortiClient agents. Which caution is most important for this specific change?
Explanation
Correct Answer
The most relevant caution is that different connection modes do not always produce identical per-user telemetry granularity. The case concerns operations tries to compare two branches' user traffic but one is managed through a FortiGate secure edge and the other uses FortiClient agents. The safer path is to review report data-source definitions, connection modes, and identifiers used for grouping and then, after verification, to build a comparable analysis that identifies the distinct traffic sources and their limitations. This is the closest caution because it addresses the failure mechanism instead of a generic issue from another security workflow.
Incorrect Answers
Comparing unequal user populations can create a misleading growth trend. The check concerns comparing unequal user populations can create a misleading growth trend, not confirming that different connection modes do not always produce identical per-user telemetry granularity.
A threat-only dataset cannot represent all authorized application usage. This assesses a threat-only dataset cannot represent all authorized application usage; it does not determine the reported condition—operations tries to compare two branches' user traffic but one is managed through a FortiGate secure edge and the other uses FortiClient agents.
Successful manual report rendering is not proof that scheduled distribution works. The case-specific requirement is confirming that different connection modes do not always produce identical per-user telemetry granularity, which that option does not establish.