Fortinet FCP_FCT_AD-7.4 Practice Test 33
Question 320
A FortiClient EMS administrator prepares a focused response to this scenario. A security dashboard lists a new FortiClient device as online while its assigned malware protection profile is disabled. Which TWO complementary steps combine the most appropriate action and direct verification? Select TWO answers.
- Test the canonical EMS FQDN from office and remote networks, relevant HTTPS connectivity and certificate name matching.
- Review the agent's running protection components, signature age, FortiGuard update reachability and safe test detection logs.
- Enable supported Malware Protection controls and validate real signature or engine update health before relying on scan status.
- Test an approved managed healthy endpoint and a deliberately noncompliant client with the same application request.
- Compare intended rule criteria, client OS/process state, received tag event, group membership and FortiOS tag status.
Explanation
Correct Answers
B:The discriminating evidence is: Review the agent's running protection components, signature age, FortiGuard update reachability and safe test detection logs.
C:The targeted next step is: Enable supported Malware Protection controls and validate real signature or engine update health before relying on scan status.
Incorrect Answers
A:This evidence belongs to the distinct FortiClient EMS topic EMS initial network identity and DNS reachability, not the case-specific issue of Malware Protection settings and signature update lifecycle described here (A security dashboard lists a new FortiClient device as online while its assigned malware protection profile is disabled.).
D:This evidence belongs to the distinct FortiClient EMS topic ZTNA access decision based on identity and device posture, not the case-specific issue of Malware Protection settings and signature update lifecycle described here (A security dashboard lists a new FortiClient device as online while its assigned malware protection profile is disabled.).
E:This evidence belongs to the distinct FortiClient EMS topic Dynamic group posture rule mismatch troubleshooting, not the case-specific issue of Malware Protection settings and signature update lifecycle described here (A security dashboard lists a new FortiClient device as online while its assigned malware protection profile is disabled.).
Question 321
A FortiClient EMS 7.4 administrator investigates this endpoint management case: An endpoint scan flags an outdated browser but the operations team closes the ticket without checking the installed version. Which is the most appropriate FIRST action to address the issue? Select ONE best answer.
- Establish an auditable process to register replacement endpoints and retire decommissioned ones from EMS without confusing their identities.
- Schedule and configure supported vulnerability scanning appropriate for device risk, then verify detection and remediation feedback.
- Define a controlled endpoint quarantine trigger for a verified threat and review the complete detection-to-action chain.
- Examine posture tag criteria and fresh endpoint facts before granting a compliant group to a device that failed the rule.
Explanation
Correct Answer
B:The targeted next step is: Schedule and configure supported vulnerability scanning appropriate for device risk, then verify detection and remediation feedback. The supporting FortiClient EMS principle is: Endpoint vulnerability reports identify exposure indicators but need current signatures, sensible schedules and a separate patch-remediation workflow.
Incorrect Answers
A:This action belongs to the distinct FortiClient EMS topic Controlled endpoint onboarding and deprovisioning lifecycle, not the case-specific issue of Vulnerability Scan profiles and remediation priorities described here (An endpoint scan flags an outdated browser but the operations team closes the ticket without checking the installed version.). The targeted action for this case is: Schedule and configure supported vulnerability scanning appropriate for device risk, then verify detection and remediation feedback.
C:This action belongs to the distinct FortiClient EMS topic Quarantine triggers from validated security indicators, not the case-specific issue of Vulnerability Scan profiles and remediation priorities described here (An endpoint scan flags an outdated browser but the operations team closes the ticket without checking the installed version.). The targeted action for this case is: Schedule and configure supported vulnerability scanning appropriate for device risk, then verify detection and remediation feedback.
D:This action belongs to the distinct FortiClient EMS topic Dynamic group posture rule mismatch troubleshooting, not the case-specific issue of Vulnerability Scan profiles and remediation priorities described here (An endpoint scan flags an outdated browser but the operations team closes the ticket without checking the installed version.). The targeted action for this case is: Schedule and configure supported vulnerability scanning appropriate for device risk, then verify detection and remediation feedback.
Question 322
An endpoint security reviewer examines this scenario. An endpoint scan flags an outdated browser but the operations team closes the ticket without checking the installed version. The proposed action is: Schedule and configure supported vulnerability scanning appropriate for device risk, then verify detection and remediation feedback. Which technical principle BEST supports that decision? Select ONE best answer.
- A correctly distributed VPN connection still needs a reachable gateway, valid user identity and compatible client settings to establish a session.
- An EMS installer needs a compatible host and correct prerequisites; successful installation of an unrelated web service does not establish support.
- Multi-site or tenant boundaries protect separation of administration and policy; the exact feature behavior must be checked against the deployed EMS edition.
- Endpoint vulnerability reports identify exposure indicators but need current signatures, sensible schedules and a separate patch-remediation workflow.
Explanation
Correct Answer
D:Endpoint vulnerability reports identify exposure indicators but need current signatures, sensible schedules and a separate patch-remediation workflow. Applied to this case (An endpoint scan flags an outdated browser but the operations team closes the ticket without checking the installed version.), it supports the controlled action: Schedule and configure supported vulnerability scanning appropriate for device risk, then verify detection and remediation feedback.
Incorrect Answers
A:This principle belongs to the distinct FortiClient EMS topic Remote Access profile parameters and user authentication, not the case-specific issue of Vulnerability Scan profiles and remediation priorities described here (An endpoint scan flags an outdated browser but the operations team closes the ticket without checking the installed version.). The targeted action for this case is: Schedule and configure supported vulnerability scanning appropriate for device risk, then verify detection and remediation feedback.
B:This principle belongs to the distinct FortiClient EMS topic Installation prerequisites and supported server operating systems, not the case-specific issue of Vulnerability Scan profiles and remediation priorities described here (An endpoint scan flags an outdated browser but the operations team closes the ticket without checking the installed version.). The targeted action for this case is: Schedule and configure supported vulnerability scanning appropriate for device risk, then verify detection and remediation feedback.
C:This principle belongs to the distinct FortiClient EMS topic EMS tenant and site isolation in shared deployments, not the case-specific issue of Vulnerability Scan profiles and remediation priorities described here (An endpoint scan flags an outdated browser but the operations team closes the ticket without checking the installed version.). The targeted action for this case is: Schedule and configure supported vulnerability scanning appropriate for device risk, then verify detection and remediation feedback.
Question 323
A Fortinet security engineer needs objective troubleshooting evidence for this scenario. An endpoint scan flags an outdated browser but the operations team closes the ticket without checking the installed version. Which diagnostic observation MOST DIRECTLY verifies the relevant issue? Select ONE best answer.
- Compare configured management interfaces, remote access controls, permitted source networks and successful authorized admin logins.
- Inspect configured scan timing, detected vulnerable software, risk rating, last scan time and a tested remediation update.
- Review installer return codes, endpoint event logs, current FortiClient version, pending reboot and package execution context.
- Compare matching endpoint groups, endpoint policy selection, individual feature profiles and last policy update time.
Explanation
Correct Answer
B:The discriminating evidence is: Inspect configured scan timing, detected vulnerable software, risk rating, last scan time and a tested remediation update. For the reported situation (An endpoint scan flags an outdated browser but the operations team closes the ticket without checking the installed version.), it should establish: Known software issues are identified, assigned to owners and reduced in follow-up scans.
Incorrect Answers
A:This evidence belongs to the distinct FortiClient EMS topic EMS server configuration and secure administrator access, not the case-specific issue of Vulnerability Scan profiles and remediation priorities described here (An endpoint scan flags an outdated browser but the operations team closes the ticket without checking the installed version.).
C:This evidence belongs to the distinct FortiClient EMS topic FortiClient installation retries and endpoint reboot coordination, not the case-specific issue of Vulnerability Scan profiles and remediation priorities described here (An endpoint scan flags an outdated browser but the operations team closes the ticket without checking the installed version.).
D:This evidence belongs to the distinct FortiClient EMS topic Profile assignment and unexpected group membership diagnosis, not the case-specific issue of Vulnerability Scan profiles and remediation priorities described here (An endpoint scan flags an outdated browser but the operations team closes the ticket without checking the installed version.).
Question 324
An endpoint administrator must verify that a configuration change achieved its goal. An endpoint scan flags an outdated browser but the operations team closes the ticket without checking the installed version. The proposed validation is: Inspect configured scan timing, detected vulnerable software, risk rating, last scan time and a tested remediation update. Which result BEST demonstrates that the requirement is satisfied? Select ONE best answer.
- The correct supported package completes installation and a controlled registration succeeds after remediation.
- The incident plan uses the available response mechanism without claiming an unsupported client capability.
- The project scales only after pilot users remain managed and planned endpoint safeguards work without service disruption.
- Known software issues are identified, assigned to owners and reduced in follow-up scans.
Explanation
Correct Answer
D:The intended acceptance criterion is: Known software issues are identified, assigned to owners and reduced in follow-up scans. Confirm it through: Inspect configured scan timing, detected vulnerable software, risk rating, last scan time and a tested remediation update.
Incorrect Answers
A:That option concerns Deployment package error codes and installation rollback. The associated corrective action is: Schedule and configure supported vulnerability scanning appropriate for device risk, then verify detection and remediation feedback.
B:This outcome belongs to the distinct FortiClient EMS topic Unsupported-platform quarantine caveat, not the case-specific issue of Vulnerability Scan profiles and remediation priorities described here (An endpoint scan flags an outdated browser but the operations team closes the ticket without checking the installed version.). The targeted action for this case is: Schedule and configure supported vulnerability scanning appropriate for device risk, then verify detection and remediation feedback.
C:That option concerns Controlled EMS initial pilot and rollback decision. The associated corrective action is: Schedule and configure supported vulnerability scanning appropriate for device risk, then verify detection and remediation feedback.
Question 325
A security operations reviewer evaluates an unsafe configuration shortcut in this case. An endpoint scan flags an outdated browser but the operations team closes the ticket without checking the installed version. Which assumption is MOST DIRECTLY relevant to reject? Select ONE best answer.
- Assume running a vulnerability scan automatically installs every required security patch without change control.
- Create an endpoint policy that deliberately combines the necessary module profiles for the targeted device group.
- Use logs from FortiClient, EMS posture and FortiGate access proxy to locate the specific denial stage for one application.
- Use a controlled EMS invitation or endpoint enrollment method that associates a legitimate device with the correct management instance.
Explanation
Correct Answer
A:It conflicts with the technical behavior: Endpoint vulnerability reports identify exposure indicators but need current signatures, sensible schedules and a separate patch-remediation workflow.
Incorrect Answers
B:This action belongs to the distinct FortiClient EMS topic Endpoint profile combination through EMS endpoint policies, not the case-specific issue of Vulnerability Scan profiles and remediation priorities described here (An endpoint scan flags an outdated browser but the operations team closes the ticket without checking the installed version.). The targeted action for this case is: Schedule and configure supported vulnerability scanning appropriate for device risk, then verify detection and remediation feedback.
C:This action belongs to the distinct FortiClient EMS topic ZTNA application access denial event correlation, not the case-specific issue of Vulnerability Scan profiles and remediation priorities described here (An endpoint scan flags an outdated browser but the operations team closes the ticket without checking the installed version.). The targeted action for this case is: Schedule and configure supported vulnerability scanning appropriate for device risk, then verify detection and remediation feedback.
D:This action belongs to the distinct FortiClient EMS topic FortiClient registration invitations and enrollment identity, not the case-specific issue of Vulnerability Scan profiles and remediation priorities described here (An endpoint scan flags an outdated browser but the operations team closes the ticket without checking the installed version.). The targeted action for this case is: Schedule and configure supported vulnerability scanning appropriate for device risk, then verify detection and remediation feedback.
Question 326
A FortiClient EMS 7.4 administrator investigates this endpoint management case: A workstation appears clean because its vulnerability scan has not run since provisioning several weeks earlier. Which is the most appropriate FIRST action to address the issue? Select ONE best answer.
- Correlate FortiClient Telemetry timestamps with EMS registration and policy events before treating an endpoint as unmanaged.
- Group devices by supported Windows, macOS or Linux capabilities and stage compatible FortiClient deployment packages.
- Schedule and configure supported vulnerability scanning appropriate for device risk, then verify detection and remediation feedback.
- Stage a representative pilot of FortiClient registration, profile enforcement, Fabric integration and change rollback before broad rollout.
Explanation
Correct Answer
C:The targeted next step is: Schedule and configure supported vulnerability scanning appropriate for device risk, then verify detection and remediation feedback. The supporting FortiClient EMS principle is: Endpoint vulnerability reports identify exposure indicators but need current signatures, sensible schedules and a separate patch-remediation workflow. Verify this by: Inspect configured scan timing, detected vulnerable software, risk rating, last scan time and a tested remediation update.
Incorrect Answers
A:This action belongs to the distinct FortiClient EMS topic FortiClient endpoint Telemetry event chronology, not the case-specific issue of Vulnerability Scan profiles and remediation priorities described here (A workstation appears clean because its vulnerability scan has not run since provisioning several weeks earlier.). The targeted action for this case is: Schedule and configure supported vulnerability scanning appropriate for device risk, then verify detection and remediation feedback.
B:This action belongs to the distinct FortiClient EMS topic Endpoint operating-system support during mass provisioning, not the case-specific issue of Vulnerability Scan profiles and remediation priorities described here (A workstation appears clean because its vulnerability scan has not run since provisioning several weeks earlier.). The targeted action for this case is: Schedule and configure supported vulnerability scanning appropriate for device risk, then verify detection and remediation feedback.
D:This action belongs to the distinct FortiClient EMS topic Controlled EMS initial pilot and rollback decision, not the case-specific issue of Vulnerability Scan profiles and remediation priorities described here (A workstation appears clean because its vulnerability scan has not run since provisioning several weeks earlier.). The targeted action for this case is: Schedule and configure supported vulnerability scanning appropriate for device risk, then verify detection and remediation feedback.
Question 327
An endpoint security reviewer examines this scenario. A workstation appears clean because its vulnerability scan has not run since provisioning several weeks earlier. The proposed action is: Schedule and configure supported vulnerability scanning appropriate for device risk, then verify detection and remediation feedback. Which technical principle BEST supports that decision? Select ONE best answer.
- EMS inventory and entitlements depend on actual managed devices; stale records and reused hostnames can distort policy targeting.
- Zero trust access is based on context and policy rather than assuming a user becomes trusted whenever physically on premises.
- Endpoint vulnerability reports identify exposure indicators but need current signatures, sensible schedules and a separate patch-remediation workflow.
- Connector setup can require confirmation at both management and gateway systems; an entered FQDN alone does not complete Fabric trust.
Explanation
Correct Answer
C:Endpoint vulnerability reports identify exposure indicators but need current signatures, sensible schedules and a separate patch-remediation workflow. Applied to this case (A workstation appears clean because its vulnerability scan has not run since provisioning several weeks earlier.), it supports the controlled action: Schedule and configure supported vulnerability scanning appropriate for device risk, then verify detection and remediation feedback.
Incorrect Answers
A:This principle belongs to the distinct FortiClient EMS topic Controlled endpoint onboarding and deprovisioning lifecycle, not the case-specific issue of Vulnerability Scan profiles and remediation priorities described here (A workstation appears clean because its vulnerability scan has not run since provisioning several weeks earlier.). The targeted action for this case is: Schedule and configure supported vulnerability scanning appropriate for device risk, then verify detection and remediation feedback.
B:This principle belongs to the distinct FortiClient EMS topic ZTNA on-net and off-net consistent policy treatment, not the case-specific issue of Vulnerability Scan profiles and remediation priorities described here (A workstation appears clean because its vulnerability scan has not run since provisioning several weeks earlier.). The targeted action for this case is: Schedule and configure supported vulnerability scanning appropriate for device risk, then verify detection and remediation feedback.
D:This principle belongs to the distinct FortiClient EMS topic Reciprocal EMS and FortiGate authorization workflow, not the case-specific issue of Vulnerability Scan profiles and remediation priorities described here (A workstation appears clean because its vulnerability scan has not run since provisioning several weeks earlier.). The targeted action for this case is: Schedule and configure supported vulnerability scanning appropriate for device risk, then verify detection and remediation feedback.
Question 328
A Fortinet security engineer needs objective troubleshooting evidence for this scenario. A workstation appears clean because its vulnerability scan has not run since provisioning several weeks earlier. Which diagnostic observation MOST DIRECTLY verifies the relevant issue? Select ONE best answer.
- Inspect configured scan timing, detected vulnerable software, risk rating, last scan time and a tested remediation update.
- Compare intended rule criteria, client OS/process state, received tag event, group membership and FortiOS tag status.
- Compare approved logging devices, timestamps, client events, detected IoCs and FortiGate Security Fabric connectivity.
- Record backup timestamp, storage protection, application version and a rehearsal restore into an isolated test environment.
Explanation
Correct Answer
A:The discriminating evidence is: Inspect configured scan timing, detected vulnerable software, risk rating, last scan time and a tested remediation update. For the reported situation (A workstation appears clean because its vulnerability scan has not run since provisioning several weeks earlier.), it should establish: Known software issues are identified, assigned to owners and reduced in follow-up scans.
Incorrect Answers
B:This evidence belongs to the distinct FortiClient EMS topic Dynamic group posture rule mismatch troubleshooting, not the case-specific issue of Vulnerability Scan profiles and remediation priorities described here (A workstation appears clean because its vulnerability scan has not run since provisioning several weeks earlier.).
C:This evidence belongs to the distinct FortiClient EMS topic FortiAnalyzer security event integration within the Fabric, not the case-specific issue of Vulnerability Scan profiles and remediation priorities described here (A workstation appears clean because its vulnerability scan has not run since provisioning several weeks earlier.).
D:This evidence belongs to the distinct FortiClient EMS topic EMS database backup and disaster recovery validation, not the case-specific issue of Vulnerability Scan profiles and remediation priorities described here (A workstation appears clean because its vulnerability scan has not run since provisioning several weeks earlier.).
Question 329
An endpoint administrator must verify that a configuration change achieved its goal. A workstation appears clean because its vulnerability scan has not run since provisioning several weeks earlier. The proposed validation is: Inspect configured scan timing, detected vulnerable software, risk rating, last scan time and a tested remediation update. Which result BEST demonstrates that the requirement is satisfied? Select ONE best answer.
- The incident plan uses the available response mechanism without claiming an unsupported client capability.
- The affected host is isolated according to policy and a documented release path exists for verified recovery.
- Only verified cleaned endpoints return to ordinary access, with incident evidence and approval retained.
- Known software issues are identified, assigned to owners and reduced in follow-up scans.
Explanation
Correct Answer
D:The intended acceptance criterion is: Known software issues are identified, assigned to owners and reduced in follow-up scans. Confirm it through: Inspect configured scan timing, detected vulnerable software, risk rating, last scan time and a tested remediation update. The associated corrective action is: Schedule and configure supported vulnerability scanning appropriate for device risk, then verify detection and remediation feedback.
Incorrect Answers
A:This outcome belongs to the distinct FortiClient EMS topic Unsupported-platform quarantine caveat, not the case-specific issue of Vulnerability Scan profiles and remediation priorities described here (A workstation appears clean because its vulnerability scan has not run since provisioning several weeks earlier.). The targeted action for this case is: Schedule and configure supported vulnerability scanning appropriate for device risk, then verify detection and remediation feedback.
B:This outcome belongs to the distinct FortiClient EMS topic Malware quarantine versus general network isolation scope, not the case-specific issue of Vulnerability Scan profiles and remediation priorities described here (A workstation appears clean because its vulnerability scan has not run since provisioning several weeks earlier.).
C:That option concerns Quarantine release approval and incident preservation. The associated corrective action is: Schedule and configure supported vulnerability scanning appropriate for device risk, then verify detection and remediation feedback.
Question 330
A FortiClient EMS administrator prepares a focused response to this scenario. A workstation appears clean because its vulnerability scan has not run since provisioning several weeks earlier. Which TWO complementary steps combine the most appropriate action and direct verification? Select TWO answers.
- Inspect the FortiGate connector address, EMS Fabric Devices authorization, certificate validation and connection status.
- Schedule and configure supported vulnerability scanning appropriate for device risk, then verify detection and remediation feedback.
- Inspect endpoint UID, current IP, registration state, posture status, connector synchronization and the FortiGate matched policy.
- Test the specified EMS FQDN, TLS connection, network ACL and certificate from the problem endpoint's location.
- Inspect configured scan timing, detected vulnerable software, risk rating, last scan time and a tested remediation update.
Explanation
Correct Answers
B:The targeted next step is: Schedule and configure supported vulnerability scanning appropriate for device risk, then verify detection and remediation feedback.
E:The discriminating evidence is: Inspect configured scan timing, detected vulnerable software, risk rating, last scan time and a tested remediation update.
Incorrect Answers
A:This evidence belongs to the distinct FortiClient EMS topic FortiGate EMS Security Fabric connector establishment, not the case-specific issue of Vulnerability Scan profiles and remediation priorities described here (A workstation appears clean because its vulnerability scan has not run since provisioning several weeks earlier.).
C:This evidence belongs to the distinct FortiClient EMS topic Endpoint identity correlation across EMS and FortiGate, not the case-specific issue of Vulnerability Scan profiles and remediation priorities described here (A workstation appears clean because its vulnerability scan has not run since provisioning several weeks earlier.).
D:This evidence belongs to the distinct FortiClient EMS topic Remote EMS registration and DNS path failures, not the case-specific issue of Vulnerability Scan profiles and remediation priorities described here (A workstation appears clean because its vulnerability scan has not run since provisioning several weeks earlier.).