DVA-C02 · Question #731
A developer must digitally sign a document with AWS KMS so that another application that does not have AWS KMS access can verify the authenticity of the document. Which solution will meet this…
The correct answer is C. Use AWS KMS with asymmetric keys. Sign the document by using the private key. Make the. AWS KMS supports asymmetric key pairs for use cases like digital signing and verification. The private key is used to sign the document within AWS KMS, and the public key can be shared externally with systems that do not have access to AWS KMS for verification. This satisfies…
Question
A developer must digitally sign a document with AWS KMS so that another application that does not have AWS KMS access can verify the authenticity of the document. Which solution will meet this requirement?
Options
- AUse AWS KMS with a symmetric key. Sign the document with AWS KMS. Make the key available
- BUse AWS KMS with a symmetric key to generate an envelope key. Sign the document with AWS
- CUse AWS KMS with asymmetric keys. Sign the document by using the private key. Make the
- DUse AWS KMS with asymmetric keys. Sign the document by using the public key. Make the
How the community answered
(32 responses)- A9% (3)
- B3% (1)
- C84% (27)
- D3% (1)
Explanation
AWS KMS supports asymmetric key pairs for use cases like digital signing and verification. The private key is used to sign the document within AWS KMS, and the public key can be shared externally with systems that do not have access to AWS KMS for verification. This satisfies the requirement of external verification without granting AWS KMS access.
Community Discussion
No community discussion yet for this question.