Fortinet NSE5_FSW_AD-7.6 (Fortinet NSE 5 - FortiSwitch 7.6 Administrator) Practice Test 26

Question 250

Before applying the planned operation “Authorize a discovered FortiSwitch on FortiGate” at the conference venue, the administrator must predict its impact. Which prediction is sound?

  1. SNMP provides structured operational measurements without becoming the forwarding control plane
  2. Controller authorization allows the FortiGate to provision and manage that switch via FortiLink
  3. Controller deauthorization changes the authorization relationship and may affect switch reset or password retention
  4. Firmware maintenance for managed switches should be coordinated through the FortiGate management workflow

Explanation

Correct Answer

B:

Given the described goal, the configured operation is meant to move an already discovered unit into centrally managed service. The most relevant validation is to check the managed-switch inventory for an authorized state and configuration synchronization for the equipment at the conference venue.

Incorrect Answers

A:

This outcome would be relevant to “Configure remote monitoring through SNMP” at the conference venue, not the task “Authorize a discovered FortiSwitch on FortiGate”; the other task is to expose interface and switch health telemetry to an authorized monitoring collector. The action “Authorize a discovered FortiSwitch on FortiGate” targets a different result: controller authorization allows the FortiGate to provision and manage that switch via FortiLink; the proposed alternative would instead be checked by poll system and interface identifiers from the configured monitoring station.

C:

That behavior applies when engineers “Deauthorize a retired managed switch deliberately”; the different operation “Authorize a discovered FortiSwitch on FortiGate” is intended to move an already discovered unit into centrally managed service. That different feature is verified by confirm the intended serial number is no longer authorized and review the deauthorization policy; for “Authorize a discovered FortiSwitch on FortiGate” on a managed switch running FortiSwitchOS 7.6, the relevant evidence is to check the managed-switch inventory for an authorized state and configuration synchronization.

D:

That behavior applies when engineers “Perform a centrally coordinated FortiSwitch firmware update”; the different operation “Authorize a discovered FortiSwitch on FortiGate” is intended to move an already discovered unit into centrally managed service. That different feature is verified by verify intended image version, upgrade status and post-reboot switch connectivity; for “Authorize a discovered FortiSwitch on FortiGate” on a managed switch running FortiSwitchOS 7.6, the relevant evidence is to check the managed-switch inventory for an authorized state and configuration synchronization.

Question 251

The work order to move an already discovered unit into centrally managed service is marked complete on a remote FortiSwitch installation. Which observation most directly tests the completed configuration?

  1. Check the managed-switch inventory for an authorized state and configuration synchronization
  2. Confirm local management access and that the unit is not assigned to a FortiGate controller
  3. Compare FortiGate and FortiSwitch system clocks and NTP association state
  4. Look for switch presence and expected topology information in the Fabric view
  5. Confirm device registration, service connectivity and cloud-visible online state

Explanation

Correct Answer

A:

The switch behavior that matters is: controller authorization allows the FortiGate to provision and manage that switch via FortiLink. Directly measuring that result demonstrates whether the step to move an already discovered unit into centrally managed service succeeded on a remote FortiSwitch installation.

Incorrect Answers

B:

The proposed check concerns “Operate a FortiSwitch in standalone mode” rather than “Authorize a discovered FortiSwitch on FortiGate”: standalone mode exposes local configuration and administration on the switch itself. For “Authorize a discovered FortiSwitch on FortiGate” on a remote FortiSwitch installation, a better test would be to check the managed-switch inventory for an authorized state and configuration synchronization, which targets move an already discovered unit into centrally managed service rather than the alternative diagnostic “Operate a FortiSwitch in standalone mode”.

C:

This check is suited to “Enable time synchronization for managed units” when trying to prevent clock drift from confusing authentication and event correlation, not to verify “Authorize a discovered FortiSwitch on FortiGate” at the campus. Checking “Authorize a discovered FortiSwitch on FortiGate” at the campus requires evidence of its own mechanism: controller authorization allows the FortiGate to provision and manage that switch via FortiLink; that is not the outcome measured by “Enable time synchronization for managed units”.

D:

