McAfee-Secured Website

Exam Code: FCP_FCT_AD-7.4

Exam Name: Fortinet NSE 6 - FortiClient EMS 7.4 Administrator

Certification Provider: Fortinet

Corresponding Certification: NSE6

100% Fortinet FCP_FCT_AD-7.4 Guaranteed Success With Testking Training Materials

Get Real FCP_FCT_AD-7.4 Exam Questions & Expert Verified Answers as Experienced on the Real Exam!

33 Questions & Answers with Testing Engine

"Fortinet NSE 6 - FortiClient EMS 7.4 Administrator Exam", also known as FCP_FCT_AD-7.4 exam, is a Fortinet certification exam.

Pass your tests with the always up-to-date FCP_FCT_AD-7.4 Exam Engine. Your FCP_FCT_AD-7.4 training materials keep you at the head of the pack!

Satisfaction Guaranteed

Money Back Guarantee

Testking provides hassle-free money back guarantee with our products. That is because we have 100% trust in the abilities of our professional and experience product team, and our record is a proof of that.

99.6% PASS RATE
Was: $137.49
Now: $124.99

Fortinet FCP_FCT_AD-7.4 Practice Test 65

Question 640

Original fictional FortiClient EMS 7.4 practice case R181-CASE-160 — Insurance broker checking incident response. Observed evidence: A previously compliant endpoint stays in the allowed application group after quarantine is applied. Which follow-up operational gate best detects a recurrence of the same failure after recovery?

  1. Add a tested post-change acceptance gate requiring this outcome: The quarantined endpoint loses access while other compliant devices remain authorized. Flag any recurrence of this warning sign: A previously compliant endpoint stays in the allowed application group after quarantine is applied.
  2. Add a tested post-change acceptance gate requiring this outcome: A compliant managed laptop connects and the noncompliant device is denied. Flag any recurrence of this warning sign: A valid user account can access a protected application from a noncompliant laptop.
  3. Add a tested post-change acceptance gate requiring this outcome: The client establishes its protected application session with verified certificate identity. Flag any recurrence of this warning sign: The user and device are trusted but the client cannot complete ZTNA mutual certificate validation.
  4. Add a tested post-change acceptance gate requiring this outcome: The verified test user acquires the correct tag after login. Flag any recurrence of this warning sign: A user identity tag is never applied after a client authenticates to EMS.

Explanation

Correct Answer

A:

The preventive gate explicitly checks: The quarantined endpoint loses access while other compliant devices remain authorized, and escalates recurrence of: A previously compliant endpoint stays in the allowed application group after quarantine is applied. That pair addresses the identified issue: ZTNA policy does not react correctly to the changed endpoint state. The control is derived from the case recovery evidence, not separately certified by a Fortinet subject-matter expert.

Incorrect Answers

B:

Incorrect for this incident. That acceptance gate guards against a different situation: A valid user account can access a protected application from a noncompliant laptop. The current failure to watch for is: A previously compliant endpoint stays in the allowed application group after quarantine is applied. Use a monitored gate confirming: The quarantined endpoint loses access while other compliant devices remain authorized.

C:

Incorrect for this incident. That acceptance gate guards against a different situation: The user and device are trusted but the client cannot complete ZTNA mutual certificate validation. The current failure to watch for is: A previously compliant endpoint stays in the allowed application group after quarantine is applied. Use a monitored gate confirming: The quarantined endpoint loses access while other compliant devices remain authorized.

D:

Incorrect for this incident. That acceptance gate guards against a different situation: A user identity tag is never applied after a client authenticates to EMS. The current failure to watch for is: A previously compliant endpoint stays in the allowed application group after quarantine is applied. Use a monitored gate confirming: The quarantined endpoint loses access while other compliant devices remain authorized.

Question 641

Original fictional FortiClient EMS 7.4 practice case R181-CASE-161 — University help desk investigating enrollment. Observed evidence: EMS shows a newly installed client as disconnected even though the installer exited successfully. Which focused administrator action best resolves the identified problem while preserving unrelated security controls?

  1. Inspect signature-service reachability and update-module logs.
  2. Inspect module health, assigned profile and relevant event pipeline.
  3. Check the agent's EMS target, connectivity and telemetry logs before reinstalling.
  4. Correlate timestamps and repair the narrowly scoped network rule.

