Practice Exams:

Palo Alto Networks NetSec-Analyst Dumps

EXAM: Palo Alto Networks Certified Network Security Analyst
Verified By Experts
Premium Bundle
$49.99

NetSec-Analyst Premium ETE File


  • Premium File 118 Questions & Answers
Whats Included:
  • Latest Questions
  • 100% Accurate Answers
  • Fast Exam Updates

Palo Alto Networks NetSec-Analyst Practice Test 47

Question 460

A university pilots encrypted traffic inspection but managed laptops distrust its inspection issuer. Suppose the team follows this shortcut instead: Enable forward proxy without deploying trust and assume clients will never show certificate warnings. What is the most likely direct security or operational consequence?

  1. Partner traffic receives unintended translation and the required site-to-site path breaks
  2. New connections fail intermittently even when firewall CPU and ISP links are healthy
  3. The remote VPN peer sees unexpected addresses and rejects or misroutes return traffic
  4. Users encounter trust failures or administrators introduce broad unsafe exclusions

Answer & Explanations

Correct answer: D

A.

This failure concerns another scenario: A payment provider must preserve original branch IPs across a VPN but internet source NAT matches first. In the stated case: A university pilots encrypted traffic inspection but managed laptops distrust its inspection issuer. The relevant consequence is: Users encounter trust failures or administrators introduce broad unsafe exclusions. The control that prevents it is: Create an SSL Forward Proxy decryption policy for consented user browsing and use an appropriate trusted forward-trust certificate.

B.

This failure concerns another scenario: A university's exam day creates far more concurrent SaaS sessions than its NAT pool supports. In the stated case: A university pilots encrypted traffic inspection but managed laptops distrust its inspection issuer. The relevant consequence is: Users encounter trust failures or administrators introduce broad unsafe exclusions. The control that prevents it is: Create an SSL Forward Proxy decryption policy for consented user browsing and use an appropriate trusted forward-trust certificate.

C.

This failure concerns another scenario: A factory VPN partner requires unchanged OT subnet addresses. In the stated case: A university pilots encrypted traffic inspection but managed laptops distrust its inspection issuer. The relevant consequence is: Users encounter trust failures or administrators introduce broad unsafe exclusions. The control that prevents it is: Create an SSL Forward Proxy decryption policy for consented user browsing and use an appropriate trusted forward-trust certificate.

D.

Users encounter trust failures or administrators introduce broad unsafe exclusions. This is the risk in the stated situation: A university pilots encrypted traffic inspection but managed laptops distrust its inspection issuer. The risky shortcut is: Enable forward proxy without deploying trust and assume clients will never show certificate warnings. Prevent it by: Create an SSL Forward Proxy decryption policy for consented user browsing and use an appropriate trusted forward-trust certificate.

Question 461

A retailer publishes an internal checkout service and needs to inspect inbound encrypted exploit attempts. Which Palo Alto Networks security control or scoped configuration best addresses the situation?

  1. Use supported SSL Inbound Inspection with the managed server certificate and private key for specifically owned TLS services
  2. Create a source NAT rule scoped to intended internal source zone/address and external egress so outbound sessions use approved translated addresses
  3. Configure a destination NAT rule matching the exposed address and port and translating only the approved backend service
  4. Place specific NAT exceptions before general source NAT and verify first matching NAT rule application

Answer & Explanations

Correct answer: A

A.

Use supported SSL Inbound Inspection with the managed server certificate and private key for specifically owned TLS services. The technical reason is: Inbound inspection observes TLS to owned servers with appropriate certificate material while forward proxy impersonates external site certificates. The stated condition is: A retailer publishes an internal checkout service and needs to inspect inbound encrypted exploit attempts. Confirm the result by: Send a test request through the public service and verify decrypted threat inspection with matching certificate identity.

B.

This action is appropriate in a different case: A branch's private clients must reach a public SaaS endpoint through an approved internet-facing address. There, the reason is: Source NAT translates source identity after session setup while Security policy matches original source and destination criteria at relevant stages. The current case is: A retailer publishes an internal checkout service and needs to inspect inbound encrypted exploit attempts. The appropriate response is: Use supported SSL Inbound Inspection with the managed server certificate and private key for specifically owned TLS services.

C.