This check is suited to “Integrate switch status with the Security Fabric” when trying to provide visibility of managed access infrastructure in the Fortinet environment, not to verify “Authorize a discovered FortiSwitch on FortiGate” at the campus. Checking “Authorize a discovered FortiSwitch on FortiGate” at the campus requires evidence of its own mechanism: controller authorization allows the FortiGate to provision and manage that switch via FortiLink; that is not the outcome measured by “Integrate switch status with the Security Fabric”.

E:

The proposed check concerns “Use FortiEdge Cloud management for a supported switch” rather than “Authorize a discovered FortiSwitch on FortiGate”: a cloud management workflow connects the registered switch to the appropriate Fortinet service. For “Authorize a discovered FortiSwitch on FortiGate” on a remote FortiSwitch installation, a better test would be to check the managed-switch inventory for an authorized state and configuration synchronization, which targets move an already discovered unit into centrally managed service rather than the alternative diagnostic “Use FortiEdge Cloud management for a supported switch”.

Question 252

A switch rollout in the remote depot will be approved only if it can reduce manual approvals for trusted units on a controlled provisioning network. Which administrative action meets this acceptance criterion?

  1. Operate a FortiSwitch in standalone mode
  2. Integrate switch status with the Security Fabric
  3. Enable time synchronization for managed units
  4. Enable automatic FortiSwitch authorization where appropriate

Explanation

Correct Answer

D:

At this network boundary, the FortiLink controller can authorize discovered devices automatically when that setting is enabled. The operator can test this claim by the specific check: observe whether a newly discovered serial number becomes authorized without manual action.

Incorrect Answers

A:

Compared with the requested “Enable automatic FortiSwitch authorization where appropriate” at the remote depot, this would manage a switch locally without delegating configuration to a FortiGate instead: standalone mode exposes local configuration and administration on the switch itself. At the remote depot, the operational proof would instead be to observe whether a newly discovered serial number becomes authorized without manual action, whereas “Operate a FortiSwitch in standalone mode” is validated by a different test: confirm local management access and that the unit is not assigned to a FortiGate controller.

B:

Compared with the requested “Enable automatic FortiSwitch authorization where appropriate” at the remote depot, this would provide visibility of managed access infrastructure in the Fortinet environment instead: controller and Fabric integration correlate switch topology and endpoint observations with FortiGate management. At the remote depot, the operational proof would instead be to observe whether a newly discovered serial number becomes authorized without manual action, whereas “Integrate switch status with the Security Fabric” is validated by a different test: look for switch presence and expected topology information in the Fabric view.

C:

For the remote depot, “Enable time synchronization for managed units” is a different type of control from “Enable automatic FortiSwitch authorization where appropriate”: a reachable NTP source supplies consistent time to switch and controller management processes. Unlike the requested feature, that setting addresses the need to prevent clock drift from confusing authentication and event correlation, not the objective to reduce manual approvals for trusted units on a controlled provisioning network.

Question 253

During validation of a standalone FortiSwitch appliance at the branch office, the team asks what the change “Enable automatic FortiSwitch authorization where appropriate” actually does. Which outcome is correct?

  1. Grouping units supports consistent profile or administrative treatment across selected devices
  2. FortiLink enablement distinguishes the switch-controller link from an ordinary production interface
  3. The FortiLink controller can authorize discovered devices automatically when that setting is enabled
  4. A migration script can translate and reapply supported standalone settings for managed deployment

Explanation

Correct Answer

C:

In this deployment, the configured operation is meant to reduce manual approvals for trusted units on a controlled provisioning network. The most relevant validation is to observe whether a newly discovered serial number becomes authorized without manual action for the equipment at the branch office.

Incorrect Answers

A:

This outcome would be relevant to “Create a FortiSwitch group for common administration” at the branch office, not the task “Enable automatic FortiSwitch authorization where appropriate”; the other task is to apply shared settings to several managed switches with related roles. The action “Enable automatic FortiSwitch authorization where appropriate” targets a different result: the FortiLink controller can authorize discovered devices automatically when that setting is enabled; the proposed alternative would instead be checked by check each intended serial number's group membership and inherited configuration.

B:

That behavior applies when engineers “Mark a FortiGate interface as dedicated to FortiSwitch”; the different operation “Enable automatic FortiSwitch authorization where appropriate” is intended to reduce manual approvals for trusted units on a controlled provisioning network. That different feature is verified by inspect the interface's FortiLink dedication and switch discovery on the connected port; for “Enable automatic FortiSwitch authorization where appropriate” on a standalone FortiSwitch appliance, the relevant evidence is to observe whether a newly discovered serial number becomes authorized without manual action.

