You created an Azure Web App named Contoso1812 on an S1 App Service plan and will add a CNAME record for a custom public hostname. To enable HTTPS access through that hostname, which two actions should you perform?

To enable HTTPS for a custom domain on an Azure Web App, you must first associate the custom domain with the web app. This is done by adding a hostname to Contoso1812, which tells Azure that this web app should respond to requests for that specific domain. Then, to secure the connection with HTTPS, you need to upload a PFX file containing the SSL certificate and its private key. This certificate encrypts the communication between the client and the web app. Turning on a system-assigned managed identity is for Azure resource authentication, not custom domain HTTPS. Scaling out or up the App Service plan affects performance and capacity, not custom domain configuration or HTTPS. Adding a deployment slot is for staging and testing new versions of the application, not for enabling HTTPS on the primary domain.