This action is appropriate in a different case: A clinic exposes a tightly scoped patient scheduling portal through one public IP address. There, the reason is: Destination NAT changes the destination of matching traffic, but routing and Security policy must still permit the resulting service path. The current case is: A retailer publishes an internal checkout service and needs to inspect inbound encrypted exploit attempts. The appropriate response is: Use supported SSL Inbound Inspection with the managed server certificate and private key for specifically owned TLS services.

D.

This action is appropriate in a different case: A payment provider must preserve original branch IPs across a VPN but internet source NAT matches first. There, the reason is: NAT rules are evaluated according to their configured order, so a broad translation can capture traffic intended for a later exception. The current case is: A retailer publishes an internal checkout service and needs to inspect inbound encrypted exploit attempts. The appropriate response is: Use supported SSL Inbound Inspection with the managed server certificate and private key for specifically owned TLS services.

Question 462

A retailer publishes an internal checkout service and needs to inspect inbound encrypted exploit attempts. A network security analyst recommends: Use supported SSL Inbound Inspection with the managed server certificate and private key for specifically owned TLS services. Which technical process explanation best justifies that recommendation?

  1. NAT rules are evaluated according to their configured order, so a broad translation can capture traffic intended for a later exception
  2. Inbound inspection observes TLS to owned servers with appropriate certificate material while forward proxy impersonates external site certificates
  3. DIPP shares external addresses using translated ports, and high session counts can exhaust available translation mappings
  4. A no-NAT exception preserves original internal addressing where the remote peer expects to route the native source

Answer & Explanations

Correct answer: B

A.

This principle explains a different technical intervention: Place specific NAT exceptions before general source NAT and verify first matching NAT rule application. It applies to: A payment provider must preserve original branch IPs across a VPN but internet source NAT matches first. The actual case is: A retailer publishes an internal checkout service and needs to inspect inbound encrypted exploit attempts. The mechanism relevant here is: Inbound inspection observes TLS to owned servers with appropriate certificate material while forward proxy impersonates external site certificates.

B.

Inbound inspection observes TLS to owned servers with appropriate certificate material while forward proxy impersonates external site certificates. That mechanism explains the decision: Use supported SSL Inbound Inspection with the managed server certificate and private key for specifically owned TLS services. In the reported situation: A retailer publishes an internal checkout service and needs to inspect inbound encrypted exploit attempts. Confirmation requires: Send a test request through the public service and verify decrypted threat inspection with matching certificate identity.

C.

This principle explains a different technical intervention: Select dynamic IP-and-port NAT with sufficient address and port capacity for legitimate concurrent egress sessions. It applies to: A university's exam day creates far more concurrent SaaS sessions than its NAT pool supports. The actual case is: A retailer publishes an internal checkout service and needs to inspect inbound encrypted exploit attempts. The mechanism relevant here is: Inbound inspection observes TLS to owned servers with appropriate certificate material while forward proxy impersonates external site certificates.

D.

This principle explains a different technical intervention: Create an explicit no-NAT matching rule for protected VPN traffic before wider outbound translation rules. It applies to: A factory VPN partner requires unchanged OT subnet addresses. The actual case is: A retailer publishes an internal checkout service and needs to inspect inbound encrypted exploit attempts. The mechanism relevant here is: Inbound inspection observes TLS to owned servers with appropriate certificate material while forward proxy impersonates external site certificates.

Question 463

A retailer publishes an internal checkout service and needs to inspect inbound encrypted exploit attempts. After the targeted configuration or process is implemented, which evidence most directly demonstrates the requested behavior?

  1. Check an authorized tunnel session for preserved original source and correct Security policy logs
  2. Test outbound and specifically approved inbound access while verifying pre- and posttranslation tuples
  3. Send a test request through the public service and verify decrypted threat inspection with matching certificate identity
  4. Run a controlled proprietary flow and inspect its reported application and resulting threat visibility

Answer & Explanations

Correct answer: C

A.

This observation would verify a different remedy: Create an explicit no-NAT matching rule for protected VPN traffic before wider outbound translation rules. That remedy applies to: A factory VPN partner requires unchanged OT subnet addresses. The present condition is: A retailer publishes an internal checkout service and needs to inspect inbound encrypted exploit attempts. To assess it, check: Send a test request through the public service and verify decrypted threat inspection with matching certificate identity.

B.