D:

That behavior applies when engineers “Migrate standalone settings with an approved script”; the different operation “Enable automatic FortiSwitch authorization where appropriate” is intended to reduce manual approvals for trusted units on a controlled provisioning network. That different feature is verified by diff the required old settings against the resulting controller-managed configuration; for “Enable automatic FortiSwitch authorization where appropriate” on a standalone FortiSwitch appliance, the relevant evidence is to observe whether a newly discovered serial number becomes authorized without manual action.

Question 254

A technician says “Enable automatic FortiSwitch authorization where appropriate” has solved the issue at the factory. Which diagnostic step would substantiate that claim?

  1. Inspect the neighbor-detection method and observed adjacency in the active FortiLink connection
  2. Review the controller's managed-switch configuration and ensuing synchronization status
  3. Inspect enabled administrative protocols and test reachability from an approved source
  4. Observe whether a newly discovered serial number becomes authorized without manual action
  5. Check the backup file timestamp and availability before starting maintenance

Explanation

Correct Answer

D:

For the stated requirement, the FortiLink controller can authorize discovered devices automatically when that setting is enabled. Directly measuring that result demonstrates whether the step to reduce manual approvals for trusted units on a controlled provisioning network succeeded on a newly commissioned floor switch.

Incorrect Answers

A:

The proposed check concerns “Enable neighbor detection appropriate for the FortiLink deployment” rather than “Enable automatic FortiSwitch authorization where appropriate”: FortiLink discovery uses configured neighbor detection; FortiOS 7.6.1 uses LLDP as its default method. For “Enable automatic FortiSwitch authorization where appropriate” on a newly commissioned floor switch, a better test would be to observe whether a newly discovered serial number becomes authorized without manual action, which targets reduce manual approvals for trusted units on a controlled provisioning network rather than the alternative diagnostic “Enable neighbor detection appropriate for the FortiLink deployment”.

B:

This check is suited to “Use FortiGate switch-controller CLI” when trying to carry out a repeatable centrally managed configuration using commands, not to verify “Enable automatic FortiSwitch authorization where appropriate” at the factory. Checking “Enable automatic FortiSwitch authorization where appropriate” at the factory requires evidence of its own mechanism: the FortiLink controller can authorize discovered devices automatically when that setting is enabled; that is not the outcome measured by “Use FortiGate switch-controller CLI”.

C:

This check is suited to “Restrict administrative protocols on switch management interfaces” when trying to reduce exposure of the switch control plane to unauthorized clients, not to verify “Enable automatic FortiSwitch authorization where appropriate” at the factory. Checking “Enable automatic FortiSwitch authorization where appropriate” at the factory requires evidence of its own mechanism: the FortiLink controller can authorize discovered devices automatically when that setting is enabled; that is not the outcome measured by “Restrict administrative protocols on switch management interfaces”.

E:

The proposed check concerns “Back up FortiSwitch configuration before upgrades” rather than “Enable automatic FortiSwitch authorization where appropriate”: a configuration export preserves management settings independently of the device's current runtime state. For “Enable automatic FortiSwitch authorization where appropriate” on a newly commissioned floor switch, a better test would be to observe whether a newly discovered serial number becomes authorized without manual action, which targets reduce manual approvals for trusted units on a controlled provisioning network rather than the alternative diagnostic “Back up FortiSwitch configuration before upgrades”.

Question 255

During a change window in the research building, engineers are asked to make a chosen Ethernet interface function as a FortiLink management attachment. What should they configure rather than using a feature for an adjacent purpose?

  1. Integrate switch status with the Security Fabric
  2. Review FortiSwitch serial number during onboarding
  3. Mark a FortiGate interface as dedicated to FortiSwitch
  4. Operate a FortiSwitch in standalone mode

Explanation

Correct Answer

C:

The deciding detail is that FortiLink enablement distinguishes the switch-controller link from an ordinary production interface. This distinction is material to the research building, where the stated goal is to make a chosen Ethernet interface function as a FortiLink management attachment.

Incorrect Answers

A:

