You have an Azure subscription. You create an Azure web app named Contoso1812 that uses an S1 App service plan. URL. Which two actions should you perform? Each correct answer presents part of the…

Question

Options

• ATurn on the system-assigned managed identity for Contoso1812.
• BAdd a hostname to Contoso1812.
• CScale out the App Service plan of Contoso1812.
• DAdd a deployment slot to Contoso1812.
• EScale up the App Service plan of Contoso1812.
• FUpload a PFX file to Contoso1812.

• A
  2% (1)
• B
  80% (37)
• C
  4% (2)
• D
  2% (1)
• E
  11% (5)

Explanation

Explanation

To configure a custom domain with HTTPS for a web app (which is the implied goal based on the context of a custom URL and secure connection), you must first add a hostname (Option B) to bind the custom domain to your web app, and then upload a PFX certificate file (Option F) to enable SSL/TLS encryption for that custom domain. These two steps work together: the hostname registers the custom domain, and the PFX file provides the certificate needed to secure it.

Why the distractors are wrong:

• A (Managed Identity): This grants the app access to Azure resources (like Key Vault), not required for custom domains.
• C (Scale Out): Adds more instances for load balancing - unrelated to custom domain/SSL setup.
• D (Deployment Slot): Used for staging/blue-green deployments, not domain configuration.
• E (Scale Up): Moves to a higher pricing tier - note that S1 already supports custom domains and SSL, so this isn't needed.

Memory Tip

Think "Name it, then Secure it" - you must first Bind the hostname (name it), then upload the File (PFX = certificate) to secure it. Custom domain = hostname + certificate, every time.

No community discussion yet for this question.