nerdexam
Microsoft

AZ-500 · Question #1

Case Study 1 - Litware, Inc Overview Litware, Inc. is a digital media company that has 500 employees in the Chicago area and 20 employees in the San Francisco area. Existing Environment Litware has…

The correct answer is D. Change the membership type of Group1 to Assigned. Explanation Why D is Correct: The requirement states that all San Francisco users and their devices must be members of Group1. To include both users and devices in the same group, the membership type must be Assigned, which allows manual addition of any combination of users…

Submitted by kev92· Mar 6, 2026Secure identity and access

Question

Case Study 1 - Litware, Inc Overview Litware, Inc. is a digital media company that has 500 employees in the Chicago area and 20 employees in the San Francisco area. Existing Environment Litware has an Azure subscription named Sub1 that has a subscription ID of 43894a43-17c2- 4a39-8cfc-3540c2653ef4. Sub1 is associated to an Azure Active Directory (Azure AD) tenant named litwareinc.com. The tenant contains the user objects and the device objects of all the Litware employees and their devices. Each user is assigned an Azure AD Premium P2 license. Azure AD Privileged Identity Management (PIM) is activated. The tenant contains the groups shown in the following table. The Azure subscription contains the objects shown in the following table. Azure Security Center is set to the Free tier. Planned changes Litware plans to deploy the Azure resources shown in the following table. Litware identifies the following identity and access requirements: All San Francisco users and their devices must be members of Group1. The members of Group2 must be assigned the Contributor role to Resource Group2 by using a permanent eligible assignment. Users must be prevented from registering applications in Azure AD and from consenting to applications that access company information on the users' behalf. Platform Protection Requirements Litware identifies the following platform protection requirements: Microsoft Antimalware must be installed on the virtual machines in Resource Group1. The members of Group2 must be assigned the Azure Kubernetes Service Cluster Admin Role. Azure AD users must be to authenticate to AKS1 by using their Azure AD credentials. Following the implementation of the planned changes, the IT team must be able to connect to VM0 by using JIT VM access. A new custom RBAC role named Role1 must be used to delegate the administration of the managed disks in Resource Group1. Role1 must be available only for Resource Group1. Security Operations Requirements Litware must be able to customize the operating system security configurations in Azure Security Center. You need to meet the identity and access requirements for Group1. What should you do?

Exhibits

AZ-500 question #1 exhibit 1
AZ-500 question #1 exhibit 2
AZ-500 question #1 exhibit 3
AZ-500 question #1 exhibit 4
AZ-500 question #1 exhibit 5
AZ-500 question #1 exhibit 6

Options

  • AAdd a members
  • BDelete Group1. Create a new group named Group1 that has a membership type of Office 365.
  • CModify the membership rule of Group1.
  • DChange the membership type of Group1 to Assigned.

How the community answered

(26 responses)
  • A
    4% (1)
  • B
    4% (1)
  • C
    12% (3)
  • D
    81% (21)

Explanation

Explanation

Why D is Correct: The requirement states that all San Francisco users and their devices must be members of Group1. To include both users and devices in the same group, the membership type must be Assigned, which allows manual addition of any combination of users, devices, and other objects. Dynamic membership rules (which Group1 currently uses) can only target either users or devices - not both simultaneously in a single group.

Why the Distractors are Wrong:

  • A (Add members): Simply adding members won't work if Group1 currently has a Dynamic membership type, as dynamic groups don't allow manual member additions - the rule controls membership automatically.
  • B (Create an Office 365 group): Office 365 groups are designed for collaboration (email, Teams, SharePoint) and cannot contain device objects, which is a core requirement here.
  • C (Modify the membership rule): A dynamic rule still cannot combine both user and device objects in a single group - Azure AD enforces that dynamic groups target one object type only.

Memory Tip: Think "Assigned = All types allowed" - when you need mixed membership (users + devices), always choose Assigned. Dynamic rules are powerful but object-type-specific; if the requirement mixes object types, dynamic won't work.

Topics

#Azure AD Groups#Group Membership#Dynamic Groups#Identity Management

Community Discussion

No community discussion yet for this question.

Sign up to join the discussion
Full AZ-500 Practice