Compared with the requested “Mark a FortiGate interface as dedicated to FortiSwitch” at the research building, this would provide visibility of managed access infrastructure in the Fortinet environment instead: controller and Fabric integration correlate switch topology and endpoint observations with FortiGate management. At the research building, the operational proof would instead be to inspect the interface's FortiLink dedication and switch discovery on the connected port, whereas “Integrate switch status with the Security Fabric” is validated by a different test: look for switch presence and expected topology information in the Fabric view.

B:

Compared with the requested “Mark a FortiGate interface as dedicated to FortiSwitch” at the research building, this would avoid configuring a similarly named but different discovered unit instead: a unique hardware serial number identifies the FortiSwitch object managed by the controller. At the research building, the operational proof would instead be to inspect the interface's FortiLink dedication and switch discovery on the connected port, whereas “Review FortiSwitch serial number during onboarding” is validated by a different test: match the serial in the physical inventory with the FortiGate discovery listing.

D:

For the research building, “Operate a FortiSwitch in standalone mode” is a different type of control from “Mark a FortiGate interface as dedicated to FortiSwitch”: standalone mode exposes local configuration and administration on the switch itself. Unlike the requested feature, that setting addresses the need to manage a switch locally without delegating configuration to a FortiGate, not the objective to make a chosen Ethernet interface function as a FortiLink management attachment.

Question 256

The operator has decided to mark a FortiGate interface as dedicated to FortiSwitch on a switch used by multiple office teams at the clinic. Which operational behavior is the most reasonable expectation of that specific feature?

  1. FortiLink enablement distinguishes the switch-controller link from an ordinary production interface
  2. FortiLink discovery uses configured neighbor detection; FortiOS 7.6.1 uses LLDP as its default method
  3. The FortiLink controller can authorize discovered devices automatically when that setting is enabled
  4. Grouping units supports consistent profile or administrative treatment across selected devices

Explanation

Correct Answer

A:

The relevant mechanism is: the configured operation is meant to make a chosen Ethernet interface function as a FortiLink management attachment. The most relevant validation is to inspect the interface's FortiLink dedication and switch discovery on the connected port for the equipment at the clinic.

Incorrect Answers

B:

That behavior applies when engineers “Enable neighbor detection appropriate for the FortiLink deployment”; the different operation “Mark a FortiGate interface as dedicated to FortiSwitch” is intended to make a chosen Ethernet interface function as a FortiLink management attachment. That different feature is verified by inspect the neighbor-detection method and observed adjacency in the active FortiLink connection; for “Mark a FortiGate interface as dedicated to FortiSwitch” on a switch used by multiple office teams, the relevant evidence is to inspect the interface's FortiLink dedication and switch discovery on the connected port.

C:

This outcome would be relevant to “Enable automatic FortiSwitch authorization where appropriate” at the clinic, not the task “Mark a FortiGate interface as dedicated to FortiSwitch”; the other task is to reduce manual approvals for trusted units on a controlled provisioning network. The action “Mark a FortiGate interface as dedicated to FortiSwitch” targets a different result: FortiLink enablement distinguishes the switch-controller link from an ordinary production interface; the proposed alternative would instead be checked by observe whether a newly discovered serial number becomes authorized without manual action.

D:

That behavior applies when engineers “Create a FortiSwitch group for common administration”; the different operation “Mark a FortiGate interface as dedicated to FortiSwitch” is intended to make a chosen Ethernet interface function as a FortiLink management attachment. That different feature is verified by check each intended serial number's group membership and inherited configuration; for “Mark a FortiGate interface as dedicated to FortiSwitch” on a switch used by multiple office teams, the relevant evidence is to inspect the interface's FortiLink dedication and switch discovery on the connected port.

Question 257

After implementing “Mark a FortiGate interface as dedicated to FortiSwitch,” the site engineer needs to assess its actual effect on a production FortiSwitch fabric. Which test is the best match?

  1. Inspect the interface's FortiLink dedication and switch discovery on the connected port
  2. Examine controller interface IP settings and switch management address assignment
  3. Check the backup file timestamp and availability before starting maintenance
  4. Review the controller's managed-switch configuration and ensuing synchronization status

Explanation

Correct Answer

A:

This approach fits because FortiLink enablement distinguishes the switch-controller link from an ordinary production interface. Directly measuring that result demonstrates whether the step to make a chosen Ethernet interface function as a FortiLink management attachment succeeded on a production FortiSwitch fabric.

