Azure MFA for Credential Encryption During Deployment
Note: The question is included in a number of questions that depicts the identical set-up. However, every question has a distinctive result. Establish if the solution satisfies the requirements. You have been informed by your superiors of the company's intentions to automate server deployment to Azure. There is, however, some concern that administrative credentials could be uncovered during this process. You are required to make sure that during the deployment, the administrative credentials are encrypted using a suitable Azure solution. Solution: You recommend the use of Azure Multi-Factor Authentication (MFA). Does the solution meet the goal?
Community Insight
The question tests the distinction between identity governance and data security; the trap is assuming any 'security' feature like MFA protects stored secrets, whereas Key Vault is required for encryption.
This question evaluates whether Azure Multi-Factor Authentication (MFA) can encrypt administrative credentials during automated server deployment. The correct answer is B, as MFA is an authentication control, not a data protection service.
Many learners choose A because they associate 'security' with MFA without reading the specific requirement for 'encryption' of credentials. They confuse access control with data confidentiality.
Community Discussion (34 comments)
Comments & Corrections
No comments yet — spotted an error or have a note? Share it below.
Expert Analysis
Why the Answer Is Correct
The solution does not meet the goal because Azure Multi-Factor Authentication (MFA) is designed to verify user identity during login, not to store or encrypt secrets. MFA adds a second factor to authentication but provides no mechanism for protecting the confidentiality of administrative credentials themselves during deployment. To encrypt and securely store these credentials, you must use a dedicated secrets management service like Azure Key Vault.Why the Other Options Are Wrong
Option A is incorrect because it validates a flawed technical premise. MFA cannot encrypt data; it only challenges the user for additional proof of identity. Using MFA would leave the plaintext credentials exposed in scripts or configuration files, defeating the purpose of encryption.Community Comment Notes
Community consensus strongly supports Option B. Users like jgalanj noted that the keyword 'credentials' points directly to Key Vault. Dennx clarified that "MFA adds an aditional layer to the authentication process, but it doesn't keep your credential safe." Another commenter emphasized that "Key Vault will protect credentials," highlighting the correct architectural component for this scenario.Official Reference
Exam Strategy
When a question asks about securing passwords, keys, or certificates, immediately think of Azure Key Vault. Do not confuse it with Azure Active Directory features like MFA or Conditional Access, which handle who gets in, not what data is protected.
Frequently Asked Questions
Why isn't MFA enough to secure credentials?
MFA verifies identity at login but does not store or encrypt the actual password or key. It prevents unauthorized access but leaves the secret itself unprotected if compromised elsewhere.
What Azure service should I use instead of MFA for secrets?
Use Azure Key Vault. It is a centralized service for managing secrets, keys, and certificates, providing encryption and strict access controls.
Related Analysis
Practice All AZ-900 Questions
Access 90 questions with complete answers and detailed explanations.
View Full AZ-900 Practice Test →