A security auditor is reviewing a certificate and notices that the 'Subject' field contains a common name that does not match the website's domain name. The certificate is otherwise valid and chains to a trusted root. What is the most likely outcome when a user visits the website?

The browser will reject the certificate because the hostname does not match the certificate's subject or SAN.

The browser will accept the certificate because the chain is trusted.

The browser will accept the certificate but display a warning.

The browser will ignore the subject field and use the issuer field for validation.

An organization wants to deploy S/MIME for email signing. Employees will use certificates issued by the organization's internal CA. What must be configured on each employee's email client to allow recipients to verify signed emails?

The email client must be configured to use the same email server for sending and receiving.

The employee's private key must be shared with the email client.

The employee's certificate must be installed on the email server.

The recipient must have the organization's root CA certificate in their trust store.

A law firm needs to send a settlement agreement to opposing counsel as a PDF attachment. The firm must ensure the recipient can verify that the document was not altered after signing and that it genuinely came from the assigned partner. The recipient does not have a pre-shared key with the firm. What should the firm do?

Send the PDF over a TLS-encrypted email connection.

Attach a digital signature created with the partner's private key over a hash of the PDF.

Include a scanned image of the partner's handwritten signature in the PDF.

Encrypt the PDF with the recipient's public key and email it.

Which key is used to create a digital signature?

A session key generated for each message

What is the correct order of certificates in a chain of trust from the end-entity certificate to the root?

Intermediate CA → End-entity → Root CA

Root CA → Intermediate CA → End-entity

Root CA → End-entity → Intermediate CA

End-entity → Intermediate CA → Root CA

EC-CouncilCertified Encryption Specialist

Domain 4Objective 1

Digital Signatures and X.509 Certificates ECES Practice Questions (Page 3)

Part of the Applications of Cryptography domain, which makes up ~25% of our current practice bank. EC-Council does not publish an official question count, but from its 120-minute exam (~50–80 total, ~13–20 in this domain), expect 3–5 from this objective — we provide 52 practice questions to prepare you well beyond it. (estimate)

52questions here

11free pages

8concepts

Questions 11–15

11expert · hard
A security auditor is reviewing a certificate and notices that the 'Subject' field contains a common name that does not match the website's domain name. The certificate is otherwise valid and chains to a trusted root. What is the most likely outcome when a user visits the website?
Select an answer first
12application · medium
An organization wants to deploy S/MIME for email signing. Employees will use certificates issued by the organization's internal CA. What must be configured on each employee's email client to allow recipients to verify signed emails?
Select an answer first
13application · medium
A law firm needs to send a settlement agreement to opposing counsel as a PDF attachment. The firm must ensure the recipient can verify that the document was not altered after signing and that it genuinely came from the assigned partner. The recipient does not have a pre-shared key with the firm. What should the firm do?
Select an answer first
14foundation · easy
Which key is used to create a digital signature?
Select an answer first
15foundation · easy
What is the correct order of certificates in a chain of trust from the end-entity certificate to the root?
Select an answer first

Finished these 5 questions?

Review the revealed explanations, or continue through the curriculum.

Next 5 questions →Back to ECES

Free Basic Practice is a study aid with revealable answers — not a scored exam. Examers.io is independent and not affiliated with or endorsed by EC-Council. “ECES” is a trademark of its owner, used for identification only.