This observation would verify a different remedy: Distinguish static bidirectional NAT design requirements from source-only or destination-only translations and check exposure explicitly. That remedy applies to: A hosted ERP backend uses a mapped static public address for selected partner integrations. The present condition is: A retailer publishes an internal checkout service and needs to inspect inbound encrypted exploit attempts. To assess it, check: Send a test request through the public service and verify decrypted threat inspection with matching certificate identity.

C.

Send a test request through the public service and verify decrypted threat inspection with matching certificate identity. This check directly tests: Use supported SSL Inbound Inspection with the managed server certificate and private key for specifically owned TLS services. The underlying behavior is: Inbound inspection observes TLS to owned servers with appropriate certificate material while forward proxy impersonates external site certificates. The case is: A retailer publishes an internal checkout service and needs to inspect inbound encrypted exploit attempts.

D.

This observation would verify a different remedy: Use application override only for a documented traffic flow when necessary and confirm associated inspection tradeoffs. That remedy applies to: A factory legacy protocol requires an explicit override after sanctioned analysis finds ordinary classification unreliable. The present condition is: A retailer publishes an internal checkout service and needs to inspect inbound encrypted exploit attempts. To assess it, check: Send a test request through the public service and verify decrypted threat inspection with matching certificate identity.

Question 464

A retailer publishes an internal checkout service and needs to inspect inbound encrypted exploit attempts. Which apparently convenient shortcut would most directly undermine the required control?

  1. Apply an application override broadly to all HTTPS so custom traffic receives a convenient label
  2. Override every connection on a shared TCP port as the trusted custom application
  3. Treat a successful session connection as proof that the existing Anti-Spyware and Vulnerability controls still inspect every payload
  4. Deploy a forward-trust proxy CA as a substitute for the private key required by inbound inspection

Answer & Explanations

Correct answer: D

A.

This proposed shortcut concerns a separate case: A factory legacy protocol requires an explicit override after sanctioned analysis finds ordinary classification unreliable. The risk in this question concerns: A retailer publishes an internal checkout service and needs to inspect inbound encrypted exploit attempts. Here the unsafe shortcut is: Deploy a forward-trust proxy CA as a substitute for the private key required by inbound inspection. Use this response instead: Use supported SSL Inbound Inspection with the managed server certificate and private key for specifically owned TLS services.

B.

This proposed shortcut concerns a separate case: A research lab has several protocols sharing TCP 8443 but only one needs a custom application identity. The risk in this question concerns: A retailer publishes an internal checkout service and needs to inspect inbound encrypted exploit attempts. Here the unsafe shortcut is: Deploy a forward-trust proxy CA as a substitute for the private key required by inbound inspection. Use this response instead: Use supported SSL Inbound Inspection with the managed server certificate and private key for specifically owned TLS services.

C.

This proposed shortcut concerns a separate case: A warehouse adds an override to restore a scanner protocol but SOC threat logs drop for that flow. The risk in this question concerns: A retailer publishes an internal checkout service and needs to inspect inbound encrypted exploit attempts. Here the unsafe shortcut is: Deploy a forward-trust proxy CA as a substitute for the private key required by inbound inspection. Use this response instead: Use supported SSL Inbound Inspection with the managed server certificate and private key for specifically owned TLS services.

D.

Deploy a forward-trust proxy CA as a substitute for the private key required by inbound inspection. This shortcut is unsafe for: A retailer publishes an internal checkout service and needs to inspect inbound encrypted exploit attempts. The resulting failure can be: Inbound sessions are not inspected as intended or TLS authentication fails. The safer response is: Use supported SSL Inbound Inspection with the managed server certificate and private key for specifically owned TLS services.

Question 465

A retailer publishes an internal checkout service and needs to inspect inbound encrypted exploit attempts. Suppose the team follows this shortcut instead: Deploy a forward-trust proxy CA as a substitute for the private key required by inbound inspection. What is the most likely direct security or operational consequence?

  1. Inbound sessions are not inspected as intended or TLS authentication fails
  2. Known threat indicators escape previously expected inspection under the override
  3. Unrelated traffic exits an unintended ISP or bypasses required inspection
  4. Connections remain directed at an unavailable next hop after an ISP outage

Answer & Explanations

Correct answer: A

A.

