Free SC-500 Exam Braindumps
Implementing End-to-End Security Controls for Cloud and AI Workloads Questions 22–26 (page: 7)

Updated On: 23-Oct-2026
View Related Case Study

Note: This section contains one or more sets of questions with the same scenario and problem. Each question presents a unique solution to the problem. You must determine whether the solution meets the stated goals. More than one solution in the set might solve the problem. It is also possible that none of the solutions in the set solve the problem.
After you answer a question in this section, you will NOT be able to return. As a result, these questions do not appear on the Review Screen.
You have an Azure subscription that contains two virtual machine named VM1 and VM2 and a storage account named storage1.
An application runs on VM1 and VM2. The application is being migrated from storage account key authentication to Microsoft Entra authentication.
You review the current configuration and identify the following:
● VM1 and VM2 each have a system-assigned managed identity.
● Each application instance requests tokens by using only the local system-assigned managed identity.
● Network access to storage1 from VM1 and VM2 is allowed.
● No Azure RBAC data roles are assigned to the managed identities on storage1.
You need to enable the application on VM1 and VM2 to read and write blob data in storage1 by using Microsoft Entra authentication without changing how the application requests tokens.
Solution: You assign the system-assigned managed identities of VM1 and VM2 the Storage Account Contributor role scoped to storage1.

  1. Yes
  2. No

Answer(s): B

Explanation:

Storage Account Contributor grants management permissions for the storage account but does not authorize blob data access through Microsoft Entra ID. Both system-assigned managed identities need Storage Blob Data Contributor at the storage1 scope to provide the required read and write access using their existing tokens.


Reference:

https://learn.microsoft.com/en-us/azure/storage/blobs/authorize-access-azure-active-directory



View Related Case Study

Note: This section contains one or more sets of questions with the same scenario and problem. Each question presents a unique solution to the problem. You must determine whether the solution meets the stated goals. More than one solution in the set might solve the problem. It is also possible that none of the solutions in the set solve the problem.
After you answer a question in this section, you will NOT be able to return. As a result, these questions do not appear on the Review Screen.
You have an Azure subscription that contains two virtual machine named VM1 and VM2 and a storage account named storage1.
An application runs on VM1 and VM2. The application is being migrated from storage account key authentication to Microsoft Entra authentication.
You review the current configuration and identify the following:
● VM1 and VM2 each have a system-assigned managed identity.
● Each application instance requests tokens by using only the local system-assigned managed identity.
● Network access to storage1 from VM1 and VM2 is allowed.
● No Azure RBAC data roles are assigned to the managed identities on storage1.
You need to enable the application on VM1 and VM2 to read and write blob data in storage1 by using Microsoft Entra authentication without changing how the application requests tokens.
Solution: You add the system-assigned managed identities of VM1 and VM2 to a Microsoft Entra security group, and assign the group the Storage Blob Data Contributor role scoped to storage1.

  1. Yes
  2. No

Answer(s): A

Explanation:

Managed identities can inherit Azure RBAC permissions through Microsoft Entra security-group membership. Assigning Storage Blob Data Contributor to the group grants both identities the required blob read and write permissions while preserving the application’s existing token requests. Group membership changes can take several hours to become effective because of managed-identity token caching.


Reference:

https://learn.microsoft.com/en-us/entra/identity/managed-identities-azure-resources/managed-ident ity-best-practice-recommendations



View Related Case Study

HOTSPOT (Drag and Drop is not supported)
You have an Azure subscription that contains a resource group named RG1. RG1 contains a virtual machine named VM1 that uses Microsoft Entra authentication.
You have two custom Azure roles named Role1 and Role2 that are scoped to RG1.
The permissions for Role1 are shown in the following JSON code.

The permissions for Role2 are shown in the following JSON code.

You assign the roles to the users shown in the following table.

For each of the following statements, select Yes if the statement is true. Otherwise, select No.
Note: Each correct selection is worth one point.
Hot Area:

  1. See Explanation section for answer.

Answer(s): A

Explanation:




No
Yes
No
Role1 excludes the virtual machine delete action, so User1 cannot delete VM1. Azure RBAC permissions are cumulative, and NotActions is not an explicit deny. Because User2 also has Role2, which grants all virtual machine actions without excluding deletion, User2 can delete VM1.
Signing in to an Azure VM with Microsoft Entra credentials requires the appropriate VM login data permissions, such as those provided by the Virtual Machine User Login or Virtual Machine Administrator Login role. The custom roles shown have no DataActions, so User3 does not receive Microsoft Entra VM sign-in permission.



View Related Case Study

HOTSPOT (Drag and Drop is not supported)
You have an Azure key vault named KV1 that uses role-based access control (RBAC) for data plane authorization.
You have multiple Azure App Service web apps that retrieve a SQL connection string stored as a secret in KV1.
You need to ensure that the web apps can access KV1. The solution must minimize the number of required identities and follow the principle of least privilege.
What should you do? To answer, select the appropriate options in the answer area.
Note: Each correct selection is worth one point.
Hot Area:

  1. See Explanation section for answer.

Answer(s): A

Explanation:



Box 1: User-Assigned Managed Identity
The best type of workload identity for this scenario is a User-Assigned Managed Identity.
Minimizes Required Identities: Unlike a system-assigned managed identity (which creates one distinct identity per App Service), a single user-assigned managed identity can be created once and shared across multiple Azure App Service web apps.
Enforces Least Privilege: You can assign this single identity the specific, built-in Azure RBAC role of Key Vault Secrets User. This scope restricts the apps to only reading the secret contents (the SQL connection string) without granting permissions to delete, list, or alter other data plane components like keys or certificates.
Eliminates Credential Management: Because it is an Azure-managed workload identity, there are no client secrets or certificates to rotate, secure, or accidentally expose in your application configurations.
Box 2: Key Vault Secrets User
Assign the Key Vault Secrets User built-in role to the web apps.
Principle of Least Privilege: The Key Vault Secrets User role grants authorization to read secret contents and properties. It completely restricts the web apps from modifying, deleting, or creating secrets. It also denies access to cryptographic keys and certificates stored in the same vault.


Reference:

https://learn.microsoft.com/en-us/azure/app-service/overview-managed-identity https://learn.microsoft.com/en-us/azure/key-vault/general/rbac-guide



View Related Case Study

HOTSPOT (Drag and Drop is not supported)
You have an Azure Container Registry.
You add role assignments for Registry1 as shown in the following table.

Which users can upload images to Registry1 and which users can download images from Registry1? To answer, select the appropriate options in the answer area.
Note: Each correct selection is worth one point.
Hot Area:

  1. See Explanation section for answer.

Answer(s): A

Explanation:




Upload images: User1 and User4 only
Download images: User1, User2, and User4
The AcrPush role permits both pushing and pulling images. The AcrPull role permits pulling images. In the registry RBAC model used by this question, the Contributor role includes the registry operations required to push and pull images. Therefore, User1 and User4 can upload images, while User1, User2, and User4 can download them.


Reference:

https://learn.microsoft.com/en-us/azure/role-based-access-control/built-in-roles/containers



Viewing page 7 of 43
Viewing questions 31 - 35 out of 207 questions


Post your Comments and Discuss Microsoft SC-500 exam prep with other Community members:

AI Tutor AI Tutor 👋 I’m here to help!