Access policies vs RBAC in Azure - Interactive Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to assign a role to a user using Azure RBAC.

Azure

az role assignment create --assignee [1] --role "Reader" --scope /subscriptions/00000000-0000-0000-0000-000000000000

Drag options to blanks, or click blank then click option'

AstorageAccount1

BvirtualMachine1

CresourceGroup1

[e-mail]

Attempts:

3 left

💡 Hint

Common Mistakes

Using a resource name instead of a user identity as assignee.

Confusing the role name with the assignee.

The assignee must be a user or service principal identity, such as an email address, to assign a role in RBAC.

2fill in blank

medium

Complete the code to create an access policy for an Azure Key Vault.

Azure

az keyvault set-policy --name MyKeyVault --object-id [1] --secret-permissions get list

Drag options to blanks, or click blank then click option'

AresourceGroup1

B00000000-0000-0000-0000-000000000000

CReader

DMyKeyVault

Attempts:

3 left

💡 Hint

Common Mistakes

Using the Key Vault name instead of the object-id.

Using role names instead of object-id.

The object-id is the unique identifier of the user or service principal for whom the access policy is set.

3fill in blank

hard

Fix the error in the command to assign a role at the resource group level.

Azure

az role assignment create --assignee [e-mail] --role [1] --scope /subscriptions/00000000-0000-0000-0000-000000000000/resourceGroups/myResourceGroup

Drag options to blanks, or click blank then click option'

AContributor

BmyResourceGroup

[e-mail]

DKey Vault

Attempts:

3 left

💡 Hint

Common Mistakes

Using resource group name as role.

Using user email as role.

The role parameter must be a valid Azure role name like Contributor, Reader, or Owner.

4fill in blank

hard

Fill both blanks to create an access policy that grants secret permissions.

Azure

az keyvault set-policy --name MyVault --object-id [1] --[2]-permissions get list

Drag options to blanks, or click blank then click option'

A00000000-0000-0000-0000-000000000001

Bkey

Csecret

Dcertificate

Attempts:

3 left

💡 Hint

Common Mistakes

Using resource names instead of object-id.

Mixing permission types incorrectly.

The object-id identifies the user, and the permission type must be either key, secret, or certificate. Here, secret-permissions are granted.

5fill in blank

hard

Fill all three blanks to assign the Reader role to a user at a subscription scope.

Azure

az role assignment create --assignee [1] --role [2] --scope [3]

Drag options to blanks, or click blank then click option'

[e-mail]

BReader

C/subscriptions/00000000-0000-0000-0000-000000000000

DContributor

Attempts:

3 left

💡 Hint

Common Mistakes

Using resource names instead of user email for assignee.

Using invalid role names.

Incorrect scope format.

The assignee is the user email, the role is Reader, and the scope is the subscription ID path.

Practice

1. What is the main difference between Azure Access Policies and RBAC?

easy

A. RBAC controls network traffic; Access Policies manage user passwords.

B. Access Policies grant permissions directly on resources; RBAC assigns roles at scopes.

C. Access Policies are used only for virtual machines; RBAC is for databases.

D. RBAC is a legacy system; Access Policies are the modern replacement.

Solution

1. Step 1: Understand Access Policies

   Access Policies give permissions directly on specific resources, like a key vault.

2. Step 2: Understand RBAC

   RBAC assigns roles with permissions at different levels like subscription or resource group.

3. Final Answer:

   Access Policies grant permissions directly on resources; RBAC assigns roles at scopes. -> Option B

4. Quick Check:

   Access Policies = direct resource permissions, RBAC = role-based scopes [OK]

Hint: Access Policies = direct, RBAC = role at scope [OK]

Common Mistakes:

• Confusing Access Policies with RBAC roles
• Thinking RBAC only applies to virtual machines
• Assuming Access Policies control network settings

2. Which of the following is the correct way to assign an RBAC role using Azure CLI?

easy

A. az network policy add --role <role> --user <user>

B. az accesspolicy set --user <user> --permission <perm>

C. az vm assign-role --user <user> --role <role>

