A developer is implementing a verification function for a signed message. The function receives the message, the signature, and the signer's certificate. Which sequence of steps correctly verifies the signature?

Encrypt the message with the certificate's public key and compare it to the signature.

Hash the message, decrypt the signature with the certificate's public key, and compare the two hashes.

Hash the signature and compare it to the message's hash.

Decrypt the message with the certificate's private key and compare it to the signature.

Why is a hash function used in creating a digital signature?

To encrypt the message with a symmetric key

To compress the message so it takes less storage space

To add randomness to the signature for extra security

To reduce the message to a fixed-size digest that is signed

A company's root CA certificate is nearing expiration. The company plans to migrate to a new root CA. To minimize disruption, what is the best practice?

Revoke all existing certificates and reissue them from the new root before the old root expires.

Cross-sign the new root with the old root and the old root with the new root.

Let the root CA expire and issue new certificates from a new root immediately.

Extend the validity of the old root CA certificate by editing its expiration date.

How does TLS/SSL use X.509 certificates to secure web communications?

The server encrypts all data with the client's public key

The server presents a certificate to prove its identity to the client

The client sends its private key to the server for authentication

The certificate contains the server's private key for decryption

A developer is implementing a document-signing feature for a mobile app. The documents can be up to 50 MB. The developer wants to minimize the computational cost of signing while still providing integrity and non-repudiation. What is the most efficient approach?

Append the signer's public key to the document and send both.

Use a symmetric key to encrypt the document and send the key with the document.

Compute a hash of the document and encrypt only the hash with the signer's private key.

Encrypt the entire document with the signer's private key.

EC-CouncilCertified Encryption Specialist

Domain 4Objective 1

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

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 26–30

26expert · medium
A developer is implementing a verification function for a signed message. The function receives the message, the signature, and the signer's certificate. Which sequence of steps correctly verifies the signature?
Select an answer first
27foundation · easy
Why is a hash function used in creating a digital signature?
Select an answer first
28expert · hard
A company's root CA certificate is nearing expiration. The company plans to migrate to a new root CA. To minimize disruption, what is the best practice?
Select an answer first
29foundation · easy
How does TLS/SSL use X.509 certificates to secure web communications?
Select an answer first
30application · medium
A developer is implementing a document-signing feature for a mobile app. The documents can be up to 50 MB. The developer wants to minimize the computational cost of signing while still providing integrity and non-repudiation. What is the most efficient approach?
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.