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…

This hotspot question tests knowledge of Azure AD Conditional Access policies, hybrid Azure AD join requirements, and role assignment scopes within a multi-tenant, Enterprise Agreement environment at Litware.

Submitted by andres_qro· Mar 6, 2026Network Design

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 How should the migrated databases DB1 and DB2 be implemented in Azure? Answer:

Exhibits

Answer Area

Database:
A single Azure SQL databaseAzure SQL Managed InstanceAn Azure SQL Database elastic pool
Service tier:
HyperscaleBusiness CriticalGeneral Purpose

Explanation

Approach. The requirement states that only users managing the production environment via the Azure portal must connect from a hybrid Azure AD-joined device and use multi-factor authentication (MFA). This is implemented through an Azure AD Conditional Access policy targeting the specific users/roles accessing production subscriptions, with conditions requiring a compliant/hybrid Azure AD-joined device and MFA grant controls. Role1, which grants DataActions read on blobs and files, is a custom Azure RBAC role defined at the litware.com tenant level and can be assigned within any subscription linked to that tenant but cannot be directly used in the dev.litware.com tenant subscriptions since custom roles are tenant-scoped. Dedicated hosts for App1 VMs must be planned at the subscription level where the VMs will reside, and ExpressRoute connectivity already provides the hybrid network path needed for on-premises workloads migrating to Azure.

Concept tested. Azure AD Conditional Access policies for hybrid Azure AD-joined device requirements, custom Azure RBAC role tenant scoping, and planning Azure dedicated hosts and ExpressRoute-connected hybrid environments for workload migration.

Reference. https://learn.microsoft.com/en-us/azure/active-directory/conditional-access/overview | https://learn.microsoft.com/en-us/azure/role-based-access-control/custom-roles | https://learn.microsoft.com/en-us/azure/virtual-machines/dedicated-hosts

Topics

#Azure#Database Selection#Service Tiers#Application Architecture

Community Discussion

No community discussion yet for this question.

Full AZ-305 Practice