Microsoft SC-300 Practice Test 38
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.
Question 371
A GitHub Actions pipeline must deploy to Azure without a stored client secret. Which authentication arrangement fits?
- Confirm the new host is allowed to retrieve the gMSA managed password.
- Match issuer, subject and audience against the federated credential configuration.
- Use workload identity federation with an approved OIDC credential on a service principal.
- Use service principal sign-in logs for application-only authentications.
Explanation
Correct Answer
C:Federated credentials exchange trusted external assertions for Entra tokens instead of persistent secrets.
Incorrect Answers
A:GMSA use requires host authorization from Active Directory.
B:Federated credential trust requires claim values consistent with the approved issuer and workload. Federated credentials exchange trusted external assertions for Entra tokens instead of persistent secrets.
D:Workload sign-ins are recorded separately from interactive human sessions.
Question 372
An external CI system has a valid OIDC assertion but Entra refuses token exchange. What should be verified?
- Use workload identity federation with an approved OIDC credential on a service principal.
- Verify application credential validity and the certificate matching the registered key.
- Match issuer, subject and audience against the federated credential configuration.
- Enable and authorize a managed identity on the hosting Azure resource.
Explanation
Correct Answer
C:Federated credential trust requires claim values consistent with the approved issuer and workload.
Incorrect Answers
A:Federated credentials exchange trusted external assertions for Entra tokens instead of persistent secrets. Federated credential trust requires claim values consistent with the approved issuer and workload.
B:Certificate-based client assertions require a current trusted key on the app object. Federated credential trust requires claim values consistent with the approved issuer and workload.
D:The workload's managed identity can request tokens through its supported runtime endpoint. Federated credential trust requires claim values consistent with the approved issuer and workload.
Question 373
A vendor integration must access Microsoft Graph without an interactive user. Which identity should it use?
- Restrict the federated credential subject to the authorized repository and branch context.
- Use a service principal with approved application permissions.
- Create the user-assigned identity as a separate Azure resource.
- Existing managed identity token acquisition and authorized app calls can fail.
Explanation
Correct Answer
B:Application-only workloads authenticate as service principals rather than impersonating a shared employee. This matters here because a vendor integration must access Microsoft Graph without an interactive user. Which identity should it use.
Incorrect Answers
A:Narrow OIDC subject matching prevents token exchange from unauthorized workflows.
C:User-assigned managed identities exist independently of applications or VMs. This matters here because a vendor integration must access Microsoft Graph without an interactive user. Which identity should it use.
D:Removing the workload identity breaks identity-based access for consumers. This matters here because a vendor integration must access Microsoft Graph without an interactive user. Which identity should it use.
Question 374
An external CI pipeline uses OIDC to deploy resources into one Azure subscription without stored secrets. Which THREE steps create a controlled workload trust? (Select THREE.)
- Create or select an application identity with a federated identity credential.
- Grant the service principal an appropriate Azure RBAC role at the intended subscription or resource scope.
- Trust tokens from every OIDC issuer with no subject restrictions.
- Give all pipeline contributors permanent tenant Global Administrator.
- Bind the issuer, subject and audience to the approved pipeline and branch.
- Embed a permanent service principal client secret in the public repository.
Explanation
Correct Answers
A:Federated credentials let a trusted external OIDC assertion obtain Entra tokens.
B:Token authentication does not automatically authorize the deployment operations.
E:Claim matching prevents a different workflow from exchanging unrelated assertions.
Incorrect Answers
C:Unconstrained issuer and subject trust could let unauthorized workflows obtain tokens.
D:Tenant global privileges are excessive and not the same as scoped Azure resource deployment rights.
F:A public long-lived secret defeats the no-stored-credentials requirement.
Question 375
A team rotates an app's certificate but token issuance still fails. What should be checked?
- Replace delegated user tokens with a managed identity or service principal as appropriate.
- Use workload identity federation with an approved OIDC credential on a service principal.
- Assign explicit Azure RBAC roles separately at each approved subscription or resource scope.
- Verify application credential validity and the certificate matching the registered key.
Explanation
Correct Answer
D:Certificate-based client assertions require a current trusted key on the app object.
Incorrect Answers
A:Unattended application work needs a workload identity rather than a human session.
B:Federated credentials exchange trusted external assertions for Entra tokens instead of persistent secrets. Certificate-based client assertions require a current trusted key on the app object.
C:Resource-role assignments are scoped and do not travel automatically with a principal.
Question 376
An automation reuses an employee's personal refresh token for server tasks. What redesign fits?
- Enable the VM's system-assigned managed identity and authorize it to Key Vault.
- Verify application credential validity and the certificate matching the registered key.
- Replace delegated user tokens with a managed identity or service principal as appropriate.
- Use workload identity federation with an approved OIDC credential on a service principal.
Explanation
Correct Answer
C:Unattended application work needs a workload identity instead of a human session.
Incorrect Answers
A:System-assigned managed identity provides automatically managed workload credentials tied to that VM. This matters here because an automation reuses an employee's personal refresh token for server tasks. What redesign fits.
B:Certificate-based client assertions require a current trusted key on the app object. This matters here because an automation reuses an employee's personal refresh token for server tasks. What redesign fits.
D:Federated credentials exchange trusted external assertions for Entra tokens instead of persistent secrets. Unattended application work needs a workload identity rather than a human session.
Question 377
A platform team must separate developer identities from workload identities in reporting. What logs matter?
- Grant the appropriate resource write action through an Azure RBAC role.
- Use workload identity federation with an approved OIDC credential on a service principal.
- Use one system-assigned identity per resource and user-assigned identities for additional separation.
- Use service principal sign-in logs for application-only authentications.
Explanation
Correct Answer
D:Workload sign-ins are recorded separately from interactive human sessions. This matters here because a platform team must separate developer identities from workload identities in reporting. What logs matter.
Incorrect Answers
A:The Azure Reader role does not permit resource creation or configuration updates. This matters here because a platform team must separate developer identities from workload identities in reporting. What logs matter.
B:Federated credentials exchange trusted external assertions for Entra tokens instead of persistent secrets. This matters here because a platform team must separate developer identities from workload identities in reporting. What logs matter.
C:System-assigned identities are bound to their respective resource instance. This matters here because a platform team must separate developer identities from workload identities in reporting. What logs matter.
Question 378
An app needs a federated credential only for the main branch, not untrusted pull requests. What trust restriction matters?
- Restrict the federated credential subject to the authorized repository and branch context.
- Use a group managed service account where the service supports it.
- Use workload identity federation with an approved OIDC credential on a service principal.
- Replace delegated user tokens with a managed identity or service principal as appropriate.
Explanation
Correct Answer
A:Narrow OIDC subject matching prevents token exchange from unauthorized workflows. This matters here because an app needs a federated credential only for the main branch, not untrusted pull requests. What trust restriction….
Incorrect Answers
B:GMSAs provide locally managed domain service credentials with automatic password management. This matters here because an app needs a federated credential only for the main branch, not untrusted pull requests. What trust restriction….
C:Federated credentials exchange trusted external assertions for Entra tokens instead of persistent secrets. This matters here because an app needs a federated credential only for the main branch, not untrusted pull requests. What trust restriction….
D:Unattended application work needs a workload identity rather than a human session. This matters here because an app needs a federated credential only for the main branch, not untrusted pull requests. What trust restriction….
Question 379
An Azure managed identity can get an access token but cannot read a blob. Which role category is needed?
- Grant the appropriate resource write action through an Azure RBAC role.
- Remove the relevant downstream RBAC or resource permission assignment.
- Request tokens through the host's managed identity endpoint.
- Assign Storage Blob Data Reader at the permitted storage scope.
Explanation
Correct Answer
D:Azure Storage blob data permissions are independent of successful managed identity authentication. This matters here because an Azure managed identity can get an access token but cannot read a blob. Which role category is needed.
Incorrect Answers
A:The Azure Reader role does not permit resource creation or configuration updates. This matters here because an Azure managed identity can get an access token but cannot read a blob. Which role category is needed.
B:Authentication identity lifecycle can be separated from resource authorization grants. This matters here because an Azure managed identity can get an access token but cannot read a blob. Which role category is needed.
C:The platform brokers tokens without exposing a reusable password or certificate to the app. Azure Storage blob data permissions are independent of successful managed identity authentication.
Question 380
An app needs to write secrets into a Key Vault in Azure RBAC mode. What authorization must be granted?
- Assign Storage Blob Data Reader at the permitted storage scope.
- Create one user-assigned managed identity and attach it to the functions.
- Assign explicit Azure RBAC roles separately at each approved subscription or resource scope.
- Grant a suitable Key Vault secrets data role to the workload identity.
Explanation
Correct Answer
D:Key Vault secret modification requires explicit vault data-plane permission. This matters here because an app needs to write secrets into a Key Vault in Azure RBAC mode. What authorization must be granted.
Incorrect Answers
A:Azure Storage blob data permissions are independent of successful managed identity authentication. This matters here because an app needs to write secrets into a Key Vault in Azure RBAC mode. What authorization must be granted.
B:A user-assigned identity is a standalone Azure resource reusable by multiple supported compute resources. This matters here because an app needs to write secrets into a Key Vault in Azure RBAC mode. What authorization must be granted.
C:Resource-role assignments are scoped and do not travel automatically with a principal. This matters here because an app needs to write secrets into a Key Vault in Azure RBAC mode. What authorization must be granted.