D. az role assignment create --assignee <user> --role <role> --scope <scope>

Solution

1. Step 1: Identify correct RBAC command

   The Azure CLI command to assign RBAC roles is 'az role assignment create' with assignee, role, and scope parameters.

2. Step 2: Verify other options

   Other options mention access policies or unrelated commands which are invalid for RBAC role assignment.

3. Final Answer:

   az role assignment create --assignee <user> --role <role> --scope <scope> -> Option D

4. Quick Check:

   RBAC role assignment uses 'az role assignment create' [OK]

Hint: RBAC role assignment uses 'az role assignment create' [OK]

Common Mistakes:

• Using access policy commands for RBAC
• Mixing VM or network commands with RBAC
• Omitting the scope parameter

3. Given this Azure CLI command output snippet for a key vault access policy:

"permissions": {"keys": ["get", "list"], "secrets": ["get"]}

What permissions does this policy grant?

medium

A. Allows only listing keys, no secret access.

B. Allows creating and deleting keys and secrets.

C. Allows getting and listing keys, and getting secrets.

D. Allows full control over keys and secrets.

Solution

1. Step 1: Read the permissions for keys

   The keys permission includes 'get' and 'list', so it allows reading and listing keys.

2. Step 2: Read the permissions for secrets

   The secrets permission includes only 'get', so it allows reading secrets but no other actions.

3. Final Answer:

   Allows getting and listing keys, and getting secrets. -> Option C

4. Quick Check:

   Permissions match get/list keys and get secrets [OK]

Hint: Check each permission list carefully for allowed actions [OK]

Common Mistakes:

• Assuming 'get' means create or delete
• Confusing 'list' with full control
• Ignoring secret permissions

4. You assigned an RBAC role to a user but they still cannot access a key vault secret. What is the most likely cause?

medium

A. The user lacks an access policy granting secret permissions on the key vault.

B. The RBAC role was assigned at subscription level, which is too broad.

C. The user needs to restart their Azure portal session.

D. RBAC roles do not control access to key vault secrets.

Solution

1. Step 1: Understand RBAC vs Access Policies for Key Vault

   Key vault secrets require access policies to grant permissions, RBAC alone may not suffice.

2. Step 2: Analyze the problem

   Even if RBAC role is assigned, without an access policy granting secret permissions, access is denied.

3. Final Answer:

   The user lacks an access policy granting secret permissions on the key vault. -> Option A

4. Quick Check:

   Key vault secret access requires access policies [OK]

Hint: Key vault secrets need access policies, not just RBAC [OK]

Common Mistakes:

• Assuming RBAC alone controls key vault secrets
• Thinking subscription-level RBAC restricts access
• Believing portal restart fixes permission issues

5. You want to secure an Azure Key Vault so that only a specific user can read secrets, and a group can manage keys. Which approach follows best practices?

hard

A. Assign specific RBAC roles to the user for secret read (Key Vault Secrets User) and to the group for key management (Key Vault Crypto Officer).

B. Create an access policy granting the user secret read permission; assign an RBAC role to the group for key management.

C. Use access policies for both user and group to grant all permissions.

D. Assign the user an RBAC role for secrets and the group an access policy for keys.

Solution

1. Step 1: Choose RBAC as best practice

   Azure recommends RBAC for Key Vault. Disable access policies and enable RBAC authorization on the Key Vault.

2. Step 2: Assign granular roles at Key Vault scope

   Assign 'Key Vault Secrets User' role to user (get/list secrets). Assign 'Key Vault Crypto Officer' role to group (manage keys).

3. Final Answer:

   Assign specific RBAC roles to the user for secret read (Key Vault Secrets User) and to the group for key management (Key Vault Crypto Officer). -> Option A

4. Quick Check:

   RBAC Secrets User + Crypto Officer roles [OK]

Hint: RBAC best practice: Secrets User + Crypto Officer roles [OK]

Common Mistakes:

• Trying to mix Access Policies and RBAC (not possible)
• Using access policies for everything (legacy method)
• Assigning overly broad roles or permissions