Question 1
Original fictional FortiClient EMS 7.4 practice case R181-CASE-001 — Regional hospital expanding its endpoint fleet. Observed evidence: The inventory design assumes EMS must replace every endpoint agent to collect posture. Which focused administrator action best resolves the identified problem while preserving unrelated security controls?
Explanation
Correct Answer
Correct for this fictional case. The distinguishing signal is: The inventory design assumes EMS must replace every endpoint agent to collect posture. It points to: EMS manages FortiClient agents rather than acting as the endpoint-resident protection client. The targeted correction is: Keep FortiClient installed on endpoints and use EMS for centralized policies and inventory. Verify success by checking: The endpoint runs FortiClient while its policy and registration appear in EMS. The response is scoped to this observed failure and should not weaken other policies.
Incorrect Answers
Incorrect for these case facts. This action is more directly suited to another hypothetical case where: The deployment diagram lacks a decision about on-premises versus hosted management connectivity. That case concerns: EMS placement and connectivity requirements are unresolved before rollout. Here the observed distinction is: The inventory design assumes EMS must replace every endpoint agent to collect posture. A more directly targeted response is: Keep FortiClient installed on endpoints and use EMS for centralized policies and inventory.
Incorrect for these case facts. This action is more directly suited to another hypothetical case where: The design treats merely listing an endpoint in EMS as equivalent to granting application access. That case concerns: EMS registration by itself is not a complete authenticated ZTNA authorization decision. Here the observed distinction is: The inventory design assumes EMS must replace every endpoint agent to collect posture. A more directly targeted response is: Keep FortiClient installed on endpoints and use EMS for centralized policies and inventory.
Incorrect for these case facts. This action is more directly suited to another hypothetical case where: Project diagram sends all managed-user application traffic through the EMS administrative console. That case concerns: The EMS management plane is being confused with the endpoint's application data path. Here the observed distinction is: The inventory design assumes EMS must replace every endpoint agent to collect posture. A more directly targeted response is: Keep FortiClient installed on endpoints and use EMS for centralized policies and inventory.