AZ-500 Question #179: Real Exam Question with Answer & Explanation

Question

You have an Azure web app named WebApp1. You upload a certificate to WebApp1. You need to make the certificate accessible to the app code of WebApp1. What should you do?

Options

• AAdd a user-assigned managed identity to WebApp1.
• BAdd an app setting to the WebApp1 configuration.
• CEnable system-assigned managed identity for the WebApp1.
• DConfigure the TLS/SSL binding for WebApp1.

Explanation

Explanation

Adding an app setting named WEBSITE_LOAD_CERTIFICATES to WebApp1's configuration is the required step - specifically, setting its value to the certificate's thumbprint (or * for all certificates) tells the Azure runtime to load the certificate into the Windows Certificate Store, making it accessible to the app's code. Without this setting, even though the certificate is uploaded, the application cannot programmatically access it. Option A (user-assigned managed identity) and Option C (system-assigned managed identity) are used for authenticating to other Azure services, not for exposing certificates to application code. Option D (TLS/SSL binding) is used to associate a certificate with a custom domain for HTTPS traffic, not to expose the certificate's data to your application logic.

🧠 Memory Tip

Think of it this way: uploading the certificate is like putting a key in a locked drawer - you still need to tell the app where the drawer is via the WEBSITE_LOAD_CERTIFICATES app setting. The setting is the "unlock instruction" that bridges the certificate store and your code.

No community discussion yet for this question.