Microsoft SC-300 Practice Test 37
Question 360
An app running on a supported Azure host needs token access without revealing credentials to developers. How is token retrieval secured?
- The linked system-assigned service principal is deleted with the Azure resource.
- Request tokens through the host's managed identity endpoint.
- Existing managed identity token acquisition and authorized app calls can fail.
- Assign Storage Blob Data Reader at the permitted storage scope.
Explanation
Correct Answer
B:The platform brokers tokens without exposing a reusable password or certificate to the app. This matters here because an app running on a supported Azure host needs token access without revealing credentials to developers. How is….
Incorrect Answers
A:System-assigned identity lifecycle follows the resource rather than an independent identity object. The platform brokers tokens without exposing a reusable password or certificate to the app.
C:Removing the workload identity breaks identity-based access for consumers. This matters here because an app running on a supported Azure host needs token access without revealing credentials to developers. How is….
D:Azure Storage blob data permissions are independent of successful managed identity authentication. The platform brokers tokens without exposing a reusable password or certificate to the app.
Question 361
Three Azure Functions must use one independently managed identity to reach the same service. Which identity type fits?
- Create one user-assigned managed identity and attach it to the functions.
- Request tokens through the host's managed identity endpoint.
- Specify the intended managed identity client ID when acquiring the token.
- Create separate user-assigned identities aligned to distinct least-privilege boundaries.
Explanation
Correct Answer
A:A user-assigned identity is a standalone Azure resource reusable by multiple supported compute resources.
Incorrect Answers
B:The platform brokers tokens without exposing a reusable password or certificate to the app. A user-assigned identity is a standalone Azure resource reusable by multiple supported compute resources.
C:Multi-identity hosts must unambiguously select the principal that needs access.
D:Reusing an identity across unrelated trust domains broadens access and blast radius. A user-assigned identity is a standalone Azure resource reusable by multiple supported compute resources.
Question 362
A compute resource is deleted, but its identity must remain for a replacement. What identity type should have been used?
- Use a user-assigned managed identity with independent lifecycle.
- Specify the intended managed identity client ID when acquiring the token.
- Assign Storage Blob Data Reader at the permitted storage scope.
- Request a token for the intended Key Vault resource audience.
Explanation
Correct Answer
A:User-assigned identities outlive individual resources until explicitly removed.
Incorrect Answers
B:Multi-identity hosts must unambiguously select the principal that needs access. This matters here because a compute resource is deleted, but its identity must remain for a replacement. What identity type should have been used.
C:Azure Storage blob data permissions are independent of successful managed identity authentication. This matters here because a compute resource is deleted, but its identity must remain for a replacement. What identity type should have been used.
D:Valid tokens are audience-specific and cannot authorize unrelated resource APIs.
Question 363
A storage authorization policy should remain tied to the same identity across blue-green deployments. Which pattern helps?
- Grant permissions to a shared user-assigned managed identity.
- Assign a suitable storage data role at the narrow container scope where supported.
- Grant the appropriate resource write action through an Azure RBAC role.
- Create separate user-assigned identities aligned to distinct least-privilege boundaries.
Explanation
Correct Answer
A:Reusing a stable principal avoids regranting access when app instances are replaced.
Incorrect Answers
B:Least privilege limits workload access to the minimum storage resource boundary. This matters here because a storage authorization policy should remain tied to the same identity across blue-green deployments. Which pattern….
C:The Azure Reader role does not permit resource creation or configuration updates.
D:Reusing an identity across unrelated trust domains broadens access and blast radius.
Question 364
A host has several user-assigned managed identities and the SDK chooses the wrong one. What selector should be configured?
- Attach a separate user-assigned managed identity for the second permission set.
- Assign a suitable storage data role at the narrow container scope where supported.
- Grant Key Vault permissions to the user-assigned identity's principal.
- Specify the intended managed identity client ID when acquiring the token.
Explanation
Correct Answer
D:Multi-identity hosts must unambiguously select the principal that needs access. This matters here because a host has several user-assigned managed identities and the SDK chooses the wrong one. What selector should be….
Incorrect Answers
A:Supported resources can use user-assigned identities alongside a system-assigned identity.
B:Least privilege limits workload access to the minimum storage resource boundary. This matters here because a host has several user-assigned managed identities and the SDK chooses the wrong one. What selector should be….
C:Identity attachment authenticates the workload but does not authorize Key Vault operations.
Question 365
A user-assigned identity is attached to a VM but Azure Key Vault calls are forbidden. What control remains necessary?
- The linked system-assigned service principal is deleted with the Azure resource.
- Grant Key Vault permissions to the user-assigned identity's principal.
- Attach a separate user-assigned managed identity for the second permission set.
- Assign Storage Blob Data Reader at the permitted storage scope.
Explanation
Correct Answer
B:Identity attachment authenticates the workload but does not authorize Key Vault operations. This matters here because a user-assigned identity is attached to a VM but Azure Key Vault calls are forbidden. What control remains necessary.
Incorrect Answers
A:System-assigned identity lifecycle follows the resource rather than an independent identity object. This alternative addresses a VM with a system-assigned identity is deleted. What happens to its managed identity? It does not meet the specified case, which requires grant key vault permissions to the user-assigned identity's principal: Identity attachment authenticates the workload but does not authorize Key Vault operations.
C:Supported resources can use user-assigned identities alongside a system-assigned identity. This matters here because a user-assigned identity is attached to a VM but Azure Key Vault calls are forbidden. What control remains necessary.
D:Azure Storage blob data permissions are independent of successful managed identity authentication. This matters here because a user-assigned identity is attached to a VM but Azure Key Vault calls are forbidden. What control remains necessary.
Question 366
A team wants to share one identity across unrelated apps with radically different privileges. What principle should be applied?
- Create separate user-assigned identities aligned to distinct least-privilege boundaries.
- Specify the intended managed identity client ID when acquiring the token.
- Attach a separate user-assigned managed identity for the second permission set.
- Enable and authorize a managed identity on the hosting Azure resource.
Explanation
Correct Answer
A:Reusing an identity across unrelated trust domains broadens access and blast radius. This matters here because a team wants to share one identity across unrelated apps with radically different privileges. What principle should….
Incorrect Answers
B:Multi-identity hosts must unambiguously select the principal that needs access. This matters here because a team wants to share one identity across unrelated apps with radically different privileges. What principle should….
C:Supported resources can use user-assigned identities alongside a system-assigned identity. This matters here because a team wants to share one identity across unrelated apps with radically different privileges. What principle should….
D:The workload's managed identity can request tokens through its supported runtime endpoint. This matters here because a team wants to share one identity across unrelated apps with radically different privileges. What principle should….
Question 367
A user-assigned managed identity is removed from a function but retained in the subscription. What should security check?
- Create one user-assigned managed identity and attach it to the functions.
- Create the user-assigned identity as a separate Azure resource.
- Review unused identity role assignments and detach or delete it as appropriate.
- Remove the relevant downstream RBAC or resource permission assignment.
Explanation
Correct Answer
C:Standalone identities can persist with permissions after individual resource attachment changes.
Incorrect Answers
A:A user-assigned identity is a standalone Azure resource reusable by multiple supported compute resources. Standalone identities can persist with permissions after individual resource attachment changes.
B:User-assigned managed identities exist independently of applications or VMs.
D:Authentication identity lifecycle can be separated from resource authorization grants.
Question 368
A deployment pipeline needs to create a user-assigned identity before any compute instances exist. Is that possible?
- Review unused identity role assignments and detach or delete it as appropriate.
- Use a group managed service account where the service supports it.
- Use a service principal with approved application permissions.
- Create the user-assigned identity as a separate Azure resource.
Explanation
Correct Answer
D:User-assigned managed identities exist independently of applications or VMs. This matters here because a deployment pipeline needs to create a user-assigned identity before any compute instances exist. Is that possible.
Incorrect Answers
A:Standalone identities can persist with permissions after individual resource attachment changes. This matters here because a deployment pipeline needs to create a user-assigned identity before any compute instances exist. Is that possible.
B:GMSAs provide locally managed domain service credentials with automatic password management. This matters here because a deployment pipeline needs to create a user-assigned identity before any compute instances exist. Is that possible.
C:Application-only workloads authenticate as service principals instead of impersonating a shared employee.
Question 369
A workload has a system-assigned identity and needs another isolated set of resource permissions. What addition fits?
- Attach a separate user-assigned managed identity for the second permission set.
- The linked system-assigned service principal is deleted with the Azure resource.
- Enable and authorize a managed identity on the hosting Azure resource.
- Inventory every resource attachment and downstream authorization before deleting the user-assigned identity.
Explanation
Correct Answer
A:Supported resources can use user-assigned identities alongside a system-assigned identity. This matters here because a workload has a system-assigned identity and needs another isolated set of resource permissions. What addition fits.
Incorrect Answers
B:System-assigned identity lifecycle follows the resource rather than an independent identity object. This alternative addresses a VM with a system-assigned identity is deleted. What happens to its managed identity? It does not meet the specified case, which requires attach a separate user-assigned managed identity for the second permission set: Supported resources can use user-assigned identities alongside a system-assigned identity.
C:The workload's managed identity can request tokens through its supported runtime endpoint. This matters here because a workload has a system-assigned identity and needs another isolated set of resource permissions. What addition fits.
D:A shared identity has multiple consumers despite being represented by one standalone resource.
Question 370
An identity is shared by multiple applications, and deleting it unexpectedly breaks all of them. What dependency should be tracked?
- Use a service principal with approved application permissions.
- Inventory every resource attachment and downstream authorization before deleting the user-assigned identity.
- The linked system-assigned service principal is deleted with the Azure resource.
- Create one user-assigned managed identity and attach it to the functions.
Explanation
Correct Answer
B:A shared identity has multiple consumers despite being represented by one standalone resource. This matters here because an identity is shared by multiple applications, and deleting it unexpectedly breaks all of them. What dependency….
Incorrect Answers
A:Application-only workloads authenticate as service principals rather than impersonating a shared employee. This alternative addresses a vendor integration must access Microsoft Graph without an interactive user. Which identity should it use? It does not meet the specified case, which requires inventory every resource attachment and downstream authorization before deleting the user-assigned identity: A shared identity has multiple consumers despite being represented by one standalone resource.
C:System-assigned identity lifecycle follows the resource rather than an independent identity object. A shared identity has multiple consumers despite being represented by one standalone resource.
D:A user-assigned identity is a standalone Azure resource reusable by multiple supported compute resources. A shared identity has multiple consumers despite being represented by one standalone resource.