Microsoft SC-300 Practice Test 49
Question 480
A resource API checks only whether a token is signed but ignores audience. What validation must be added?
- Validate the roles claim for approved application app roles.
- Use statically consented permissions configured for the requested resource.
- Validate issuer, audience and required scopes or roles.
- Require authorized administrator consent for the high-privilege application roles.
Explanation
Correct Answer
C:A valid token for another API must not grant access to a separate resource.
Incorrect Answers
A:App-only authorizations are typically represented as assigned roles. This matters here because a resource API checks only whether a token is signed but ignores audience. What validation must be added.
B:The.default scope resolves preconfigured permissions rather than requesting arbitrary new scopes interactively. A valid token for another API must not grant access to an unrelated resource.
D:Tenant application-role grants are privileged authorizations. This matters here because a resource API checks only whether a token is signed but ignores audience. What validation must be added.
Question 481
An administrator wants app roles visible in application tokens for group authorization. What should be configured?
- Define and assign the intended app roles with allowed member types.
- Choose the minimum Graph permissions supported for that group operation.
- Register the exact redirect URI for the appropriate platform.
- Verify the token's approved scopes or app roles in addition to membership.
Explanation
Correct Answer
A:Roles must be exposed on the resource application and assigned to principals. This matters here because an administrator wants app roles visible in application tokens for group authorization.
Incorrect Answers
B:Avoid broader Directory.ReadWrite.All grants when more restrictive permissions meet requirements. This matters here because an administrator wants app roles visible in application tokens for group authorization.
C:OAuth redirect URIs must match approved application callbacks. This matters here because an administrator wants app roles visible in application tokens for group authorization.
D:Group membership context is not a substitute for API action authorization. This matters here because an administrator wants app roles visible in application tokens for group authorization.
Question 482
A client requests a resource-specific scope through .default during service principal auth. What does the request rely on?
- Set allowed member types for users, applications or both as intended.
- Define an application app role for service principal access.
- Establish a service principal in that tenant through supported consent or provisioning.
- Use statically consented permissions configured for the requested resource.
Explanation
Correct Answer
D:The.default scope resolves preconfigured permissions rather than requesting arbitrary new scopes interactively. This matters here because a client requests a resource-specific scope through .default during service principal auth. What does the request….
Incorrect Answers
A:App role definitions specify which principal categories may receive each permission. This matters here because a client requests a resource-specific scope through .default during service principal auth. What does the request….
B:Application app roles authorize workload-only API calls. This matters here because a client requests a resource-specific scope through .default during service principal auth. What does the request….
C:The app definition and a tenant-local enterprise application instance are different directory objects. The.default scope resolves preconfigured permissions rather than requesting arbitrary new scopes interactively.
Question 483
A token contains an expected group claim but lacks the API permission required for write operations. What should be checked?
- Verify the token's approved scopes or app roles in addition to membership.
- Set allowed member types for users, applications or both as intended.
- Assign the app role to the appropriate users, groups or service principals.
- Use application permissions with tenant admin consent as needed.
Explanation
Correct Answer
A:Group membership context is not a substitute for API action authorization. This matters here because a token contains an expected group claim but lacks the API permission required for write operations.
Incorrect Answers
B:App role definitions specify which principal categories may receive each permission. This matters here because a token contains an expected group claim but lacks the API permission required for write operations.
C:Defining a role does not create assignments for every principal. This matters here because a token contains an expected group claim but lacks the API permission required for write operations.
D:Application permissions allow service principal actions without delegated user context. This matters here because a token contains an expected group claim but lacks the API permission required for write operations.
Question 484
A multi-tenant API wants different roles for application-only and user principals. Which app-role property matters?
- Use statically consented permissions configured for the requested resource.
- Request an access token for Microsoft Graph instead of using an ID token.
- Set allowed member types for users, applications or both as intended.
- Validate issuer, audience and required scopes or roles.
Explanation
Correct Answer
C:App role definitions specify which principal categories may receive each permission. This matters here because a multi-tenant API wants different roles for application-only and user principals. Which app-role property matters.
Incorrect Answers
A:The.default scope resolves preconfigured permissions rather than requesting arbitrary new scopes interactively. This matters here because a multi-tenant API wants different roles for application-only and user principals. Which app-role property matters.
B:ID tokens describe user authentication to the client, not API authorization for another resource. App role definitions specify which principal categories may receive each permission.
D:A valid token for another API must not grant access to an unrelated resource. App role definitions specify which principal categories may receive each permission.
Question 485
An app uses a two-year secret stored in a plaintext code repository. What credential design improves security?
- Use an appropriate managed identity for the Azure-hosted workload.
- Track application credential expiry and establish tested rotation ownership.
- Use statically consented permissions configured for the requested resource.
- Replace leaked secrets with a certificate or workload federation and secure credential storage.
Explanation
Correct Answer
D:Application secrets embedded in source code can be copied and are difficult to rotate safely. This matters here because an app uses a two-year secret stored in a plaintext code repository. What credential design improves security.
Incorrect Answers
A:Managed identities avoid manual credential maintenance for supported services. This matters here because an app uses a two-year secret stored in a plaintext code repository. What credential design improves security.
B:Credentials require lifecycle monitoring regardless of their initial creation. This matters here because an app uses a two-year secret stored in a plaintext code repository. What credential design improves security.
C:The.default scope resolves preconfigured permissions rather than requesting arbitrary new scopes interactively. Application secrets embedded in source code can be copied and are difficult to rotate safely.
Question 486
An application certificate is expiring during a production rollout. What should admins do first?
- Use an appropriate managed identity for the Azure-hosted workload.
- Replace leaked secrets with a certificate or workload federation and secure credential storage.
- Use delegated OAuth scopes rather than app-role application permissions.
- Add and validate the replacement credential before removing the old one.
Explanation
Correct Answer
D:Overlapping credentials support uninterrupted rotation. This matters here because an application certificate is expiring during a production rollout.
Incorrect Answers
A:Managed identities avoid manual credential maintenance for supported services. This matters here because an application certificate is expiring during a production rollout.
B:Application secrets embedded in source code can be copied and are difficult to rotate safely. This matters here because an application certificate is expiring during a production rollout.
C:Delegated scopes describe what a client may do on behalf of the signed-in user. This matters here because an application certificate is expiring during a production rollout.
Question 487
A service principal has multiple unused client secrets from departed teams. What cleanup is needed?
- Inventory and remove unused credentials after identifying dependent workloads.
- Add and validate the replacement credential before removing the old one.
- Verify the token's approved scopes or app roles in addition to membership.
- Use an appropriate managed identity for the Azure-hosted workload.
Explanation
Correct Answer
A:Orphaned app credentials remain potential authentication entry points. This matters here because a service principal has multiple unused client secrets from departed teams. What cleanup is needed.
Incorrect Answers
B:Overlapping credentials support uninterrupted rotation. This matters here because a service principal has multiple unused client secrets from departed teams. What cleanup is needed.
C:Group membership context is not a substitute for API action authorization. This matters here because a service principal has multiple unused client secrets from departed teams. What cleanup is needed.
D:Managed identities avoid manual credential maintenance for supported services. This matters here because a service principal has multiple unused client secrets from departed teams. What cleanup is needed.
Question 488
An Azure-hosted service keeps a client secret only to reach another Azure resource. What alternative is preferable?
- Define and assign the intended app roles with allowed member types.
- Use an appropriate managed identity for the Azure-hosted workload.
- Configure a federated credential bound to the external workload identity.
- Inventory and remove unused credentials after identifying dependent workloads.
Explanation
Correct Answer
B:Managed identities avoid manual credential maintenance for supported services. This matters here because an Azure-hosted service keeps a client secret only to reach another Azure resource. What alternative is preferable.
Incorrect Answers
A:Roles must be exposed on the resource application and assigned to principals. This matters here because an Azure-hosted service keeps a client secret only to reach another Azure resource. What alternative is preferable.
C:Workload identity federation exchanges trusted assertions instead of presenting a long-lived local key.
D:Orphaned app credentials remain potential authentication entry points. This matters here because an Azure-hosted service keeps a client secret only to reach another Azure resource. What alternative is preferable.
Question 489
A pipeline outside Azure supports OIDC federation. What eliminates the stored service principal certificate?
- Use an appropriate managed identity for the Azure-hosted workload.
- Choose multitenant organizational directory accounts for the app.
- Configure a federated credential bound to the external workload identity.
- Inventory and remove unused credentials after identifying dependent workloads.
Explanation
Correct Answer
C:Workload identity federation exchanges trusted assertions rather than presenting a long-lived local key. This matters here because a pipeline outside Azure supports OIDC federation. What eliminates the stored service principal certificate.
Incorrect Answers
A:Managed identities avoid manual credential maintenance for supported services. This matters here because a pipeline outside Azure supports OIDC federation. What eliminates the stored service principal certificate.
B:Multitenant apps can create tenant-local service principals through consent. This matters here because a pipeline outside Azure supports OIDC federation. What eliminates the stored service principal certificate.
D:Orphaned app credentials remain potential authentication entry points. This matters here because a pipeline outside Azure supports OIDC federation. What eliminates the stored service principal certificate.
Question 490
A token issuance incident follows secret expiry. What preventive evidence should be monitored?
- Replace leaked secrets with a certificate or workload federation and secure credential storage.
- Add and validate the replacement credential before removing the old one.
- Check delegated scopes through the scp claim.
- Track application credential expiry and establish tested rotation ownership.
Explanation
Correct Answer
D:Credentials require lifecycle monitoring regardless of their initial creation. This matters here because a token issuance incident follows secret expiry. What preventive evidence should be monitored.
Incorrect Answers
A:Application secrets embedded in source code can be copied and are difficult to rotate safely. This matters here because a token issuance incident follows secret expiry. What preventive evidence should be monitored.
B:Overlapping credentials support uninterrupted rotation. This matters here because a token issuance incident follows secret expiry. What preventive evidence should be monitored.
C:Delegated access tokens generally carry OAuth scope grants in scp. This matters here because a token issuance incident follows secret expiry. What preventive evidence should be monitored.