Explanation

Correct Answer

C:

Correct for this fictional case. The distinguishing signal is: EMS shows a newly installed client as disconnected even though the installer exited successfully. It points to: Installer completion does not establish a working telemetry session to EMS. The targeted correction is: Check the agent's EMS target, connectivity and telemetry logs before reinstalling. Verify success by checking: The client establishes a verified telemetry session and appears online. The response is scoped to this observed failure and should not weaken other policies.

Incorrect Answers

A:

Incorrect for these case facts. This action is more directly suited to another hypothetical case where: Endpoint protection updates fail while EMS administration and telemetry remain available. That case concerns: Security update distribution has a separate external dependency from the EMS console. Here the observed distinction is: EMS shows a newly installed client as disconnected even though the installer exited successfully. A more directly targeted response is: Check the agent's EMS target, connectivity and telemetry logs before reinstalling.

B:

Incorrect for these case facts. This action is more directly suited to another hypothetical case where: EMS records agent telemetry but not the expected antivirus detection events. That case concerns: Detection or reporting module configuration differs from normal endpoint-management connectivity. Here the observed distinction is: EMS shows a newly installed client as disconnected even though the installer exited successfully. A more directly targeted response is: Check the agent's EMS target, connectivity and telemetry logs before reinstalling.

D:

Incorrect for these case facts. This action is more directly suited to another hypothetical case where: Client connection drops coincide with a firewall log denying an EMS service connection. That case concerns: An intermediate policy intermittently blocks required endpoint management traffic. Here the observed distinction is: EMS shows a newly installed client as disconnected even though the installer exited successfully. A more directly targeted response is: Check the agent's EMS target, connectivity and telemetry logs before reinstalling.

Question 642

Original fictional FortiClient EMS 7.4 practice case R181-CASE-161 — University help desk investigating enrollment. Observed evidence: EMS shows a newly installed client as disconnected even though the installer exited successfully. After the scoped corrective action, which observation best confirms this specific incident was resolved?

  1. The client establishes a verified telemetry session and appears online.
  2. The client downloads the intended definitions without opening unrelated services.
  3. Agent check-ins remain stable and deny logs stop for the approved service.
  4. A controlled detection test appears in the correct EMS event history.

Explanation

Correct Answer

A:

This is the case-specific acceptance evidence after taking the targeted step: Check the agent's EMS target, connectivity and telemetry logs before reinstalling. The initial signal was: EMS shows a newly installed client as disconnected even though the installer exited successfully. A generic online indication alone would not prove this particular issue was resolved: Installer completion does not establish a working telemetry session to EMS.

Incorrect Answers

B:

Incorrect for this incident. This result would support a different diagnosis: Security update distribution has a separate external dependency from the EMS console; its warning sign is: Endpoint protection updates fail while EMS administration and telemetry remain available. The current case instead requires verification that: The client establishes a verified telemetry session and appears online. That follows remediation of: Installer completion does not establish a working telemetry session to EMS.

C:

Incorrect for this incident. This result would support a different diagnosis: An intermediate policy intermittently blocks required endpoint management traffic; its warning sign is: Client connection drops coincide with a firewall log denying an EMS service connection. The current case instead requires verification that: The client establishes a verified telemetry session and appears online. That follows remediation of: Installer completion does not establish a working telemetry session to EMS.

D:

Incorrect for this incident. This result would support a different diagnosis: Detection or reporting module configuration differs from normal endpoint-management connectivity; its warning sign is: EMS records agent telemetry but not the expected antivirus detection events. The current case instead requires verification that: The client establishes a verified telemetry session and appears online. That follows remediation of: Installer completion does not establish a working telemetry session to EMS.

Question 643

Original fictional FortiClient EMS 7.4 practice case R181-CASE-161 — University help desk investigating enrollment. Observed evidence: EMS shows a newly installed client as disconnected even though the installer exited successfully. Which management, security, or integration failure most directly explains the evidence?

  1. Security update distribution has a separate external dependency from the EMS console.
  2. Installer completion does not establish a working telemetry session to EMS.
  3. An intermediate policy intermittently blocks required endpoint management traffic.
  4. Detection or reporting module configuration differs from normal endpoint-management connectivity.

Explanation

Correct Answer

B:

The supplied evidence — EMS shows a newly installed client as disconnected even though the installer exited successfully — most directly supports: Installer completion does not establish a working telemetry session to EMS. Confirm the explanation by applying the controlled correction: Check the agent's EMS target, connectivity and telemetry logs before reinstalling; then checking that: The client establishes a verified telemetry session and appears online. Similar symptoms can have other causes in real deployments.

Incorrect Answers

A:

Incorrect for the stated evidence. This alternative concern better explains a different situation: Endpoint protection updates fail while EMS administration and telemetry remain available. Here the actual observation — EMS shows a newly installed client as disconnected even though the installer exited successfully — most directly indicates: Installer completion does not establish a working telemetry session to EMS. The scoped correction is: Check the agent's EMS target, connectivity and telemetry logs before reinstalling.

C:

Incorrect for the stated evidence. This alternative concern better explains a different situation: Client connection drops coincide with a firewall log denying an EMS service connection. Here the actual observation — EMS shows a newly installed client as disconnected even though the installer exited successfully — most directly indicates: Installer completion does not establish a working telemetry session to EMS. The scoped correction is: Check the agent's EMS target, connectivity and telemetry logs before reinstalling.

D:

Incorrect for the stated evidence. This alternative concern better explains a different situation: EMS records agent telemetry but not the expected antivirus detection events. Here the actual observation — EMS shows a newly installed client as disconnected even though the installer exited successfully — most directly indicates: Installer completion does not establish a working telemetry session to EMS. The scoped correction is: Check the agent's EMS target, connectivity and telemetry logs before reinstalling.

Question 644

Original fictional FortiClient EMS 7.4 practice case R181-CASE-161 — University help desk investigating enrollment. Observed evidence: EMS shows a newly installed client as disconnected even though the installer exited successfully. Which follow-up operational gate best detects a recurrence of the same failure after recovery?

  1. Add a tested post-change acceptance gate requiring this outcome: Agent check-ins remain stable and deny logs stop for the approved service. Flag any recurrence of this warning sign: Client connection drops coincide with a firewall log denying an EMS service connection.
  2. Add a tested post-change acceptance gate requiring this outcome: A controlled detection test appears in the correct EMS event history. Flag any recurrence of this warning sign: EMS records agent telemetry but not the expected antivirus detection events.
  3. Add a tested post-change acceptance gate requiring this outcome: The client establishes a verified telemetry session and appears online. Flag any recurrence of this warning sign: EMS shows a newly installed client as disconnected even though the installer exited successfully.
  4. Add a tested post-change acceptance gate requiring this outcome: The client downloads the intended definitions without opening unrelated services. Flag any recurrence of this warning sign: Endpoint protection updates fail while EMS administration and telemetry remain available.

Explanation

Correct Answer

C:

The preventive gate explicitly checks: The client establishes a verified telemetry session and appears online, and escalates recurrence of: EMS shows a newly installed client as disconnected even though the installer exited successfully. That pair addresses the identified issue: Installer completion does not establish a working telemetry session to EMS. The control is derived from the case recovery evidence, not separately certified by a Fortinet subject-matter expert.

Incorrect Answers

A:

Incorrect for this incident. That acceptance gate guards against a different situation: Client connection drops coincide with a firewall log denying an EMS service connection. The current failure to watch for is: EMS shows a newly installed client as disconnected even though the installer exited successfully. Use a monitored gate confirming: The client establishes a verified telemetry session and appears online.

B:

Incorrect for this incident. That acceptance gate guards against a different situation: EMS records agent telemetry but not the expected antivirus detection events. The current failure to watch for is: EMS shows a newly installed client as disconnected even though the installer exited successfully. Use a monitored gate confirming: The client establishes a verified telemetry session and appears online.

D:

Incorrect for this incident. That acceptance gate guards against a different situation: Endpoint protection updates fail while EMS administration and telemetry remain available. The current failure to watch for is: EMS shows a newly installed client as disconnected even though the installer exited successfully. Use a monitored gate confirming: The client establishes a verified telemetry session and appears online.

Question 645

Original fictional FortiClient EMS 7.4 practice case R181-CASE-162 — Regional hospital investigating intermittent reachability. Observed evidence: Client connection drops coincide with a firewall log denying an EMS service connection. Which focused administrator action best resolves the identified problem while preserving unrelated security controls?

  1. Check EMS quarantine status and the associated incident case before network changes.
  2. Diagnose the management link independently of ordinary client data traffic.
  3. Compare EMS inventory, policy assignment and agent profile versions.
  4. Correlate timestamps and repair the narrowly scoped network rule.