Inbound sessions are not inspected as intended or TLS authentication fails. This is the risk in the stated situation: A retailer publishes an internal checkout service and needs to inspect inbound encrypted exploit attempts. The risky shortcut is: Deploy a forward-trust proxy CA as a substitute for the private key required by inbound inspection. Prevent it by: Use supported SSL Inbound Inspection with the managed server certificate and private key for specifically owned TLS services.

B.

This failure concerns another scenario: A warehouse adds an override to restore a scanner protocol but SOC threat logs drop for that flow. In the stated case: A retailer publishes an internal checkout service and needs to inspect inbound encrypted exploit attempts. The relevant consequence is: Inbound sessions are not inspected as intended or TLS authentication fails. The control that prevents it is: Use supported SSL Inbound Inspection with the managed server certificate and private key for specifically owned TLS services.

C.

This failure concerns another scenario: A finance app must use a dedicated managed ISP while ordinary browsing stays on the primary uplink. In the stated case: A retailer publishes an internal checkout service and needs to inspect inbound encrypted exploit attempts. The relevant consequence is: Inbound sessions are not inspected as intended or TLS authentication fails. The control that prevents it is: Use supported SSL Inbound Inspection with the managed server certificate and private key for specifically owned TLS services.

D.

This failure concerns another scenario: A retail branch's preferred private MPLS path fails and accounting sessions need allowed internet backup. In the stated case: A retailer publishes an internal checkout service and needs to inspect inbound encrypted exploit attempts. The relevant consequence is: Inbound sessions are not inspected as intended or TLS authentication fails. The control that prevents it is: Use supported SSL Inbound Inspection with the managed server certificate and private key for specifically owned TLS services.

Question 466

A software company protects its own HTTPS API behind a firewall using authorized key material. Which Palo Alto Networks security control or scoped configuration best addresses the situation?

  1. Distinguish static bidirectional NAT design requirements from source-only or destination-only translations and check exposure explicitly
  2. Use supported SSL Inbound Inspection with the managed server certificate and private key for specifically owned TLS services
  3. Use application override only for a documented traffic flow when necessary and confirm associated inspection tradeoffs
  4. Evaluate a supported custom application signature before broad application overrides when traffic has a stable matchable identifier

Answer & Explanations

Correct answer: B

A.

This action is appropriate in a different case: A hosted ERP backend uses a mapped static public address for selected partner integrations. There, the reason is: A static mapping can support predictable reverse translation, but inbound reachability still depends on separate policy and routing. The current case is: A software company protects its own HTTPS API behind a firewall using authorized key material. The appropriate response is: Use supported SSL Inbound Inspection with the managed server certificate and private key for specifically owned TLS services.

B.

Use supported SSL Inbound Inspection with the managed server certificate and private key for specifically owned TLS services. The technical reason is: Inbound inspection observes TLS to owned servers with appropriate certificate material while forward proxy impersonates external site certificates. The stated condition is: A software company protects its own HTTPS API behind a firewall using authorized key material. Confirm the result by: Send a test request through the public service and verify decrypted threat inspection with matching certificate identity.

C.

This action is appropriate in a different case: A factory legacy protocol requires an explicit override after sanctioned analysis finds ordinary classification unreliable. There, the reason is: An application override can bypass normal signature-based App-ID classification for matching sessions, limiting application-layer inspection features. The current case is: A software company protects its own HTTPS API behind a firewall using authorized key material. The appropriate response is: Use supported SSL Inbound Inspection with the managed server certificate and private key for specifically owned TLS services.

D.

This action is appropriate in a different case: A research lab has several protocols sharing TCP 8443 but only one needs a custom application identity. There, the reason is: A custom signature can retain more useful application classification while an override forces a configured application label without ordinary inspection. The current case is: A software company protects its own HTTPS API behind a firewall using authorized key material. The appropriate response is: Use supported SSL Inbound Inspection with the managed server certificate and private key for specifically owned TLS services.

Question 467

A software company protects its own HTTPS API behind a firewall using authorized key material. A network security analyst recommends: Use supported SSL Inbound Inspection with the managed server certificate and private key for specifically owned TLS services. Which technical process explanation best justifies that recommendation?

  1. A custom signature can retain more useful application classification while an override forces a configured application label without ordinary inspection
  2. Override policy can change how the firewall processes a matching flow, so previously expected content inspection or application dependency assumptions may no longer apply
  3. Inbound inspection observes TLS to owned servers with appropriate certificate material while forward proxy impersonates external site certificates
  4. PBF can select a specific forwarding path for matched sessions rather than relying entirely on the standard virtual router routing table

