Role-Based Access Control (RBAC) in Azure - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Understanding RBAC Role Assignments

In Azure RBAC, what does a role assignment link together?

A A subscription, a resource group, and a policy

B A user, a role definition, and a scope

C A service principal, a key vault, and a certificate

D A virtual machine, a network, and a storage account

💡 Hint

Think about what three things must be connected to grant permissions.

In Azure RBAC, a role assignment connects a security principal (like a user), a role definition (which defines permissions), and a scope (where the permissions apply).

❓ security

intermediate

Least Privilege Principle in RBAC

You want to follow the least privilege principle in Azure RBAC. Which approach best supports this principle?

A Assign users the Reader role at the management group level

B Assign users the Owner role at the subscription level

C Assign users the Contributor role at the resource group level

D Assign users custom roles with only necessary permissions at the resource level

💡 Hint

Least privilege means giving only the permissions needed, no more.

Custom roles with only necessary permissions at the smallest scope help enforce least privilege by limiting access strictly to what is needed.

❓ service_behavior

advanced

Effect of Multiple Role Assignments on Permissions

If a user has two role assignments on the same resource: Reader and Contributor, what effective permissions does the user have?

A Only Reader permissions, because it is the most restrictive

B Only Contributor permissions, because it is the least restrictive

C Both Reader and Contributor permissions combined, effectively Contributor

D No permissions due to conflict between roles

💡 Hint

Think about how Azure combines permissions from multiple roles.

Azure RBAC combines permissions from all assigned roles, so the user effectively has the combined permissions, which in this case is Contributor.

❓ service_behavior

advanced

Role Assignment Scope Impact

You assign a user the Reader role at the resource group level. Which resources can the user read?

A All resources inside the resource group and the resource group itself

B Only the resource group itself, not the resources inside it

C All resources in the subscription, including other resource groups

D Only resources explicitly assigned to the user

💡 Hint

Consider what 'scope' means in Azure RBAC.

Assigning a role at the resource group level grants permissions on the resource group and all resources contained within it.

❓ Architecture

expert

Designing RBAC for Multi-Tenant Azure Environment

You manage an Azure environment hosting multiple tenants. Each tenant has its own subscription and resource groups. You want to allow tenant admins to manage only their subscription resources without affecting others. Which RBAC design best achieves this?

A Assign tenant admins Owner role at their respective subscription level only

B Assign tenant admins Owner role at the management group level containing all subscriptions

C Assign tenant admins Contributor role at the resource group level across all subscriptions

D Assign tenant admins Reader role at the subscription level and Owner role at resource group level

💡 Hint

Think about isolating permissions per tenant subscription.

Assigning Owner role at the subscription level for each tenant admin limits their control to only their subscription, preventing cross-tenant access.

Practice

1. What is the main purpose of Role-Based Access Control (RBAC) in Azure?

easy

A. To store data securely

B. To create virtual machines automatically

C. To monitor network traffic

D. To assign permissions to users based on their roles

Solution

1. Step 1: Understand RBAC concept

   RBAC is designed to control who can do what by assigning roles with specific permissions.

2. Step 2: Identify the main function

   Assigning permissions based on roles helps manage access securely and efficiently.

3. Final Answer:

   To assign permissions to users based on their roles -> Option D

4. Quick Check:

   RBAC controls access by roles = A [OK]

Hint: RBAC = roles control permissions [OK]

Common Mistakes:

• Confusing RBAC with resource creation
• Thinking RBAC monitors traffic
• Assuming RBAC stores data

2. Which of the following is the correct way to assign a role to a user in Azure CLI?

easy

A. az role create --user [e-mail] --role Contributor

B. az user assign role --email [e-mail] --role Contributor

C. az role assignment create --assignee [e-mail] --role Contributor --scope /subscriptions/12345

D. az assign role --user [e-mail] --role Contributor

Solution

1. Step 1: Recall Azure CLI syntax for role assignment

   The correct command uses 'az role assignment create' with --assignee, --role, and --scope parameters.

2. Step 2: Match the correct command

   az role assignment create --assignee [e-mail] --role Contributor --scope /subscriptions/12345 matches the correct syntax and parameters for assigning a role.

3. Final Answer:

   az role assignment create --assignee [e-mail] --role Contributor --scope /subscriptions/12345 -> Option C

4. Quick Check:

   Correct CLI syntax = D [OK]

Hint: Use 'az role assignment create' with assignee and scope [OK]

Common Mistakes:

• Using wrong command verbs like 'assign' or 'create' alone
• Missing the --scope parameter
• Incorrect parameter names

3. Given this Azure CLI command:

az role assignment create --assignee [e-mail] --role Reader --scope /subscriptions/12345/resourceGroups/myGroup

What permission level does the user get on the resource group?

medium

A. Read-only access to the resource group

B. Write access to all resources in the subscription

C. Full control over the subscription

D. No access because scope is incorrect

Solution

1. Step 1: Analyze the role and scope

   The role is 'Reader', which grants read-only permissions. The scope is a specific resource group, limiting access to that group.

2. Step 2: Determine permission level

   The user can only read resources inside 'myGroup' resource group, not modify or access other subscription parts.

3. Final Answer:

   Read-only access to the resource group -> Option A

4. Quick Check:

   Reader role + resource group scope = read-only access [OK]

Hint: Reader role means read-only at given scope [OK]

Common Mistakes:

• Assuming Reader grants write or full control
• Confusing subscription scope with resource group scope
• Thinking scope is invalid

4. You tried to assign the 'Owner' role to a user but got an error. Which of these is the most likely cause?

medium

A. You do not have permission to assign the Owner role

B. The user email is invalid

C. The role name 'Owner' does not exist

D. You forgot to specify the subscription ID

Solution

1. Step 1: Understand role assignment permissions

   Assigning the 'Owner' role requires you to have sufficient permissions, usually Owner or User Access Administrator.

2. Step 2: Identify common error causes

   If you lack permission, Azure blocks the assignment with an error. Other options are less likely because 'Owner' is a valid role and subscription ID is often optional if context is set.

3. Final Answer:

   You do not have permission to assign the Owner role -> Option A

4. Quick Check:

   Permission needed to assign Owner role = B [OK]

Hint: Only users with rights can assign Owner role [OK]

Common Mistakes:

• Assuming role name is wrong
• Ignoring permission requirements
• Forgetting subscription context

5. You want to give a service principal permission to manage only virtual machines in a resource group without affecting other resources. Which RBAC role and scope should you assign?

hard

A. Assign 'Contributor' role at the subscription scope

B. Assign 'Virtual Machine Contributor' role at the resource group scope

C. Assign 'Owner' role at the resource group scope

D. Assign 'Reader' role at the virtual machine resource scope

Solution

1. Step 1: Identify the least privilege role for VM management

   'Virtual Machine Contributor' allows managing VMs but not other resources.

2. Step 2: Choose the correct scope

   Assigning at the resource group scope limits permissions to that group only, not the whole subscription.

3. Step 3: Evaluate other options

   'Contributor' at subscription is too broad; 'Owner' is too powerful; 'Reader' only allows viewing, not managing.

4. Final Answer:

   Assign 'Virtual Machine Contributor' role at the resource group scope -> Option B

5. Quick Check:

   Least privilege VM management at resource group = A [OK]

Hint: Use specific role + resource group scope for least privilege [OK]

Common Mistakes:

• Using broad roles like Contributor or Owner unnecessarily
• Assigning at subscription scope when resource group is enough
• Choosing Reader role which lacks management permissions