Explanation

Correct Answer

D:

Correct for this fictional case. The distinguishing signal is: Client connection drops coincide with a firewall log denying an EMS service connection. It points to: An intermediate policy intermittently blocks required endpoint management traffic. The targeted correction is: Correlate timestamps and repair the narrowly scoped network rule. Verify success by checking: Agent check-ins remain stable and deny logs stop for the approved service. The response is scoped to this observed failure and should not weaken other policies.

Incorrect Answers

A:

Incorrect for these case facts. This action is more directly suited to another hypothetical case where: Support receives calls about network loss but does not inspect whether the devices were intentionally quarantined. That case concerns: Security response state was omitted from connectivity triage. Here the observed distinction is: Client connection drops coincide with a firewall log denying an EMS service connection. A more directly targeted response is: Correlate timestamps and repair the narrowly scoped network rule.

B:

Incorrect for these case facts. This action is more directly suited to another hypothetical case where: EMS dashboard shows a branch offline although local devices still have working application access. That case concerns: EMS management state is being treated as an application forwarding failure. Here the observed distinction is: Client connection drops coincide with a firewall log denying an EMS service connection. A more directly targeted response is: Correlate timestamps and repair the narrowly scoped network rule.

C:

Incorrect for these case facts. This action is more directly suited to another hypothetical case where: Two endpoints in the same claimed group receive different security settings. That case concerns: Effective group membership and policy revision have not been reconciled per endpoint. Here the observed distinction is: Client connection drops coincide with a firewall log denying an EMS service connection. A more directly targeted response is: Correlate timestamps and repair the narrowly scoped network rule.

Question 646

Original fictional FortiClient EMS 7.4 practice case R181-CASE-162 — Regional hospital investigating intermittent reachability. Observed evidence: Client connection drops coincide with a firewall log denying an EMS service connection. After the scoped corrective action, which observation best confirms this specific incident was resolved?

  1. Agent check-ins remain stable and deny logs stop for the approved service.
  2. Both pilot endpoints report the appropriate intended effective configuration.
  3. The test diagnosis correctly distinguishes intentional isolation from link failure.
  4. Endpoint management reconnects while application forwarding remains unchanged.

Explanation

Correct Answer

A:

This is the case-specific acceptance evidence after taking the targeted step: Correlate timestamps and repair the narrowly scoped network rule. The initial signal was: Client connection drops coincide with a firewall log denying an EMS service connection. A generic online indication alone would not prove this particular issue was resolved: An intermediate policy intermittently blocks required endpoint management traffic.

Incorrect Answers

B:

Incorrect for this incident. This result would support a different diagnosis: Effective group membership and policy revision have not been reconciled per endpoint; its warning sign is: Two endpoints in the same claimed group receive different security settings. The current case instead requires verification that: Agent check-ins remain stable and deny logs stop for the approved service. That follows remediation of: An intermediate policy intermittently blocks required endpoint management traffic.

C:

Incorrect for this incident. This result would support a different diagnosis: Security response state was omitted from connectivity triage; its warning sign is: Support receives calls about network loss but does not inspect whether the devices were intentionally quarantined. The current case instead requires verification that: Agent check-ins remain stable and deny logs stop for the approved service. That follows remediation of: An intermediate policy intermittently blocks required endpoint management traffic.

D:

Incorrect for this incident. This result would support a different diagnosis: EMS management state is being treated as an application forwarding failure; its warning sign is: EMS dashboard shows a branch offline although local devices still have working application access. The current case instead requires verification that: Agent check-ins remain stable and deny logs stop for the approved service. That follows remediation of: An intermediate policy intermittently blocks required endpoint management traffic.

Question 647

Original fictional FortiClient EMS 7.4 practice case R181-CASE-162 — Regional hospital investigating intermittent reachability. Observed evidence: Client connection drops coincide with a firewall log denying an EMS service connection. Which management, security, or integration failure most directly explains the evidence?

  1. Security response state was omitted from connectivity triage.
  2. Effective group membership and policy revision have not been reconciled per endpoint.
  3. An intermediate policy intermittently blocks required endpoint management traffic.
  4. EMS management state is being treated as an application forwarding failure.