Answer & Explanations

Correct answer: C

A.

This principle explains a different technical intervention: Evaluate a supported custom application signature before broad application overrides when traffic has a stable matchable identifier. It applies to: A research lab has several protocols sharing TCP 8443 but only one needs a custom application identity. The actual case is: A software company protects its own HTTPS API behind a firewall using authorized key material. The mechanism relevant here is: Inbound inspection observes TLS to owned servers with appropriate certificate material while forward proxy impersonates external site certificates.

B.

This principle explains a different technical intervention: Audit effective security profiles and permitted ports for any exception that forces an application identification. It applies to: A warehouse adds an override to restore a scanner protocol but SOC threat logs drop for that flow. The actual case is: A software company protects its own HTTPS API behind a firewall using authorized key material. The mechanism relevant here is: Inbound inspection observes TLS to owned servers with appropriate certificate material while forward proxy impersonates external site certificates.

C.

Inbound inspection observes TLS to owned servers with appropriate certificate material while forward proxy impersonates external site certificates. That mechanism explains the decision: Use supported SSL Inbound Inspection with the managed server certificate and private key for specifically owned TLS services. In the reported situation: A software company protects its own HTTPS API behind a firewall using authorized key material. Confirmation requires: Send a test request through the public service and verify decrypted threat inspection with matching certificate identity.

D.

This principle explains a different technical intervention: Create a Policy-Based Forwarding rule matching approved source and destination constraints with a reachable next hop. It applies to: A finance app must use a dedicated managed ISP while ordinary browsing stays on the primary uplink. The actual case is: A software company protects its own HTTPS API behind a firewall using authorized key material. The mechanism relevant here is: Inbound inspection observes TLS to owned servers with appropriate certificate material while forward proxy impersonates external site certificates.

Question 468

A software company protects its own HTTPS API behind a firewall using authorized key material. After the targeted configuration or process is implemented, which evidence most directly demonstrates the requested behavior?

  1. Generate two test applications and confirm only the designated flow takes the special egress next hop
  2. Simulate a safe next-hop outage and verify monitor state plus new-session route restoration
  3. Inspect a pilot session's matching PBF, security rule and translated address under failover
  4. Send a test request through the public service and verify decrypted threat inspection with matching certificate identity

Answer & Explanations

Correct answer: D

A.

This observation would verify a different remedy: Create a Policy-Based Forwarding rule matching approved source and destination constraints with a reachable next hop. That remedy applies to: A finance app must use a dedicated managed ISP while ordinary browsing stays on the primary uplink. The present condition is: A software company protects its own HTTPS API behind a firewall using authorized key material. To assess it, check: Send a test request through the public service and verify decrypted threat inspection with matching certificate identity.

B.

This observation would verify a different remedy: Enable PBF path monitoring with a tested failure action so critical traffic can recover through approved routing. That remedy applies to: A retail branch's preferred private MPLS path fails and accounting sessions need allowed internet backup. The present condition is: A software company protects its own HTTPS API behind a firewall using authorized key material. To assess it, check: Send a test request through the public service and verify decrypted threat inspection with matching certificate identity.

C.

This observation would verify a different remedy: Validate PBF path selection alongside separate Security and NAT rules for the actual egress after steering. That remedy applies to: A university shifts a science portal to a secondary ISP but forgets source NAT for that interface. The present condition is: A software company protects its own HTTPS API behind a firewall using authorized key material. To assess it, check: Send a test request through the public service and verify decrypted threat inspection with matching certificate identity.

D.

Send a test request through the public service and verify decrypted threat inspection with matching certificate identity. This check directly tests: Use supported SSL Inbound Inspection with the managed server certificate and private key for specifically owned TLS services. The underlying behavior is: Inbound inspection observes TLS to owned servers with appropriate certificate material while forward proxy impersonates external site certificates. The case is: A software company protects its own HTTPS API behind a firewall using authorized key material.

Question 469

