AZ-305 · Question #3
Case Study 1 - Litware Existing Environment Azure Environment Litware has 10 Azure subscriptions that are linked to the Litware.com tenant and five Azure subscriptions that are linked to the…
The correct answer is Storage account type:: Standard general-purpose v2; Configuration:: Hierarchical namespace. This hotspot question tests knowledge of Azure RBAC custom roles, conditional access policies, and cross-tenant role assignments in an Enterprise Agreement environment with multiple Azure AD tenants.
Question
Exhibits
Answer Area
- Storage account type:Standard general-purpose v2Premium page blobsPremium file sharesStandard general-purpose v2
- Configuration:Hierarchical namespaceNFSv3Large file sharesHierarchical namespace
Explanation
This hotspot question tests knowledge of Azure RBAC custom roles, conditional access policies, and cross-tenant role assignments in an Enterprise Agreement environment with multiple Azure AD tenants.
Approach. Custom Azure RBAC roles like Role1 defined in the litware.com tenant cannot be directly assigned to subscriptions in the dev.litware.com tenant, as RBAC custom roles are scoped to the tenant where they are created. Conditional Access policies requiring hybrid Azure AD-joined device compliance apply only to users accessing the Azure portal for production environments, meaning a policy must be scoped specifically to production subscription management actions. For the authentication requirement, a Conditional Access policy must target the Azure portal application (Microsoft Azure Management) and enforce device compliance or hybrid join as a grant control, applied only to users with production environment management roles.
Concept tested. Azure RBAC custom role tenant scoping, Conditional Access policy configuration for hybrid Azure AD-joined devices, and multi-tenant subscription management in an Enterprise Agreement - specifically understanding that custom roles defined in one Azure AD tenant cannot be reused across a different tenant without recreation, and that Conditional Access policies must be carefully scoped to target only production management users accessing the Azure portal.
Reference. https://learn.microsoft.com/en-us/azure/role-based-access-control/custom-roles and https://learn.microsoft.com/en-us/azure/active-directory/conditional-access/concept-conditional-access-conditions#device-platforms
Topics
Community Discussion
No community discussion yet for this question.

