MENU
You deploy a production Azure Function app that connects to an Azure SQL Database.
The solution must provide the follow ng functionality:
* Prevent secrets from being exposed in source control.
* Support secret rotation without redeploying the function app.
* Avoid downtime during credential updates.
You need to configure secure and maintainable secret management. What should you configure?
Suggested Answer: A
Get Premium AI-200 Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
12 comments · newest first
HO
Honey
22 days ago
B is not secure enough. Local.settings.json can be exposed.
JA
Janine
27 days ago
Agreed! A prevents secrets in source control.
TH
Therese
1 month ago
I think A is the best choice. Key Vault is secure.
AN
Annice
1 month ago
Parameter files in source control? That's a bad idea!
EI
Eileen
1 month ago
Key Vault references are definitely the best for security.
TA
Tandra
2 months ago
Surprised that hard coding is even an option here!
GI
Gilbert
2 months ago
I disagree, environment variables are easier to manage locally.
DO
Dominque
2 months ago
A) Application settings with Key Vault references is the way to go!
EL
Elly
2 months ago
I vaguely recall something about parameter files being a bad practice for secrets, so I would probably rule out option C as well.
NU
Nu
2 months ago
I think we had a practice question about secret rotation, and it emphasized avoiding hard-coded values, which makes me lean away from option D.
AM
Amos
2 months ago
I'm not entirely sure, but I feel like using environment variables in local.settings.json could expose secrets if not handled properly.
TO
Tora
3 months ago
I remember we discussed using Azure Key Vault for managing secrets, so I think option A might be the right choice.