Fortinet FCP_FCT_AD-7.4 Practice Test 36
Question 350
A FortiClient EMS administrator prepares a focused response to this scenario. A team wants users to choose personal VPN entries while retaining centrally controlled malware and ZTNA configuration. Which TWO complementary steps combine the most appropriate action and direct verification? Select TWO answers.
- Run equivalent approved and noncompliant tests from on-premises and remote networks and inspect both policy outcomes.
- Inspect the FortiGate connector address, EMS Fabric Devices authorization, certificate validation and connection status.
- Compare the delivered System Settings profile, local UI controls, admin policy and a controlled user attempt to change a setting.
- Set FortiClient system options in EMS so endpoint users retain only the self-service capabilities approved by policy.
- Schedule and configure supported vulnerability scanning appropriate for device risk, then verify detection and remediation feedback.
Explanation
Correct Answers
C:The discriminating evidence is: Compare the delivered System Settings profile, local UI controls, admin policy and a controlled user attempt to change a setting.
D:The targeted next step is: Set FortiClient system options in EMS so endpoint users retain only the self-service capabilities approved by policy.
Incorrect Answers
A:This evidence belongs to the distinct FortiClient EMS topic ZTNA on-net and off-net consistent policy treatment, not the case-specific issue of System Settings profile and controlled endpoint self-service described here (A team wants users to choose personal VPN entries while retaining centrally controlled malware and ZTNA configuration.).
B:This evidence belongs to the distinct FortiClient EMS topic FortiGate EMS Security Fabric connector establishment, not the case-specific issue of System Settings profile and controlled endpoint self-service described here (A team wants users to choose personal VPN entries while retaining centrally controlled malware and ZTNA configuration.).
E:This action belongs to the distinct FortiClient EMS topic Vulnerability Scan profiles and remediation priorities, not the case-specific issue of System Settings profile and controlled endpoint self-service described here (A team wants users to choose personal VPN entries while retaining centrally controlled malware and ZTNA configuration.). The targeted action for this case is: Set FortiClient system options in EMS so endpoint users retain only the self-service capabilities approved by policy.
Question 351
A FortiClient EMS 7.4 administrator investigates this endpoint management case: A security group should include only patched corporate laptops but an unpatched test device is receiving the same tag. Which is the most appropriate FIRST action to address the issue? Select ONE best answer.
- Build EMS security posture rules from verifiable endpoint facts such as supported OS versions, domains and running processes.
- Review management interface exposure, administration access controls and required endpoint-control settings before enrolling a pilot fleet.
- Keep endpoint policy administration in EMS while using FortiGate enforcement as an independent network security boundary.
- Use a controlled EMS invitation or endpoint enrollment method that associates a legitimate device with the correct management instance.
Explanation
Correct Answer
A:The targeted next step is: Build EMS security posture rules from verifiable endpoint facts such as supported OS versions, domains and running processes. The supporting FortiClient EMS principle is: FortiClient evaluates rules on endpoints and communicates results to EMS, which can use them for dynamic grouping and downstream access policy.
Incorrect Answers
B:This action belongs to the distinct FortiClient EMS topic EMS server configuration and secure administrator access, not the case-specific issue of Security posture tagging from operating-system facts described here (A security group should include only patched corporate laptops but an unpatched test device is receiving the same tag.). The targeted action for this case is: Build EMS security posture rules from verifiable endpoint facts such as supported OS versions, domains and running processes.
C:This action belongs to the distinct FortiClient EMS topic Security Fabric endpoint profile versus network access ownership, not the case-specific issue of Security posture tagging from operating-system facts described here (A security group should include only patched corporate laptops but an unpatched test device is receiving the same tag.). The targeted action for this case is: Build EMS security posture rules from verifiable endpoint facts such as supported OS versions, domains and running processes.
D:This action belongs to the distinct FortiClient EMS topic FortiClient registration invitations and enrollment identity, not the case-specific issue of Security posture tagging from operating-system facts described here (A security group should include only patched corporate laptops but an unpatched test device is receiving the same tag.). The targeted action for this case is: Build EMS security posture rules from verifiable endpoint facts such as supported OS versions, domains and running processes.
Question 352
An endpoint security reviewer examines this scenario. A security group should include only patched corporate laptops but an unpatched test device is receiving the same tag. The proposed action is: Build EMS security posture rules from verifiable endpoint facts such as supported OS versions, domains and running processes. Which technical principle BEST supports that decision? Select ONE best answer.
- FortiClient evaluates rules on endpoints and communicates results to EMS, which can use them for dynamic grouping and downstream access policy.
- An installed protection module needs functioning update paths and approved policy to keep definitions usable in a managed endpoint context.
- Endpoint connection logs can distinguish network failure, authentication refusal, deliberate deregistration and temporary service interruption.
- Restoring normal connectivity without checking infection, device identity and owner approval can reintroduce a security incident.
Explanation
Correct Answer
A:FortiClient evaluates rules on endpoints and communicates results to EMS, which can use them for dynamic grouping and downstream access policy. Applied to this case (A security group should include only patched corporate laptops but an unpatched test device is receiving the same tag.), it supports the controlled action: Build EMS security posture rules from verifiable endpoint facts such as supported OS versions, domains and running processes.
Incorrect Answers
B:This principle belongs to the distinct FortiClient EMS topic Malware definitions and FortiGuard update connectivity, not the case-specific issue of Security posture tagging from operating-system facts described here (A security group should include only patched corporate laptops but an unpatched test device is receiving the same tag.). The targeted action for this case is: Build EMS security posture rules from verifiable endpoint facts such as supported OS versions, domains and running processes.
C:This principle belongs to the distinct FortiClient EMS topic FortiClient endpoint Telemetry event chronology, not the case-specific issue of Security posture tagging from operating-system facts described here (A security group should include only patched corporate laptops but an unpatched test device is receiving the same tag.). The targeted action for this case is: Build EMS security posture rules from verifiable endpoint facts such as supported OS versions, domains and running processes.
D:This principle belongs to the distinct FortiClient EMS topic Quarantine release approval and incident preservation, not the case-specific issue of Security posture tagging from operating-system facts described here (A security group should include only patched corporate laptops but an unpatched test device is receiving the same tag.). The targeted action for this case is: Build EMS security posture rules from verifiable endpoint facts such as supported OS versions, domains and running processes.
Question 353
A Fortinet security engineer needs objective troubleshooting evidence for this scenario. A security group should include only patched corporate laptops but an unpatched test device is receiving the same tag. Which diagnostic observation MOST DIRECTLY verifies the relevant issue? Select ONE best answer.
- Trace one endpoint's received EMS policy, posture tag and matching FortiGate decision for a test application flow.
- Inspect the rule logic, endpoint reported facts, resulting tag and any propagated FortiGate group before allowing sensitive access.
- Review alert evidence, affected device identity, operator approval and local/remote quarantine state before and after the action.
- Compare certificate subject/SAN, issuing CA, expiration and endpoint trust-store validation against the actual EMS name.
Explanation
Correct Answer
B:The discriminating evidence is: Inspect the rule logic, endpoint reported facts, resulting tag and any propagated FortiGate group before allowing sensitive access. For the reported situation (A security group should include only patched corporate laptops but an unpatched test device is receiving the same tag.), it should establish: Compliant managed devices receive the intended tag and ineligible devices remain outside the privileged group.
Incorrect Answers
A:This evidence belongs to the distinct FortiClient EMS topic Endpoint management versus FortiGate enforcement boundary, not the case-specific issue of Security posture tagging from operating-system facts described here (A security group should include only patched corporate laptops but an unpatched test device is receiving the same tag.).
C:This evidence belongs to the distinct FortiClient EMS topic Malware quarantine versus general network isolation scope, not the case-specific issue of Security posture tagging from operating-system facts described here (A security group should include only patched corporate laptops but an unpatched test device is receiving the same tag.).
D:This evidence belongs to the distinct FortiClient EMS topic TLS certificate trust for EMS management services, not the case-specific issue of Security posture tagging from operating-system facts described here (A security group should include only patched corporate laptops but an unpatched test device is receiving the same tag.).
Question 354
An endpoint administrator must verify that a configuration change achieved its goal. A security group should include only patched corporate laptops but an unpatched test device is receiving the same tag. The proposed validation is: Inspect the rule logic, endpoint reported facts, resulting tag and any propagated FortiGate group before allowing sensitive access. Which result BEST demonstrates that the requirement is satisfied? Select ONE best answer.
- Compliant managed devices receive the intended tag and ineligible devices remain outside the privileged group.
- The selected deployment can manage the intended users without assuming all endpoints are permanently on the corporate LAN.
- The supported controls operate where expected, and unsupported features are clearly documented rather than silently treated as failures.
- The endpoint registers against its intended EMS and receives an auditable current policy assignment.
Explanation
Correct Answer
A:The intended acceptance criterion is: Compliant managed devices receive the intended tag and ineligible devices remain outside the privileged group. Confirm it through: Inspect the rule logic, endpoint reported facts, resulting tag and any propagated FortiGate group before allowing sensitive access.
Incorrect Answers
B:That option concerns FortiClient EMS on-premises and cloud placement. The associated corrective action is: Build EMS security posture rules from verifiable endpoint facts such as supported OS versions, domains and running processes.
C:That option concerns FortiClient platform capability differences. The associated corrective action is: Build EMS security posture rules from verifiable endpoint facts such as supported OS versions, domains and running processes.
D:This outcome belongs to the distinct FortiClient EMS topic EMS endpoint connection and Telemetry registration, not the case-specific issue of Security posture tagging from operating-system facts described here (A security group should include only patched corporate laptops but an unpatched test device is receiving the same tag.). The targeted action for this case is: Build EMS security posture rules from verifiable endpoint facts such as supported OS versions, domains and running processes.
Question 355
A security operations reviewer evaluates an unsafe configuration shortcut in this case. A security group should include only patched corporate laptops but an unpatched test device is receiving the same tag. Which assumption is MOST DIRECTLY relevant to reject? Select ONE best answer.
- Validate the health of the EMS application service and its database separately when management state or inventory becomes inconsistent.
- Revisit a failed EMS upgrade using supported migration steps, preserved database backups and compatible client versions.
- Size the FortiClient EMS service and supporting storage for enrolled endpoint volume, log growth and planned management operations.
- Assign an endpoint trusted status solely because its user claims the operating system is current without any posture check.
Explanation
Correct Answer
D:It conflicts with the technical behavior: FortiClient evaluates rules on endpoints and communicates results to EMS, which can use them for dynamic grouping and downstream access policy.
Incorrect Answers
A:This action belongs to the distinct FortiClient EMS topic FortiClient EMS server and database component boundaries, not the case-specific issue of Security posture tagging from operating-system facts described here (A security group should include only patched corporate laptops but an unpatched test device is receiving the same tag.). The targeted action for this case is: Build EMS security posture rules from verifiable endpoint facts such as supported OS versions, domains and running processes.
B:This action belongs to the distinct FortiClient EMS topic EMS upgrade regression and database recovery plan, not the case-specific issue of Security posture tagging from operating-system facts described here (A security group should include only patched corporate laptops but an unpatched test device is receiving the same tag.). The targeted action for this case is: Build EMS security posture rules from verifiable endpoint facts such as supported OS versions, domains and running processes.
C:This action belongs to the distinct FortiClient EMS topic EMS server performance planning for endpoint count, not the case-specific issue of Security posture tagging from operating-system facts described here (A security group should include only patched corporate laptops but an unpatched test device is receiving the same tag.). The targeted action for this case is: Build EMS security posture rules from verifiable endpoint facts such as supported OS versions, domains and running processes.
Question 356
A FortiClient EMS 7.4 administrator investigates this endpoint management case: A campus uses process-presence posture to protect a finance application and needs to verify the process actually runs before tagging. Which is the most appropriate FIRST action to address the issue? Select ONE best answer.
- Evaluate agent status, last contact, module update state and actual policy results together when reporting endpoint protection.
- Assign an endpoint trusted status solely because its user claims the operating system is current without any posture check.
- Check licensing and the installed deployment modules before concluding that a missing FortiClient protection feature is a technical defect.
- Build EMS security posture rules from verifiable endpoint facts such as supported OS versions, domains and running processes.
Explanation
Correct Answer
D:The targeted next step is: Build EMS security posture rules from verifiable endpoint facts such as supported OS versions, domains and running processes. The supporting FortiClient EMS principle is: FortiClient evaluates rules on endpoints and communicates results to EMS, which can use them for dynamic grouping and downstream access policy. Verify this by: Inspect the rule logic, endpoint reported facts, resulting tag and any propagated FortiGate group before allowing sensitive access.
Incorrect Answers
A:This action belongs to the distinct FortiClient EMS topic Endpoint health dashboard and meaningful compliance evidence, not the case-specific issue of Security posture tagging from operating-system facts described here (A campus uses process-presence posture to protect a finance application and needs to verify the process actually runs before tagging.). The targeted action for this case is: Build EMS security posture rules from verifiable endpoint facts such as supported OS versions, domains and running processes.
B:This is a technically risky shortcut in the present scenario: Assign an endpoint trusted status solely because its user claims the operating system is current without any posture check. It contradicts the governing distinction: FortiClient evaluates rules on endpoints and communicates results to EMS, which can use them for dynamic grouping and downstream access policy. Apply the controlled alternative: Build EMS security posture rules from verifiable endpoint facts such as supported OS versions, domains and running processes.
C:This action belongs to the distinct FortiClient EMS topic Endpoint license and EMS provisioned features, not the case-specific issue of Security posture tagging from operating-system facts described here (A campus uses process-presence posture to protect a finance application and needs to verify the process actually runs before tagging.). The targeted action for this case is: Build EMS security posture rules from verifiable endpoint facts such as supported OS versions, domains and running processes.
Question 357
An endpoint security reviewer examines this scenario. A campus uses process-presence posture to protect a finance application and needs to verify the process actually runs before tagging. The proposed action is: Build EMS security posture rules from verifiable endpoint facts such as supported OS versions, domains and running processes. Which technical principle BEST supports that decision? Select ONE best answer.
- FortiClient evaluates rules on endpoints and communicates results to EMS, which can use them for dynamic grouping and downstream access policy.
- On-premises and hosted EMS models change infrastructure responsibilities and connectivity planning, not the basic need for endpoints to enroll and receive policy.
- An EMS Fabric connector lets FortiOS obtain managed endpoint posture information, but the connector requires mutual trust and reachability.
- An EMS-managed endpoint can receive locked configuration while some user actions may remain available according to profile and feature support.
Explanation
Correct Answer
A:FortiClient evaluates rules on endpoints and communicates results to EMS, which can use them for dynamic grouping and downstream access policy. Applied to this case (A campus uses process-presence posture to protect a finance application and needs to verify the process actually runs before tagging.), it supports the controlled action: Build EMS security posture rules from verifiable endpoint facts such as supported OS versions, domains and running processes.
Incorrect Answers
B:This principle belongs to the distinct FortiClient EMS topic FortiClient EMS on-premises and cloud placement, not the case-specific issue of Security posture tagging from operating-system facts described here (A campus uses process-presence posture to protect a finance application and needs to verify the process actually runs before tagging.). The targeted action for this case is: Build EMS security posture rules from verifiable endpoint facts such as supported OS versions, domains and running processes.
C:This principle belongs to the distinct FortiClient EMS topic FortiGate EMS Security Fabric connector establishment, not the case-specific issue of Security posture tagging from operating-system facts described here (A campus uses process-presence posture to protect a finance application and needs to verify the process actually runs before tagging.). The targeted action for this case is: Build EMS security posture rules from verifiable endpoint facts such as supported OS versions, domains and running processes.
D:This principle belongs to the distinct FortiClient EMS topic System Settings profile and controlled endpoint self-service, not the case-specific issue of Security posture tagging from operating-system facts described here (A campus uses process-presence posture to protect a finance application and needs to verify the process actually runs before tagging.). The targeted action for this case is: Build EMS security posture rules from verifiable endpoint facts such as supported OS versions, domains and running processes.
Question 358
A Fortinet security engineer needs objective troubleshooting evidence for this scenario. A campus uses process-presence posture to protect a finance application and needs to verify the process actually runs before tagging. Which diagnostic observation MOST DIRECTLY verifies the relevant issue? Select ONE best answer.
- Compare deployment package module selection, target OS, installed client components and the effective endpoint profile after registration.
- Inspect the rule logic, endpoint reported facts, resulting tag and any propagated FortiGate group before allowing sensitive access.
- Review FortiOS received tag objects, the associated source device, address-group membership and an approved traffic test.
- Compare the EMS endpoint inventory, assigned policy, agent Telemetry state and a representative module status on the endpoint.
Explanation
Correct Answer
B:The discriminating evidence is: Inspect the rule logic, endpoint reported facts, resulting tag and any propagated FortiGate group before allowing sensitive access. For the reported situation (A campus uses process-presence posture to protect a finance application and needs to verify the process actually runs before tagging.), it should establish: Compliant managed devices receive the intended tag and ineligible devices remain outside the privileged group.
Incorrect Answers
A:This evidence belongs to the distinct FortiClient EMS topic EMS-created FortiClient deployment packages and feature modules, not the case-specific issue of Security posture tagging from operating-system facts described here (A campus uses process-presence posture to protect a finance application and needs to verify the process actually runs before tagging.).
C:This evidence belongs to the distinct FortiClient EMS topic Dynamic firewall policies driven by EMS security posture tags, not the case-specific issue of Security posture tagging from operating-system facts described here (A campus uses process-presence posture to protect a finance application and needs to verify the process actually runs before tagging.).
D:This evidence belongs to the distinct FortiClient EMS topic EMS management plane versus FortiClient endpoint agent, not the case-specific issue of Security posture tagging from operating-system facts described here (A campus uses process-presence posture to protect a finance application and needs to verify the process actually runs before tagging.).
Question 359
An endpoint administrator must verify that a configuration change achieved its goal. A campus uses process-presence posture to protect a finance application and needs to verify the process actually runs before tagging. The proposed validation is: Inspect the rule logic, endpoint reported facts, resulting tag and any propagated FortiGate group before allowing sensitive access. Which result BEST demonstrates that the requirement is satisfied? Select ONE best answer.
- The gateway accepts a legitimate managed device certificate and rejects invalid or untrusted device material.
- A representative client adopts the approved policy and reports a matching applied version.
- A clean recovery exercise restores representative profiles and endpoint records within the approved recovery objective.
- Compliant managed devices receive the intended tag and ineligible devices remain outside the privileged group.
Explanation
Correct Answer
D:The intended acceptance criterion is: Compliant managed devices receive the intended tag and ineligible devices remain outside the privileged group. Confirm it through: Inspect the rule logic, endpoint reported facts, resulting tag and any propagated FortiGate group before allowing sensitive access. The associated corrective action is: Build EMS security posture rules from verifiable endpoint facts such as supported OS versions, domains and running processes.
Incorrect Answers
A:That option concerns ZTNA device certificates and endpoint authentication chain. The associated corrective action is: Build EMS security posture rules from verifiable endpoint facts such as supported OS versions, domains and running processes.
B:That option concerns Policy delivery lag and endpoint reconnection. The associated corrective action is: Build EMS security posture rules from verifiable endpoint facts such as supported OS versions, domains and running processes.
C:That option concerns EMS database backup and disaster recovery validation. The associated corrective action is: Build EMS security posture rules from verifiable endpoint facts such as supported OS versions, domains and running processes.
Question 360
A FortiClient EMS administrator prepares a focused response to this scenario. A campus uses process-presence posture to protect a finance application and needs to verify the process actually runs before tagging. Which TWO complementary steps combine the most appropriate action and direct verification? Select TWO answers.
- Record backup timestamp, storage protection, application version and a rehearsal restore into an isolated test environment.
- Build EMS security posture rules from verifiable endpoint facts such as supported OS versions, domains and running processes.
- Use a controlled EMS invitation or endpoint enrollment method that associates a legitimate device with the correct management instance.
- Check FortiClient version, relevant logs, timestamps, error codes, local network tests and EMS-side connection state.
- Inspect the rule logic, endpoint reported facts, resulting tag and any propagated FortiGate group before allowing sensitive access.
Explanation
Correct Answers
B:The targeted next step is: Build EMS security posture rules from verifiable endpoint facts such as supported OS versions, domains and running processes.
E:The discriminating evidence is: Inspect the rule logic, endpoint reported facts, resulting tag and any propagated FortiGate group before allowing sensitive access.
Incorrect Answers
A:This evidence belongs to the distinct FortiClient EMS topic EMS database backup and disaster recovery validation, not the case-specific issue of Security posture tagging from operating-system facts described here (A campus uses process-presence posture to protect a finance application and needs to verify the process actually runs before tagging.).
C:This action belongs to the distinct FortiClient EMS topic FortiClient registration invitations and enrollment identity, not the case-specific issue of Security posture tagging from operating-system facts described here (A campus uses process-presence posture to protect a finance application and needs to verify the process actually runs before tagging.). The targeted action for this case is: Build EMS security posture rules from verifiable endpoint facts such as supported OS versions, domains and running processes.
D:This evidence belongs to the distinct FortiClient EMS topic FortiClient diagnostic logging collection from endpoint, not the case-specific issue of Security posture tagging from operating-system facts described here (A campus uses process-presence posture to protect a finance application and needs to verify the process actually runs before tagging.).