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?
Click on the arrows to vote for the correct answer
A. B. C. D.B
https://docs.microsoft.com/en-us/azure/app-service/configure-ssl-certificate-in-codeWhen you upload a certificate to an Azure Web App, it is stored in a secure and private location. To make the certificate accessible to the app code, you need to configure the TLS/SSL binding for the WebApp1.
The TLS/SSL binding is a secure connection between the client and the server. It requires a certificate to authenticate the server and encrypt the data in transit. To configure the TLS/SSL binding for WebApp1, you need to follow these steps:
Go to the Azure portal and navigate to the WebApp1.
In the left-hand menu, select "TLS/SSL settings".
In the "TLS/SSL settings" page, select "Private Key Certificates (.pfx)".
Upload the certificate that you want to use for the TLS/SSL binding.
Once the certificate is uploaded, you need to configure the binding. Select the "HTTPS Only" option to force all traffic to use the secure connection.
Save the changes.
After you have configured the TLS/SSL binding, the certificate will be accessible to the app code of WebApp1. You can use the certificate to secure communication between the app and other services or clients.
Note that the other answer options are not relevant to making the certificate accessible to the app code:
A. Adding a user-assigned managed identity to WebApp1 does not help make the certificate accessible to the app code.
B. Adding an app setting to the WebApp1 configuration does not help make the certificate accessible to the app code.
C. Enabling a system-assigned managed identity for the WebApp1 does not help make the certificate accessible to the app code.