AZ-204 Develop Azure compute solutions Practice Question

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

• ✗

  A managed identity

  Why it's wrong here

  While managed identities are an excellent solution for Azure resources, such as an App Service, to securely authenticate to other Azure services (e.g., Azure Key Vault, Azure SQL Database) without managing credentials, they are not designed for external users or client applications to authenticate *to* the App Service itself. Managed identities provide an identity for the resource, not an authentication mechanism for external consumers of the resource.

• ✓

  Client ID and Client Secret

  Why this is correct

  A Client ID, also known as the Application ID, uniquely identifies the application within Microsoft Entra ID, while a Client Secret is a confidential credential (like a password or certificate) used by confidential client applications, such as web apps, to prove their identity. These two components are fundamental in OAuth 2.0 flows, enabling the application to securely acquire access tokens and ID tokens from Microsoft Entra ID for user authentication and authorization.

• ✓

  An App Registration in Microsoft Entra ID

  Why this is correct

  An App Registration in Microsoft Entra ID is the foundational configuration that establishes an application's identity within the Microsoft identity platform, allowing it to integrate with Entra ID for authentication and authorization. This registration process assigns a unique Application (client) ID, defines redirect URIs, specifies API permissions, and can generate client secrets or certificates, thereby enabling the web app to authenticate users and access protected resources.

• ✗

  An Azure AD B2C tenant

  Why it's wrong here

  An Azure AD B2C (Business-to-Consumer) tenant is a distinct identity service specifically engineered for managing customer identities for consumer-facing applications, supporting social identity providers and custom user flows. It is not typically used for authenticating internal organizational users within an enterprise environment, which is the domain of a standard Microsoft Entra ID tenant for employee and partner identities.

• ✗

  Azure Front Door

  Why it's wrong here

  Azure Front Door is a global, scalable entry-point that leverages Microsoft's global edge network to provide fast, secure, and highly available web applications through capabilities like global load balancing, dynamic site acceleration, and Web Application Firewall (WAF). It operates at the network and application layer (Layer 7) to route traffic and enhance performance, but it does not provide identity management or authentication services for users or applications directly.