Explanation

Correct Answer

C:

The supplied evidence — Client connection drops coincide with a firewall log denying an EMS service connection — most directly supports: An intermediate policy intermittently blocks required endpoint management traffic. Confirm the explanation by applying the controlled correction: Correlate timestamps and repair the narrowly scoped network rule; then checking that: Agent check-ins remain stable and deny logs stop for the approved service. Similar symptoms can have other causes in real deployments.

Incorrect Answers

A:

Incorrect for the stated evidence. This alternative concern better explains a different situation: Support receives calls about network loss but does not inspect whether the devices were intentionally quarantined. Here the actual observation — Client connection drops coincide with a firewall log denying an EMS service connection — most directly indicates: An intermediate policy intermittently blocks required endpoint management traffic. The scoped correction is: Correlate timestamps and repair the narrowly scoped network rule.

B:

Incorrect for the stated evidence. This alternative concern better explains a different situation: Two endpoints in the same claimed group receive different security settings. Here the actual observation — Client connection drops coincide with a firewall log denying an EMS service connection — most directly indicates: An intermediate policy intermittently blocks required endpoint management traffic. The scoped correction is: Correlate timestamps and repair the narrowly scoped network rule.

D:

Incorrect for the stated evidence. This alternative concern better explains a different situation: EMS dashboard shows a branch offline although local devices still have working application access. Here the actual observation — Client connection drops coincide with a firewall log denying an EMS service connection — most directly indicates: An intermediate policy intermittently blocks required endpoint management traffic. The scoped correction is: Correlate timestamps and repair the narrowly scoped network rule.

Question 648

Original fictional FortiClient EMS 7.4 practice case R181-CASE-162 — Regional hospital investigating intermittent reachability. Observed evidence: Client connection drops coincide with a firewall log denying an EMS service connection. Which follow-up operational gate best detects a recurrence of the same failure after recovery?

  1. Add a tested post-change acceptance gate requiring this outcome: Agent check-ins remain stable and deny logs stop for the approved service. Flag any recurrence of this warning sign: Client connection drops coincide with a firewall log denying an EMS service connection.
  2. Add a tested post-change acceptance gate requiring this outcome: Both pilot endpoints report the appropriate intended effective configuration. Flag any recurrence of this warning sign: Two endpoints in the same claimed group receive different security settings.
  3. Add a tested post-change acceptance gate requiring this outcome: The test diagnosis correctly distinguishes intentional isolation from link failure. Flag any recurrence of this warning sign: Support receives calls about network loss but does not inspect whether the devices were intentionally quarantined.
  4. Add a tested post-change acceptance gate requiring this outcome: Endpoint management reconnects while application forwarding remains unchanged. Flag any recurrence of this warning sign: EMS dashboard shows a branch offline although local devices still have working application access.

Explanation

Correct Answer

A:

The preventive gate explicitly checks: Agent check-ins remain stable and deny logs stop for the approved service, and escalates recurrence of: Client connection drops coincide with a firewall log denying an EMS service connection. That pair addresses the identified issue: An intermediate policy intermittently blocks required endpoint management traffic. The control is derived from the case recovery evidence, not separately certified by a Fortinet subject-matter expert.

Incorrect Answers

B:

Incorrect for this incident. That acceptance gate guards against a different situation: Two endpoints in the same claimed group receive different security settings. The current failure to watch for is: Client connection drops coincide with a firewall log denying an EMS service connection. Use a monitored gate confirming: Agent check-ins remain stable and deny logs stop for the approved service.

C:

Incorrect for this incident. That acceptance gate guards against a different situation: Support receives calls about network loss but does not inspect whether the devices were intentionally quarantined. The current failure to watch for is: Client connection drops coincide with a firewall log denying an EMS service connection. Use a monitored gate confirming: Agent check-ins remain stable and deny logs stop for the approved service.

D:

Incorrect for this incident. That acceptance gate guards against a different situation: EMS dashboard shows a branch offline although local devices still have working application access. The current failure to watch for is: Client connection drops coincide with a firewall log denying an EMS service connection. Use a monitored gate confirming: Agent check-ins remain stable and deny logs stop for the approved service.

Question 649

