The exhibit displays a Zero Trust Tagging rule that applies the "Non-compliant" tag to endpoints meeting specific criteria. To make an endpoint compliant, it must not meet these criteria. The rules for being non-compliant are: 1) having high, critical, or medium severity vulnerabilities, 2) having the Web Filter disabled, and 3) running the Calculator application. Therefore, an administrator must patch the specified vulnerabilities and enable the web filter profile to move the endpoint towards a compliant state.

B. Run Calculator application on the endpoint. This action would trigger one of the non-compliant conditions, making the endpoint non-compliant.

C. Integrate FortiSandbox for infected file analysis. This action is irrelevant as FortiSandbox integration is not a condition in the displayed Zero Trust Tagging rule.

FortiClient EMS 7.4 Administration Guide, "Zero Trust Fabric Connectivity," page 111, "Configuring Zero Trust tagging rules." This section details how rules are created based on endpoint state, such as vulnerability status and feature enablement. An endpoint becomes compliant by negating the conditions defined in the non-compliant tagging rule.