Incorrect Answers

B:

This check is suited to “Assign a reachable FortiLink interface IP subnet” when trying to support switch-controller management communication over the FortiLink connection, not to verify “Mark a FortiGate interface as dedicated to FortiSwitch” at the data hall. Checking “Mark a FortiGate interface as dedicated to FortiSwitch” at the data hall requires evidence of its own mechanism: FortiLink enablement distinguishes the switch-controller link from an ordinary production interface; that is not the outcome measured by “Assign a reachable FortiLink interface IP subnet”.

C:

This check is suited to “Back up FortiSwitch configuration before upgrades” when trying to make recovery possible if a firmware or policy change fails, not to verify “Mark a FortiGate interface as dedicated to FortiSwitch” at the data hall. Checking “Mark a FortiGate interface as dedicated to FortiSwitch” at the data hall requires evidence of its own mechanism: FortiLink enablement distinguishes the switch-controller link from an ordinary production interface; that is not the outcome measured by “Back up FortiSwitch configuration before upgrades”.

D:

The proposed check concerns “Use FortiGate switch-controller CLI” rather than “Mark a FortiGate interface as dedicated to FortiSwitch”: the controller CLI provides managed-switch objects and port settings that can be provisioned to switches. For “Mark a FortiGate interface as dedicated to FortiSwitch” on a production FortiSwitch fabric, a better test would be to inspect the interface's FortiLink dedication and switch discovery on the connected port, which targets make a chosen Ethernet interface function as a FortiLink management attachment rather than the alternative diagnostic “Use FortiGate switch-controller CLI”.

Question 258

For the development floor, the network team needs to allow an unconfigured switch to find its FortiLink controller during installation. Which change is the most direct way to implement that requirement on a newly racked distribution unit?

  1. Check managed-switch configuration synchronization
  2. Send operational messages to an external syslog collector
  3. Check supported model and feature availability before provisioning
  4. Restore the saved standalone configuration locally
  5. Use a supported auto-discovery FortiSwitch port

Explanation

Correct Answer

E:

The critical distinction is that discovery-capable ports advertise and detect controller connectivity without preprogramming the full local switch. The operator can test this claim by the specific check: check the port's model-dependent auto-discovery support and switch discovery event.

Incorrect Answers

A:

Compared with the requested “Use a supported auto-discovery FortiSwitch port” at the development floor, this would detect a switch that has not accepted the controller's latest changes instead: synchronization status identifies divergence between controller intent and provisioned switch state. At the development floor, the operational proof would instead be to check the port's model-dependent auto-discovery support and switch discovery event, whereas “Check managed-switch configuration synchronization” is validated by a different test: compare controller-configured port values with device status and sync indicators.

B:

For the development floor, “Send operational messages to an external syslog collector” is a different type of control from “Use a supported auto-discovery FortiSwitch port”: syslog forwarding exports event records to a reachable collector rather than changing packet forwarding. Unlike the requested feature, that setting addresses the need to retain switch events outside the device for investigation and retention, not the objective to allow an unconfigured switch to find its FortiLink controller during installation.

C:

Compared with the requested “Use a supported auto-discovery FortiSwitch port” at the development floor, this would avoid issuing settings to an unsupported FortiSwitch platform instead: supported capabilities vary by model and hardware; validating the feature matrix prevents invalid configuration assumptions. At the development floor, the operational proof would instead be to check the port's model-dependent auto-discovery support and switch discovery event, whereas “Check supported model and feature availability before provisioning” is validated by a different test: compare the exact SKU and FortiSwitchOS release against the target feature documentation.

D:

Compared with the requested “Use a supported auto-discovery FortiSwitch port” at the development floor, this would recover a locally administered switch after a failed change instead: standalone backup/restore reloads a saved device configuration rather than rebuilding a FortiGate-managed object. At the development floor, the operational proof would instead be to check the port's model-dependent auto-discovery support and switch discovery event, whereas “Restore the saved standalone configuration locally” is validated by a different test: inspect the restored local settings and confirm there is no controller configuration conflict.

Question 259

A switch change for the conference venue consists of this step: use a supported auto-discovery FortiSwitch port. Which behavior reflects the purpose of that change?

  1. FortiGate switch profiles can set managed switch administrative credentials centrally
  2. Controller authorization allows the FortiGate to provision and manage that switch via FortiLink
  3. Role or access profiles restrict management menus and configuration privileges
  4. Discovery-capable ports advertise and detect controller connectivity without preprogramming the full local switch

