nerdexam
Microsoft

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.

Submitted by amina.ke· Mar 6, 2026Process and manage data

Question

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 dev.litware.com tenant. All the subscriptions are in an Enterprise Agreement (EA). The litware.com tenant contains a custom Azure role-based access control (Azure RBAC) role named Role1 that grants the DataActions read permission to the blobs and files in Azure Storage. On-Premises Environment The on-premises network of Litware contains the resources shown in the following table. Network Environment Litware has ExpressRoute connectivity to Azure. Planned Changes and Requirements Litware plans to implement the following changes: Migrate DB1 and DB2 to Azure. Migrate App1 to Azure virtual machines. Migrate the external storage used by App1 to Azure Storage. Deploy the Azure virtual machines that will host App1 to Azure dedicated hosts. Authentication and Authorization Requirements Litware identifies the following authentication and authorization requirements: Only users that manage the production environment by using the Azure portal must connect from a hybrid Azure AD-joined device and authenticate by using Azure Multi-Factor Authentication (MFA). The Network Contributor built-in RBAC role must be used to grant permissions to the network administrators for all the virtual networks in all the Azure subscriptions. To access the resources in Azure, App1 must use the managed identity of the virtual machines that will host the app. RBAC roles must be applied at the highest level possible. Resiliency Requirements Litware identifies the following resiliency requirements: Once migrated to Azure, DB1 and DB2 must meet the following requirements: - Maintain availability if two availability zones in the local Azure region fail. - Fail over automatically. - Minimize I/O latency. App1 must meet the following requirements: - Be hosted in an Azure region that supports availability zones. - Be hosted on Azure virtual machines that support automatic scaling. - Maintain availability if two availability zones in the local Azure region fail. Security and Compliance Requirements Litware identifies the following security and compliance requirements: Once App1 is migrated to Azure, you must ensure that new data can be written to the app, and the modification of new and existing data is prevented for a period of three years. On-premises users and services must be able to access the Azure Storage account that will host the data in App1. Access to the public endpoint of the Azure Storage account that will host the App1 data must be prevented. All Azure SQL databases in the production environment must have Transparent Data Encryption (TDE) enabled. App1 must NOT share physical hardware with other workloads. Business Requirements Litware identifies the following business requirements: Minimize administrative effort. Minimize costs. Hotspot Question You plan to migrate App1 to Azure. You need to recommend a storage solution for App1 that meets the security and compliance requirements. Which type of storage should you recommend, and how should you recommend configuring the storage? To answer, select the appropriate options in the answer area. NOTE: Each correct selection is worth one point. Answer:

Exhibits

AZ-305 question #3 exhibit 1
AZ-305 question #3 exhibit 2

Answer Area

  • Storage account type:Standard general-purpose v2
    Premium page blobsPremium file sharesStandard general-purpose v2
  • Configuration:Hierarchical namespace
    NFSv3Large 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

#Azure Data Lake Storage#hierarchical namespace#storage compliance#WORM policy

Community Discussion

No community discussion yet for this question.

Full AZ-305 Practice