SY0-301 · Question #810
To ensure compatibility with their flagship product, the security engineer is tasked to recommend an encryption cipher that will be compatible with the majority of third party software and hardware ve
The correct answer is D. AES. AES (Advanced Encryption Standard) is the NIST-standardized symmetric encryption cipher with the broadest adoption across software libraries, hardware accelerators, and vendor implementations worldwide.
Question
To ensure compatibility with their flagship product, the security engineer is tasked to recommend an encryption cipher that will be compatible with the majority of third party software and hardware vendors. Which of the following should be recommended?
Options
- ASHA
- BMD5
- CBlowfish
- DAES
How the community answered
(33 responses)- B3% (1)
- C6% (2)
- D91% (30)
Why each option
AES (Advanced Encryption Standard) is the NIST-standardized symmetric encryption cipher with the broadest adoption across software libraries, hardware accelerators, and vendor implementations worldwide.
SHA (Secure Hash Algorithm) is a cryptographic hash function used for integrity verification and digital signatures, not for encrypting data.
MD5 is a hashing algorithm, not an encryption cipher, and it is cryptographically broken and unsuitable for security use.
Blowfish is a valid symmetric cipher but it has much narrower vendor support compared to AES and is not a recognized government or industry standard for general use.
AES was standardized by NIST (FIPS 197) and is mandated or preferred in a vast number of government, enterprise, and commercial security specifications globally. Its widespread hardware support - including dedicated AES-NI CPU instructions - means virtually all modern third-party software and hardware implement it. Choosing AES maximizes interoperability while still providing strong, vetted encryption security.
Concept tested: AES as the universally compatible encryption standard
Source: https://csrc.nist.gov/pubs/fips/197/final
Topics
Community Discussion
No community discussion yet for this question.