You deployed an Azure App Service web app named App1 and created an Azure Key Vault named Vault1 containing API keys, passwords, certificates, and keys. You must grant App1 access to Vault1, support automatic credential rotation, and avoid storing credentials in code. What should you do?

Assigning a managed identity to App1 is the correct solution because it provides an automatically managed identity in Azure Active Directory for App1. This identity can then be granted permissions to access Vault1 using Azure Role-Based Access Control (RBAC), eliminating the need to store credentials (like connection strings or API keys) in App1's code. Managed identities support automatic credential rotation by Azure, fulfilling that requirement. Enabling App Service Authentication for App1 is for user authentication to the app, not for the app itself to access other Azure resources. Adding a TLS/SSL binding to App1 secures communication to the app, but doesn't grant the app access to Key Vault. Uploading a self-signed client certificate to Vault1 and configuring App1 to use it would involve managing certificates manually and storing certificate details, which goes against avoiding storing credentials in code and automatic rotation.