Prepare and test your skills
Prepare and test your skills
Free sample question, answered and explained below. The Professional Cloud Architect practice bank has 2,335 more like it. Try 10 free: instant score, no account.
An enterprise is planning to migrate several core business applications to Google Cloud while maintaining its existing Microsoft Entra ID (formerly Azure Active Directory) as the authoritative identity provider (IdP).
The organization wants to implement automated user provisioning and Single Sign-On (SSO) with Cloud Identity to support centralized access control. The architecture must satisfy the following requirements:
Which identity federation strategy should the cloud architect implement?
Cloud Identity federation establishes a trust relationship between Google Cloud and an external Identity Provider (IdP) such as Microsoft Entra ID. By pairing automated directory synchronization with SAML 2.0 Single Sign-On (SSO), user identities and credentials remain centralized in Entra ID while granting access to Google Cloud resources.
user@example.com) on both the Google Cloud sign-in prompt and the Entra ID redirect screen.Mapping Entra ID UPNs configured with custom domain suffixes to Cloud Identity email addresses aligns the authentication identifier with the notification transport address, eliminating user confusion during identity-provider redirects.
This approach relies on individual end users registering self-managed consumer Google accounts using their existing business email addresses, after which administrators manually assign IAM roles to these accounts.
A small team needed temporary, ad-hoc access to a single external sandbox project without integrating with existing enterprise directories.
onmicrosoft.com domain in Cloud Identity and map Entra ID ObjectIds to Cloud Identity user identifiersThis approach attempts to use Microsoft's default initial domain (tenant.onmicrosoft.com) and internal directory ObjectId GUIDs to construct user accounts in Cloud Identity.
onmicrosoft.com domain is owned and operated by Microsoft, meaning organizations cannot verify ownership in Cloud Identity.12345678-abcd-1234-abcd-1234567890ab). Cloud Identity requires human-readable email format identifiers for IAM role assignments and communication.You were implementing an internal programmatic API token mapping where human interaction and email notifications were not required.
This option attempts to provision Cloud Identity users using Microsoft Entra ID MOERAs (Microsoft Online Email Routing Addresses), which are default routing addresses formatted as user@tenant.onmicrosoft.com.
onmicrosoft.com suffix. Because the enterprise does not own this domain, it cannot be validated or registered within Cloud Identity.Microsoft Entra ID allowed delegating authoritative DNS ownership of onmicrosoft.com subdomains to tenant administrators, which is not supported.
Answer them yourself and get your score the moment you finish. No account needed.
Full access includes
Keep the momentum going with these hand-picked practice scenarios
Last updated Validated