Question 140
At fictional Dovetail University, an endpoint security engineer responsible for student devices is reviewing endpoint provisioning, security modules and profile delivery during a security policy acceptance test (FCT-7.4-2.2-035). The observed endpoint management issue is: An EMS administrator revises an assigned Vulnerability Scan profile but believes a lack of immediate client change proves the agent is broken. Which corrective engineering action best addresses the specific problem?
Explanation
Correct Answer
The targeted correction is to inspect endpoint telemetry freshness, sync timing and the actual applied configuration before escalating. The diagnosed issue is: An EMS administrator revises an assigned Vulnerability Scan profile but believes a lack of immediate client change proves the agent is broken. Evidence of success is: After normal supported synchronization the endpoint reports the intended scan settings. The underlying endpoint-security principle is that eMS profile changes propagate through the managed telemetry and policy evaluation lifecycle.
Incorrect Answers
“Stage endpoint software distribution and use supported network-aware deployment windows and caching where applicable” would address a different implementation objective; the stated problem is an EMS administrator revises an assigned Vulnerability Scan profile but believes a lack of immediate client change proves the agent is broken. The actual control boundary is eMS profile changes propagate through the managed telemetry and policy evaluation lifecycle. The directly responsive action is “Inspect endpoint telemetry freshness, sync timing and the actual applied configuration before escalating”.
“Validate FortiGuard reachability and the supported signature or engine update path for managed endpoints” would address a different implementation objective; the stated problem is an EMS administrator revises an assigned Vulnerability Scan profile but believes a lack of immediate client change proves the agent is broken. The actual control boundary is eMS profile changes propagate through the managed telemetry and policy evaluation lifecycle. The directly responsive action is “Inspect endpoint telemetry freshness, sync timing and the actual applied configuration before escalating”.
“Configure the supported remote-access profile then validate VPN establishment and routing from a managed endpoint” would address a different implementation objective; the stated problem is an EMS administrator revises an assigned Vulnerability Scan profile but believes a lack of immediate client change proves the agent is broken. The actual control boundary is eMS profile changes propagate through the managed telemetry and policy evaluation lifecycle. The directly responsive action is “Inspect endpoint telemetry freshness, sync timing and the actual applied configuration before escalating”.