210-250 · Question #190
To communicate that a document is using a digital signature, which one of the following is the next step in the process after a hash of the document is calculated by the sender?
The correct answer is C. The hash is encrypted using the private key of the sender. After hashing a document, the sender creates a digital signature by encrypting that hash with their own private key, cryptographically binding the signature to their identity.
Question
To communicate that a document is using a digital signature, which one of the following is the next step in the process after a hash of the document is calculated by the sender?
Options
- AThe hash is appended to the end of the document.
- BThe hash is stored by the sender.
- CThe hash is encrypted using the private key of the sender.
- DThe hash is encrypted using a symmetric encryption algorithm.
- EThe hash is signed using the public key of the receiver.
How the community answered
(48 responses)- B4% (2)
- C92% (44)
- D2% (1)
- E2% (1)
Why each option
After hashing a document, the sender creates a digital signature by encrypting that hash with their own private key, cryptographically binding the signature to their identity.
Appending an unencrypted hash provides no cryptographic protection - an attacker could modify the document and recalculate a matching hash without detection.
Storing the hash locally does nothing to convey a verifiable signature to the receiving party and provides no authentication or integrity guarantee for the receiver.
The sender encrypts the computed hash using their own private key, which is the operation that produces the digital signature. Because only the sender possesses the corresponding private key, this step ensures non-repudiation and authenticity. Any recipient can then decrypt the signature using the sender's public key and compare the resulting hash to a freshly computed one, verifying integrity.
Symmetric encryption of the hash does not produce a valid digital signature because any party sharing the symmetric key could have created it, eliminating the non-repudiation property.
The receiver's public key is used to encrypt data for confidentiality, not for creating a digital signature - signing requires the sender's private key, not the receiver's public key.
Concept tested: Digital signature creation process using sender private key
Source: https://csrc.nist.gov/publications/detail/fips/186/5/final
Topics
Community Discussion
No community discussion yet for this question.