Original fictional FortiClient EMS 7.4 practice case R181-CASE-163 — Retail chain diagnosing incorrect profiles. Observed evidence: Two endpoints in the same claimed group receive different security settings. Which focused administrator action best resolves the identified problem while preserving unrelated security controls?

  1. Compare EMS inventory, policy assignment and agent profile versions.
  2. Inspect the certificate chain, hostname and trusted replacement sequence.
  3. Check time synchronization and normalize event timestamps before analyzing the sequence.
  4. Correlate Fabric connector logs, trust state and permitted network path.

Explanation

Correct Answer

A:

Correct for this fictional case. The distinguishing signal is: Two endpoints in the same claimed group receive different security settings. It points to: Effective group membership and policy revision have not been reconciled per endpoint. The targeted correction is: Compare EMS inventory, policy assignment and agent profile versions. Verify success by checking: Both pilot endpoints report the appropriate intended effective configuration. The response is scoped to this observed failure and should not weaken other policies.

Incorrect Answers

B:

Incorrect for these case facts. This action is more directly suited to another hypothetical case where: FortiClient diagnostics show repeated TLS rejection immediately after a new EMS certificate rollout. That case concerns: The client no longer trusts the EMS server's presented management identity. Here the observed distinction is: Two endpoints in the same claimed group receive different security settings. A more directly targeted response is: Compare EMS inventory, policy assignment and agent profile versions.

C:

Incorrect for these case facts. This action is more directly suited to another hypothetical case where: Logs from the EMS host and clients appear to disagree about the order of a threat incident. That case concerns: Host and endpoint clock offsets prevent reliable event correlation. Here the observed distinction is: Two endpoints in the same claimed group receive different security settings. A more directly targeted response is: Compare EMS inventory, policy assignment and agent profile versions.

D:

Incorrect for these case facts. This action is more directly suited to another hypothetical case where: The Fabric connector is marked disconnected but EMS agents show healthy status. That case concerns: FortiGate-EMS integration has failed independently of endpoint enrollment. Here the observed distinction is: Two endpoints in the same claimed group receive different security settings. A more directly targeted response is: Compare EMS inventory, policy assignment and agent profile versions.

Question 650

Original fictional FortiClient EMS 7.4 practice case R181-CASE-163 — Retail chain diagnosing incorrect profiles. Observed evidence: Two endpoints in the same claimed group receive different security settings. After the scoped corrective action, which observation best confirms this specific incident was resolved?

  1. TLS telemetry authenticates against the verified EMS identity.
  2. A replayed event timeline aligns across EMS and FortiClient records.
  3. Both pilot endpoints report the appropriate intended effective configuration.
  4. The connector returns healthy and security tags synchronize.

Explanation

Correct Answer

C:

This is the case-specific acceptance evidence after taking the targeted step: Compare EMS inventory, policy assignment and agent profile versions. The initial signal was: Two endpoints in the same claimed group receive different security settings. A generic online indication alone would not prove this particular issue was resolved: Effective group membership and policy revision have not been reconciled per endpoint.

Incorrect Answers

A:

Incorrect for this incident. This result would support a different diagnosis: The client no longer trusts the EMS server's presented management identity; its warning sign is: FortiClient diagnostics show repeated TLS rejection immediately after a new EMS certificate rollout. The current case instead requires verification that: Both pilot endpoints report the appropriate intended effective configuration. That follows remediation of: Effective group membership and policy revision have not been reconciled per endpoint.

B:

Incorrect for this incident. This result would support a different diagnosis: Host and endpoint clock offsets prevent reliable event correlation; its warning sign is: Logs from the EMS host and clients appear to disagree about the order of a threat incident. The current case instead requires verification that: Both pilot endpoints report the appropriate intended effective configuration. That follows remediation of: Effective group membership and policy revision have not been reconciled per endpoint.

D:

Incorrect for this incident. This result would support a different diagnosis: FortiGate-EMS integration has failed independently of endpoint enrollment; its warning sign is: The Fabric connector is marked disconnected but EMS agents show healthy status. The current case instead requires verification that: Both pilot endpoints report the appropriate intended effective configuration. That follows remediation of: Effective group membership and policy revision have not been reconciled per endpoint.

Fortinet NSE 6 - FortiClient EMS 7.4 Administrator (FCP_FCT_AD-7.4) Practice Tests