Explanation

Correct Answer

D:

That setting is appropriate here because the configured operation is meant to allow an unconfigured switch to find its FortiLink controller during installation. The most relevant validation is to check the port's model-dependent auto-discovery support and switch discovery event for the equipment at the conference venue.

Incorrect Answers

A:

This outcome would be relevant to “Select a FortiSwitch profile with a managed admin password” at the conference venue, not the task “Use a supported auto-discovery FortiSwitch port”; the other task is to give authorized operators controlled switch access without depending on an empty local password. The action “Use a supported auto-discovery FortiSwitch port” targets a different result: discovery-capable ports advertise and detect controller connectivity without preprogramming the full local switch; the proposed alternative would instead be checked by verify the applied profile and successful login using the assigned administrator credentials.

B:

That behavior applies when engineers “Authorize a discovered FortiSwitch on FortiGate”; the different operation “Use a supported auto-discovery FortiSwitch port” is intended to allow an unconfigured switch to find its FortiLink controller during installation. That different feature is verified by check the managed-switch inventory for an authorized state and configuration synchronization; for “Use a supported auto-discovery FortiSwitch port” on two distribution switches, the relevant evidence is to check the port's model-dependent auto-discovery support and switch discovery event.

C:

That behavior applies when engineers “Apply an administrative access profile”; the different operation “Use a supported auto-discovery FortiSwitch port” is intended to allow an unconfigured switch to find its FortiLink controller during installation. That different feature is verified by test which GUI menus and CLI commands are available to the assigned administrator; for “Use a supported auto-discovery FortiSwitch port” on two distribution switches, the relevant evidence is to check the port's model-dependent auto-discovery support and switch discovery event.

Question 260

At the campus, a dashboard shows ordinary link-up state, but the team also needs proof for “Use a supported auto-discovery FortiSwitch port.” Which targeted check should be used?

  1. Inspect the switch-controller managed-switch list before editing the target unit
  2. Confirm the intended serial number is no longer authorized and review the deauthorization policy
  3. Check the port's model-dependent auto-discovery support and switch discovery event
  4. Inspect the interface's FortiLink dedication and switch discovery on the connected port

Explanation

Correct Answer

C:

This is the precise control because discovery-capable ports advertise and detect controller connectivity without preprogramming the full local switch. Directly measuring that result demonstrates whether the step to allow an unconfigured switch to find its FortiLink controller during installation succeeded on a staging FortiSwitch.

Incorrect Answers

A:

This check is suited to “Use the FortiGate switch-controller GUI” when trying to perform routine managed-switch edits through the centralized user interface, not to verify “Use a supported auto-discovery FortiSwitch port” at the campus. Checking “Use a supported auto-discovery FortiSwitch port” at the campus requires evidence of its own mechanism: discovery-capable ports advertise and detect controller connectivity without preprogramming the full local switch; that is not the outcome measured by “Use the FortiGate switch-controller GUI”.

B:

This check is suited to “Deauthorize a retired managed switch deliberately” when trying to remove an old device from centralized switch management without accidentally changing a replacement unit, not to verify “Use a supported auto-discovery FortiSwitch port” at the campus. Checking “Use a supported auto-discovery FortiSwitch port” at the campus requires evidence of its own mechanism: discovery-capable ports advertise and detect controller connectivity without preprogramming the full local switch; that is not the outcome measured by “Deauthorize a retired managed switch deliberately”.

D:

The proposed check concerns “Mark a FortiGate interface as dedicated to FortiSwitch” rather than “Use a supported auto-discovery FortiSwitch port”: FortiLink enablement distinguishes the switch-controller link from an ordinary production interface. For “Use a supported auto-discovery FortiSwitch port” on a staging FortiSwitch, a better test would be to check the port's model-dependent auto-discovery support and switch discovery event, which targets allow an unconfigured switch to find its FortiLink controller during installation rather than the alternative diagnostic “Mark a FortiGate interface as dedicated to FortiSwitch”.

Fortinet NSE 5 - FortiSwitch 7.6 Administrator (NSE5_FSW_AD-7.6) Practice Tests