A software company protects its own HTTPS API behind a firewall using authorized key material. Which apparently convenient shortcut would most directly undermine the required control?

  1. Deploy a forward-trust proxy CA as a substitute for the private key required by inbound inspection
  2. Add a PBF rule and assume it automatically permits the app and supplies a suitable public NAT address
  3. Assign every application to the highest-bandwidth circuit without measuring latency or loss
  4. Set every SLA loss threshold to zero percent and treat any natural packet drop as a total circuit failure

Answer & Explanations

Correct answer: A

A.

Deploy a forward-trust proxy CA as a substitute for the private key required by inbound inspection. This shortcut is unsafe for: A software company protects its own HTTPS API behind a firewall using authorized key material. The resulting failure can be: Inbound sessions are not inspected as intended or TLS authentication fails. The safer response is: Use supported SSL Inbound Inspection with the managed server certificate and private key for specifically owned TLS services.

B.

This proposed shortcut concerns a separate case: A university shifts a science portal to a secondary ISP but forgets source NAT for that interface. The risk in this question concerns: A software company protects its own HTTPS API behind a firewall using authorized key material. Here the unsafe shortcut is: Deploy a forward-trust proxy CA as a substitute for the private key required by inbound inspection. Use this response instead: Use supported SSL Inbound Inspection with the managed server certificate and private key for specifically owned TLS services.

C.

This proposed shortcut concerns a separate case: A video consultation app must prefer low-jitter WAN over a bulky backup provider. The risk in this question concerns: A software company protects its own HTTPS API behind a firewall using authorized key material. Here the unsafe shortcut is: Deploy a forward-trust proxy CA as a substitute for the private key required by inbound inspection. Use this response instead: Use supported SSL Inbound Inspection with the managed server certificate and private key for specifically owned TLS services.

D.

This proposed shortcut concerns a separate case: A financial services branch sees SD-WAN flapping under minor daily jitter. The risk in this question concerns: A software company protects its own HTTPS API behind a firewall using authorized key material. Here the unsafe shortcut is: Deploy a forward-trust proxy CA as a substitute for the private key required by inbound inspection. Use this response instead: Use supported SSL Inbound Inspection with the managed server certificate and private key for specifically owned TLS services.

Question 470

A software company protects its own HTTPS API behind a firewall using authorized key material. Suppose the team follows this shortcut instead: Deploy a forward-trust proxy CA as a substitute for the private key required by inbound inspection. What is the most likely direct security or operational consequence?

  1. Frequent flaps disrupt users during ordinary transient network variation
  2. Inbound sessions are not inspected as intended or TLS authentication fails
  3. Clinical or financial transactions reset despite the existence of a healthy backup circuit
  4. Restricted transport carries unapproved traffic and critical bandwidth is consumed

Answer & Explanations

Correct answer: B

A.

This failure concerns another scenario: A financial services branch sees SD-WAN flapping under minor daily jitter. In the stated case: A software company protects its own HTTPS API behind a firewall using authorized key material. The relevant consequence is: Inbound sessions are not inspected as intended or TLS authentication fails. The control that prevents it is: Use supported SSL Inbound Inspection with the managed server certificate and private key for specifically owned TLS services.

B.

Inbound sessions are not inspected as intended or TLS authentication fails. This is the risk in the stated situation: A software company protects its own HTTPS API behind a firewall using authorized key material. The risky shortcut is: Deploy a forward-trust proxy CA as a substitute for the private key required by inbound inspection. Prevent it by: Use supported SSL Inbound Inspection with the managed server certificate and private key for specifically owned TLS services.

C.

This failure concerns another scenario: A regional bank needs proof its payroll service survives a short ISP outage within tolerance. In the stated case: A software company protects its own HTTPS API behind a firewall using authorized key material. The relevant consequence is: Inbound sessions are not inspected as intended or TLS authentication fails. The control that prevents it is: Use supported SSL Inbound Inspection with the managed server certificate and private key for specifically owned TLS services.

D.

This failure concerns another scenario: A hospital must isolate guest browsing from its private clinical WAN while both use SD-WAN. In the stated case: A software company protects its own HTTPS API behind a firewall using authorized key material. The relevant consequence is: Inbound sessions are not inspected as intended or TLS authentication fails. The control that prevents it is: Use supported SSL Inbound Inspection with the managed server certificate and private key for specifically owned TLS services.

Palo Alto Networks Certified Network Security Analyst (NetSec-Analyst) Practice Tests