SC-900 Describe the capabilities of Microsoft Entra 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.

• ✗

  Enable Microsoft Entra ID Domain Services

  Why it's wrong here

  Microsoft Entra ID Domain Services provides managed domain services like traditional Active Directory, including features such as Group Policy, LDAP, and Kerberos/NTLM authentication, for cloud-based virtual machines and applications. It is primarily used to lift-and-shift legacy applications requiring domain-joined servers to Azure without deploying domain controllers. However, for providing single sign-on (SSO) to modern SaaS applications directly from Microsoft Entra ID, this service is entirely unnecessary as it doesn't facilitate direct federation or authentication for cloud-native apps.

• ✓

  Add the application from the Microsoft Entra ID Gallery in Enterprise applications

  Why this is correct

  The Microsoft Entra ID Gallery within Enterprise applications offers a vast catalog of pre-integrated software-as-a-service (SaaS) applications, each with pre-configured settings for single sign-on (SSO). Adding an application from this gallery streamlines the setup process, allowing administrators to quickly enable secure access and user provisioning using standards like SAML or OIDC without manual configuration. This approach is ideal for integrating common third-party cloud services, leveraging Microsoft Entra ID as the central identity provider.

• ✗

  Configure Microsoft Entra ID Governance

  Why it's wrong here

  Microsoft Entra ID Governance focuses on managing and monitoring access to resources, ensuring that the right people have the right access for the right reasons. Its capabilities include access reviews, entitlement management, and privileged identity management, which are crucial for maintaining compliance and security posture. While essential for managing access after an application is integrated, it does not facilitate the initial integration or configuration of single sign-on for a new application itself.

• ✗

  Register the application in App registrations

  Why it's wrong here

  App registrations in Microsoft Entra ID are specifically designed for developers to integrate custom-built applications, APIs, or services with the Microsoft identity platform. This process involves defining application properties, permissions, and authentication methods (like redirect URIs) for applications developed in-house or by third parties not listed in the gallery. It is not the appropriate method for integrating pre-built, off-the-shelf SaaS applications that already have established integration patterns with Microsoft Entra ID.

Go deeper

Related to this question