Fortinet FCP_FCT_AD-7.4 Practice Test 20
Question 190
A FortiClient EMS administrator prepares a focused response to this scenario. A deployment team turns on a strict web filter across all branches and has no change owner or recovery condition when users lose access. Which TWO complementary steps combine the most appropriate action and direct verification? Select TWO answers.
- Test the specified EMS FQDN, TLS connection, network ACL and certificate from the problem endpoint's location.
- Validate the health of the EMS application service and its database separately when management state or inventory becomes inconsistent.
- Compare the approved baseline, one representative endpoint policy, a Telemetry session, feature operation and rollback evidence.
- Compare endpoint platform, exact FortiClient release, supported remediation options and incident playbook expectations.
- Stage a representative pilot of FortiClient registration, profile enforcement, Fabric integration and change rollback before broad rollout.
Explanation
Correct Answers
C:The discriminating evidence is: Compare the approved baseline, one representative endpoint policy, a Telemetry session, feature operation and rollback evidence.
E:The targeted next step is: Stage a representative pilot of FortiClient registration, profile enforcement, Fabric integration and change rollback before broad rollout.
Incorrect Answers
A:This evidence belongs to the distinct FortiClient EMS topic Remote EMS registration and DNS path failures, not the case-specific issue of Controlled EMS initial pilot and rollback decision described here (A deployment team turns on a strict web filter across all branches and has no change owner or recovery condition when users lose access.).
B:This action belongs to the distinct FortiClient EMS topic FortiClient EMS server and database component boundaries, not the case-specific issue of Controlled EMS initial pilot and rollback decision described here (A deployment team turns on a strict web filter across all branches and has no change owner or recovery condition when users lose access.). The targeted action for this case is: Stage a representative pilot of FortiClient registration, profile enforcement, Fabric integration and change rollback before broad rollout.
D:This evidence belongs to the distinct FortiClient EMS topic Unsupported-platform quarantine caveat, not the case-specific issue of Controlled EMS initial pilot and rollback decision described here (A deployment team turns on a strict web filter across all branches and has no change owner or recovery condition when users lose access.).
Question 191
A FortiClient EMS 7.4 administrator investigates this endpoint management case: An administrator changes the endpoint policy hierarchy during an upgrade but cannot explain why several machines changed settings. Which is the most appropriate FIRST action to address the issue? Select ONE best answer.
- Keep endpoint policy administration in EMS while using FortiGate enforcement as an independent network security boundary.
- Group devices by supported Windows, macOS or Linux capabilities and stage compatible FortiClient deployment packages.
- Maintain a patch and configuration change process that records administrative actions and validates endpoint management after maintenance.
- Trace an endpoint's EMS group conditions and effective policy before editing a profile that other users rely on.
Explanation
Correct Answer
C:The targeted next step is: Maintain a patch and configuration change process that records administrative actions and validates endpoint management after maintenance. The supporting FortiClient EMS principle is: Regular security updates and approved access changes need post-change validation; logs and baseline comparisons support root-cause analysis.
Incorrect Answers
A:This action belongs to the distinct FortiClient EMS topic Security Fabric endpoint profile versus network access ownership, not the case-specific issue of EMS patching administration and operational audit described here (An administrator changes the endpoint policy hierarchy during an upgrade but cannot explain why several machines changed settings.). The targeted action for this case is: Maintain a patch and configuration change process that records administrative actions and validates endpoint management after maintenance.
B:This action belongs to the distinct FortiClient EMS topic Endpoint operating-system support during mass provisioning, not the case-specific issue of EMS patching administration and operational audit described here (An administrator changes the endpoint policy hierarchy during an upgrade but cannot explain why several machines changed settings.). The targeted action for this case is: Maintain a patch and configuration change process that records administrative actions and validates endpoint management after maintenance.
D:This action belongs to the distinct FortiClient EMS topic Profile assignment and unexpected group membership diagnosis, not the case-specific issue of EMS patching administration and operational audit described here (An administrator changes the endpoint policy hierarchy during an upgrade but cannot explain why several machines changed settings.). The targeted action for this case is: Maintain a patch and configuration change process that records administrative actions and validates endpoint management after maintenance.
Question 192
An endpoint security reviewer examines this scenario. An administrator changes the endpoint policy hierarchy during an upgrade but cannot explain why several machines changed settings. The proposed action is: Maintain a patch and configuration change process that records administrative actions and validates endpoint management after maintenance. Which technical principle BEST supports that decision? Select ONE best answer.
- Regular security updates and approved access changes need post-change validation; logs and baseline comparisons support root-cause analysis.
- Management and endpoint communication services require deliberate, documented access paths; exposing every EMS service to the public Internet is not necessary.
- FortiClient feature support and policy enforcement can differ across Windows, macOS and Linux, so a universal profile assumption is unsafe.
- Successful service installation alone is insufficient; a pilot must verify endpoint management and the real protected traffic path.
Explanation
Correct Answer
A:Regular security updates and approved access changes need post-change validation; logs and baseline comparisons support root-cause analysis. Applied to this case (An administrator changes the endpoint policy hierarchy during an upgrade but cannot explain why several machines changed settings.), it supports the controlled action: Maintain a patch and configuration change process that records administrative actions and validates endpoint management after maintenance.
Incorrect Answers
B:This principle belongs to the distinct FortiClient EMS topic EMS server configuration and secure administrator access, not the case-specific issue of EMS patching administration and operational audit described here (An administrator changes the endpoint policy hierarchy during an upgrade but cannot explain why several machines changed settings.). The targeted action for this case is: Maintain a patch and configuration change process that records administrative actions and validates endpoint management after maintenance.
C:This principle belongs to the distinct FortiClient EMS topic FortiClient platform capability differences, not the case-specific issue of EMS patching administration and operational audit described here (An administrator changes the endpoint policy hierarchy during an upgrade but cannot explain why several machines changed settings.). The targeted action for this case is: Maintain a patch and configuration change process that records administrative actions and validates endpoint management after maintenance.
D:This principle belongs to the distinct FortiClient EMS topic Controlled EMS initial pilot and rollback decision, not the case-specific issue of EMS patching administration and operational audit described here (An administrator changes the endpoint policy hierarchy during an upgrade but cannot explain why several machines changed settings.). The targeted action for this case is: Maintain a patch and configuration change process that records administrative actions and validates endpoint management after maintenance.
Question 193
A Fortinet security engineer needs objective troubleshooting evidence for this scenario. An administrator changes the endpoint policy hierarchy during an upgrade but cannot explain why several machines changed settings. Which diagnostic observation MOST DIRECTLY verifies the relevant issue? Select ONE best answer.
- Inspect release notes, audit history, completed maintenance actions, certificate validity and a pilot endpoint check-in.
- Review change ticket, affected group, matched rule, expected expiry and post-change endpoint protection state.
- Inspect upgrade and database migration logs, old backup integrity, service health and representative endpoint inventory/policy checks.
- Review the local filtering event, profile identifier, domain category and business authorization for an exception.
Explanation
Correct Answer
A:The discriminating evidence is: Inspect release notes, audit history, completed maintenance actions, certificate validity and a pilot endpoint check-in. For the reported situation (An administrator changes the endpoint policy hierarchy during an upgrade but cannot explain why several machines changed settings.), it should establish: Changes can be tied to authorized accounts and the management service remains healthy after each maintenance window.
Incorrect Answers
B:This evidence belongs to the distinct FortiClient EMS topic Endpoint policy exception and approval workflow, not the case-specific issue of EMS patching administration and operational audit described here (An administrator changes the endpoint policy hierarchy during an upgrade but cannot explain why several machines changed settings.).
C:This evidence belongs to the distinct FortiClient EMS topic EMS upgrade regression and database recovery plan, not the case-specific issue of EMS patching administration and operational audit described here (An administrator changes the endpoint policy hierarchy during an upgrade but cannot explain why several machines changed settings.).
D:This evidence belongs to the distinct FortiClient EMS topic Web Filter exceptions for business-critical sites, not the case-specific issue of EMS patching administration and operational audit described here (An administrator changes the endpoint policy hierarchy during an upgrade but cannot explain why several machines changed settings.).
Question 194
An endpoint administrator must verify that a configuration change achieved its goal. An administrator changes the endpoint policy hierarchy during an upgrade but cannot explain why several machines changed settings. The proposed validation is: Inspect release notes, audit history, completed maintenance actions, certificate validity and a pilot endpoint check-in. Which result BEST demonstrates that the requirement is satisfied? Select ONE best answer.
- A device enters or leaves the target group according to verifiable facts and no stale compliance exception persists.
- Only active authorized devices remain managed and replacement systems receive policy without inheriting an unrelated identity.
- Changes can be tied to authorized accounts and the management service remains healthy after each maintenance window.
- Prohibited categories are blocked and legitimate business sites remain usable under documented exceptions.
Explanation
Correct Answer
C:The intended acceptance criterion is: Changes can be tied to authorized accounts and the management service remains healthy after each maintenance window. Confirm it through: Inspect release notes, audit history, completed maintenance actions, certificate validity and a pilot endpoint check-in.
Incorrect Answers
A:That option concerns Dynamic group posture rule mismatch troubleshooting. The associated corrective action is: Maintain a patch and configuration change process that records administrative actions and validates endpoint management after maintenance.
B:That option concerns Controlled endpoint onboarding and deprovisioning lifecycle. The associated corrective action is: Maintain a patch and configuration change process that records administrative actions and validates endpoint management after maintenance.
D:That option concerns Web Filter profile category and exception governance. The associated corrective action is: Maintain a patch and configuration change process that records administrative actions and validates endpoint management after maintenance.
Question 195
A security operations reviewer evaluates an unsafe configuration shortcut in this case. An administrator changes the endpoint policy hierarchy during an upgrade but cannot explain why several machines changed settings. Which assumption is MOST DIRECTLY relevant to reject? Select ONE best answer.
- Authorize a new FortiGate connection in EMS and validate the reciprocal authorization state where the FortiOS workflow requires it.
- Isolate whether a blocked user application originates from a FortiClient local protection module or a FortiGate network security policy.
- Patch EMS production without preserving change records and disable all logging to make the upgrade run faster.
- Assign EMS administrative roles according to approved operating responsibilities instead of broadly granting full server access.
Explanation
Correct Answer
C:It conflicts with the technical behavior: Regular security updates and approved access changes need post-change validation; logs and baseline comparisons support root-cause analysis.
Incorrect Answers
A:This action belongs to the distinct FortiClient EMS topic Reciprocal EMS and FortiGate authorization workflow, not the case-specific issue of EMS patching administration and operational audit described here (An administrator changes the endpoint policy hierarchy during an upgrade but cannot explain why several machines changed settings.). The targeted action for this case is: Maintain a patch and configuration change process that records administrative actions and validates endpoint management after maintenance.
B:This action belongs to the distinct FortiClient EMS topic Network versus endpoint protection event distinctions, not the case-specific issue of EMS patching administration and operational audit described here (An administrator changes the endpoint policy hierarchy during an upgrade but cannot explain why several machines changed settings.). The targeted action for this case is: Maintain a patch and configuration change process that records administrative actions and validates endpoint management after maintenance.
D:This action belongs to the distinct FortiClient EMS topic EMS administrator permissions and separation of duties, not the case-specific issue of EMS patching administration and operational audit described here (An administrator changes the endpoint policy hierarchy during an upgrade but cannot explain why several machines changed settings.). The targeted action for this case is: Maintain a patch and configuration change process that records administrative actions and validates endpoint management after maintenance.
Question 196
A FortiClient EMS 7.4 administrator investigates this endpoint management case: A new EMS hotfix is applied during business hours and the operations team has no evidence that Telemetry or ZTNA tags recovered. Which is the most appropriate FIRST action to address the issue? Select ONE best answer.
- Use a controlled EMS invitation or endpoint enrollment method that associates a legitimate device with the correct management instance.
- Maintain a patch and configuration change process that records administrative actions and validates endpoint management after maintenance.
- Configure supported Sandbox analysis workflow and correlate submitted-sample verdicts with endpoint security actions.
- Review EMS administrative and operational logs with the incident's time window and relevant scope before drawing conclusions.
Explanation
Correct Answer
B:The targeted next step is: Maintain a patch and configuration change process that records administrative actions and validates endpoint management after maintenance. The supporting FortiClient EMS principle is: Regular security updates and approved access changes need post-change validation; logs and baseline comparisons support root-cause analysis. Verify this by: Inspect release notes, audit history, completed maintenance actions, certificate validity and a pilot endpoint check-in.
Incorrect Answers
A:This action belongs to the distinct FortiClient EMS topic FortiClient registration invitations and enrollment identity, not the case-specific issue of EMS patching administration and operational audit described here (A new EMS hotfix is applied during business hours and the operations team has no evidence that Telemetry or ZTNA tags recovered.). The targeted action for this case is: Maintain a patch and configuration change process that records administrative actions and validates endpoint management after maintenance.
C:This action belongs to the distinct FortiClient EMS topic FortiClient Sandbox integration and detection handoff, not the case-specific issue of EMS patching administration and operational audit described here (A new EMS hotfix is applied during business hours and the operations team has no evidence that Telemetry or ZTNA tags recovered.). The targeted action for this case is: Maintain a patch and configuration change process that records administrative actions and validates endpoint management after maintenance.
D:This action belongs to the distinct FortiClient EMS topic EMS Administration Log Viewer filters and audit trails, not the case-specific issue of EMS patching administration and operational audit described here (A new EMS hotfix is applied during business hours and the operations team has no evidence that Telemetry or ZTNA tags recovered.). The targeted action for this case is: Maintain a patch and configuration change process that records administrative actions and validates endpoint management after maintenance.
Question 197
An endpoint security reviewer examines this scenario. A new EMS hotfix is applied during business hours and the operations team has no evidence that Telemetry or ZTNA tags recovered. The proposed action is: Maintain a patch and configuration change process that records administrative actions and validates endpoint management after maintenance. Which technical principle BEST supports that decision? Select ONE best answer.
- Installed feature modules are defined during client deployment and must be considered alongside later EMS policy provisioning.
- Management capacity must account for concurrent Telemetry sessions, database resources and the practical operating workload rather than server CPU alone.
- Regular security updates and approved access changes need post-change validation; logs and baseline comparisons support root-cause analysis.
- A deployed antivirus module needs an active profile, update availability and policy-consistent scan behavior; installation alone is not protection proof.
Explanation
Correct Answer
C:Regular security updates and approved access changes need post-change validation; logs and baseline comparisons support root-cause analysis. Applied to this case (A new EMS hotfix is applied during business hours and the operations team has no evidence that Telemetry or ZTNA tags recovered.), it supports the controlled action: Maintain a patch and configuration change process that records administrative actions and validates endpoint management after maintenance.
Incorrect Answers
A:This principle belongs to the distinct FortiClient EMS topic EMS-created FortiClient deployment packages and feature modules, not the case-specific issue of EMS patching administration and operational audit described here (A new EMS hotfix is applied during business hours and the operations team has no evidence that Telemetry or ZTNA tags recovered.). The targeted action for this case is: Maintain a patch and configuration change process that records administrative actions and validates endpoint management after maintenance.
B:This principle belongs to the distinct FortiClient EMS topic EMS server performance planning for endpoint count, not the case-specific issue of EMS patching administration and operational audit described here (A new EMS hotfix is applied during business hours and the operations team has no evidence that Telemetry or ZTNA tags recovered.). The targeted action for this case is: Maintain a patch and configuration change process that records administrative actions and validates endpoint management after maintenance.
D:This principle belongs to the distinct FortiClient EMS topic Malware Protection settings and signature update lifecycle, not the case-specific issue of EMS patching administration and operational audit described here (A new EMS hotfix is applied during business hours and the operations team has no evidence that Telemetry or ZTNA tags recovered.). The targeted action for this case is: Maintain a patch and configuration change process that records administrative actions and validates endpoint management after maintenance.
Question 198
A Fortinet security engineer needs objective troubleshooting evidence for this scenario. A new EMS hotfix is applied during business hours and the operations team has no evidence that Telemetry or ZTNA tags recovered. Which diagnostic observation MOST DIRECTLY verifies the relevant issue? Select ONE best answer.
- Inspect release notes, audit history, completed maintenance actions, certificate validity and a pilot endpoint check-in.
- Review host OS/build, CPU and storage, administrator rights, required components and preflight installer logs.
- Compare EMS site FQDNs, FortiGate connector configuration, approved peers and visible tags for a test managed device.
- Compare endpoint OS, FortiClient version, installed modules and the official release-specific capability notes.
Explanation
Correct Answer
A:The discriminating evidence is: Inspect release notes, audit history, completed maintenance actions, certificate validity and a pilot endpoint check-in. For the reported situation (A new EMS hotfix is applied during business hours and the operations team has no evidence that Telemetry or ZTNA tags recovered.), it should establish: Changes can be tied to authorized accounts and the management service remains healthy after each maintenance window.
Incorrect Answers
B:This evidence belongs to the distinct FortiClient EMS topic Installation prerequisites and supported server operating systems, not the case-specific issue of EMS patching administration and operational audit described here (A new EMS hotfix is applied during business hours and the operations team has no evidence that Telemetry or ZTNA tags recovered.).
C:This evidence belongs to the distinct FortiClient EMS topic EMS Fabric connector scope and multi-site mapping, not the case-specific issue of EMS patching administration and operational audit described here (A new EMS hotfix is applied during business hours and the operations team has no evidence that Telemetry or ZTNA tags recovered.).
D:This evidence belongs to the distinct FortiClient EMS topic Endpoint OS-specific limitations and unsupported fixes, not the case-specific issue of EMS patching administration and operational audit described here (A new EMS hotfix is applied during business hours and the operations team has no evidence that Telemetry or ZTNA tags recovered.).
Question 199
An endpoint administrator must verify that a configuration change achieved its goal. A new EMS hotfix is applied during business hours and the operations team has no evidence that Telemetry or ZTNA tags recovered. The proposed validation is: Inspect release notes, audit history, completed maintenance actions, certificate validity and a pilot endpoint check-in. Which result BEST demonstrates that the requirement is satisfied? Select ONE best answer.
- Changes can be tied to authorized accounts and the management service remains healthy after each maintenance window.
- The selected deployment can manage the intended users without assuming all endpoints are permanently on the corporate LAN.
- A posture change propagates appropriately and the gateway does not rely indefinitely on unsupported stale compliance assumptions.
- Approved users connect to the intended application endpoint and other services remain unreachable.
Explanation
Correct Answer
A:The intended acceptance criterion is: Changes can be tied to authorized accounts and the management service remains healthy after each maintenance window. Confirm it through: Inspect release notes, audit history, completed maintenance actions, certificate validity and a pilot endpoint check-in. The associated corrective action is: Maintain a patch and configuration change process that records administrative actions and validates endpoint management after maintenance.
Incorrect Answers
B:That option concerns FortiClient EMS on-premises and cloud placement. The associated corrective action is: Maintain a patch and configuration change process that records administrative actions and validates endpoint management after maintenance.
C:That option concerns ZTNA tag freshness and management connectivity. The associated corrective action is: Maintain a patch and configuration change process that records administrative actions and validates endpoint management after maintenance.
D:That option concerns FortiGate ZTNA access proxy and application mapping. The associated corrective action is: Maintain a patch and configuration change process that records administrative actions and validates endpoint management after maintenance.
Question 200
An endpoint security operations team needs a controlled Fortinet response and proof of its result. A new EMS hotfix is applied during business hours and the operations team has no evidence that Telemetry or ZTNA tags recovered. Which THREE complementary steps provide the best response, direct diagnostic evidence and a measurable success condition? Select THREE answers.
- Inspect EMS quarantine state, endpoint response, FortiGate status and representative permitted/denied network traffic.
- Maintain a patch and configuration change process that records administrative actions and validates endpoint management after maintenance.
- Inspect release notes, audit history, completed maintenance actions, certificate validity and a pilot endpoint check-in.
- Changes can be tied to authorized accounts and the management service remains healthy after each maintenance window.
- Size the FortiClient EMS service and supporting storage for enrolled endpoint volume, log growth and planned management operations.
- Compare EMS site FQDNs, FortiGate connector configuration, approved peers and visible tags for a test managed device.
Explanation
Correct Answers
B:The targeted next step is: Maintain a patch and configuration change process that records administrative actions and validates endpoint management after maintenance.
C:The discriminating evidence is: Inspect release notes, audit history, completed maintenance actions, certificate validity and a pilot endpoint check-in.
D:The intended acceptance criterion is: Changes can be tied to authorized accounts and the management service remains healthy after each maintenance window.
Incorrect Answers
A:This evidence belongs to the distinct FortiClient EMS topic Endpoint quarantine state and data-plane effects, not the case-specific issue of EMS patching administration and operational audit described here (A new EMS hotfix is applied during business hours and the operations team has no evidence that Telemetry or ZTNA tags recovered.).
E:This action belongs to the distinct FortiClient EMS topic EMS server performance planning for endpoint count, not the case-specific issue of EMS patching administration and operational audit described here (A new EMS hotfix is applied during business hours and the operations team has no evidence that Telemetry or ZTNA tags recovered.). The targeted action for this case is: Maintain a patch and configuration change process that records administrative actions and validates endpoint management after maintenance.
F:This evidence belongs to the distinct FortiClient EMS topic EMS Fabric connector scope and multi-site mapping, not the case-specific issue of EMS patching administration and operational audit described here (A new EMS hotfix is applied during business hours and the operations team has no evidence that Telemetry or ZTNA tags recovered.). The targeted action for this case is: Maintain a patch and configuration change process that records administrative actions and validates endpoint management after maintenance. Verify it through: Inspect release notes, audit history, completed maintenance actions, certificate validity and a pilot endpoint check-in.