Microsoft SC-300 Practice Test 46
Question 450
A developer needs a stable identifier for the application across environments. Which identifier is relevant?
- Match token issuer and audience to the app's configured supported account type.
- Register the app as single-tenant.
- Use the application's client or application ID.
- Assign the app role to the appropriate users, groups or service principals.
Explanation
Correct Answer
C:Client IDs identify the registered application in protocol requests. This matters here because a developer needs a stable identifier for the application across environments. Which identifier is relevant.
Incorrect Answers
A:Token validation must respect tenant trust instead of accepting arbitrary issuers.
B:Single-tenant audience restricts organizational identities to the home directory. This matters here because a developer needs a stable identifier for the application across environments. Which identifier is relevant.
D:Defining a role does not create assignments for every principal.
Question 451
An API validates the wrong tenant issuer for incoming tokens. What should be verified?
- Use application permissions with tenant admin consent as needed.
- Use the application's client or application ID.
- Use one suitable application registration with controlled service principal and user authorization.
- Match token issuer and audience to the app's configured supported account type.
Explanation
Correct Answer
D:Token validation must respect tenant trust rather than accepting arbitrary issuers. This matters here because an API validates the wrong tenant issuer for incoming tokens.
Incorrect Answers
A:Application permissions allow service principal actions without delegated user context.
B:Client IDs identify the registered application in protocol requests. This matters here because an API validates the wrong tenant issuer for incoming tokens.
C:A shared app definition supports many users without duplicating application identities. This matters here because an API validates the wrong tenant issuer for incoming tokens.
Question 452
A project accidentally creates separate app registrations for every user. What architecture should replace them?
- Use one suitable application registration with controlled service principal and user authorization.
- Register the app as single-tenant.
- Add and validate the replacement credential before removing the old one.
- Select the supported organizational-and-personal Microsoft account audience.
Explanation
Correct Answer
A:A shared app definition supports many users without duplicating application identities. This matters here because a project accidentally creates separate app registrations for every user. What architecture should replace them.
Incorrect Answers
B:Single-tenant audience restricts organizational identities to the home directory. This matters here because a project accidentally creates separate app registrations for every user. What architecture should replace them.
C:Overlapping credentials support uninterrupted rotation.
D:Supported account types define which identities may sign in. This matters here because a project accidentally creates separate app registrations for every user. What architecture should replace them.
Question 453
A multi-tenant app gains broad application permission in a customer tenant. Who authorizes it?
- Obtain admin consent within the customer resource tenant.
- Inventory and remove unused credentials after identifying dependent workloads.
- Establish a service principal in that tenant through supported consent or provisioning.
- Define the API's application ID URI and published scopes or roles.
Explanation
Correct Answer
A:Application permission consent is granted for the tenant-local service principal. This matters here because a multi-tenant app gains broad application permission in a customer tenant. Who authorizes it.
Incorrect Answers
B:Orphaned app credentials remain potential authentication entry points.
C:The app definition and a tenant-local enterprise application instance are different directory objects. This matters here because a multi-tenant app gains broad application permission in a customer tenant. Who authorizes it.
D:Exposing an API establishes the resource identifiers and permissions for callers.
Question 454
An app registration must expose a protected web API to external client applications. What configuration concept matters?
- Obtain admin consent within the customer resource tenant.
- Request an access token for Microsoft Graph instead of using an ID token.
- Define the API's application ID URI and published scopes or roles.
- Match token issuer and audience to the app's configured supported account type.
Explanation
Correct Answer
C:Exposing an API establishes the resource identifiers and permissions for callers. This matters here because an app registration must expose a protected web API to external client applications. What configuration concept matters.
Incorrect Answers
A:Application permission consent is granted for the tenant-local service principal. This matters here because an app registration must expose a protected web API to external client applications. What configuration concept matters.
B:ID tokens describe user authentication to the client, not API authorization for another resource. Exposing an API establishes the resource identifiers and permissions for callers.
D:Token validation must respect tenant trust rather than accepting arbitrary issuers. This matters here because an app registration must expose a protected web API to external client applications. What configuration concept matters.
Question 455
An enterprise app object appears after external admin consent but its credential configuration stays in the developer tenant. Why?
- Use delegated OAuth scopes rather than app-role application permissions.
- Distinguish the home-tenant app object from the tenant-local service principal.
- Establish a service principal in that tenant through supported consent or provisioning.
- Choose multitenant organizational directory accounts for the app.
Explanation
Correct Answer
B:Home application registrations own definitions while local service principals represent deployment instances.
Incorrect Answers
A:Delegated scopes describe what a client may do on behalf of the signed-in user. Home application registrations own definitions while local service principals represent deployment instances.
C:The app definition and a tenant-local enterprise application instance are different directory objects. Home application registrations own definitions while local service principals represent deployment instances.
D:Multitenant apps can create tenant-local service principals through consent. This matters here because an enterprise app object appears after external admin consent but its credential configuration stays in theā¦.
Question 456
A web app receives an invalid redirect_uri error after authentication. What registration property must be corrected?
- Remove the secret and redesign with a public-client flow or protected backend.
- Use an appropriate managed identity for the Azure-hosted workload.
- Register the exact redirect URI for the appropriate platform.
- Use client credentials with application permissions.
Explanation
Correct Answer
C:OAuth redirect URIs must match approved application callbacks.
Incorrect Answers
A:Browser-distributed code cannot keep client secrets confidential.
B:Managed identities avoid manual credential maintenance for supported services.
D:Daemon apps use workload-only tokens instead of delegated authorization.
Question 457
A browser-based single-page application needs users to sign in securely and call a protected API. Which THREE registration decisions avoid exposing a reusable secret? (Select THREE.)
- Use the ID token as the downstream API authorization token.
- Request a resource-specific API access token using approved delegated scopes.
- Use authorization code flow with PKCE as a public client.
- Configure the application with an SPA platform redirect URI.
- Allow arbitrary unregistered redirect URIs in production.
- Embed a confidential client secret in shipped JavaScript.
Explanation
Correct Answers
B:The API requires a token for its own audience and delegated authorization.
C:PKCE protects the code exchange without requiring a browser-held confidential client secret.
D:The registration must recognize the browser-based client callback.
Incorrect Answers
A:An ID token authenticates the user to the client but is not the intended API access token.
E:Unrestricted callbacks undermine authorization-code flow protection.
F:Browser-delivered code cannot protect reusable client credentials.
Question 458
A backend web application needs to acquire tokens securely in authorization code flow. What credential design fits?
- Use one suitable application registration with controlled service principal and user authorization.
- Configure SPA redirect URIs and authorization code flow with PKCE.
- Register the exact HTTPS callback URL and remove obsolete redirects after testing.
- Use confidential client authentication with certificate or approved secret.
Explanation
Correct Answer
D:Server-side confidential clients can protect credentials during token exchange.
Incorrect Answers
A:A shared app definition supports many users without duplicating application identities. This matters here because a backend web application needs to acquire tokens securely in authorization code flow. What credential design fits.
B:SPAs use public-client flows rather than embedding confidential secrets.
C:The identity platform compares the response address to configured redirect URIs.
Question 459
A single-page application uses browser code and wants modern sign-in. Which redirect type and flow matter?
- Configure SPA redirect URIs and authorization code flow with PKCE.
- Register the exact HTTPS callback URL and remove obsolete redirects after testing.
- Use client credentials with application permissions.
- Use one suitable application registration with controlled service principal and user authorization.
Explanation
Correct Answer
A:SPAs use public-client flows instead of embedding confidential secrets.
Incorrect Answers
B:The identity platform compares the response address to configured redirect URIs. This matters here because a single-page application uses browser code and wants modern sign-in. Which redirect type and flow matter.
C:Daemon apps use workload-only tokens rather than delegated authorization. This matters here because a single-page application uses browser code and wants modern sign-in. Which redirect type and flow matter.
D:A shared app definition supports many users without duplicating application identities. This matters here because a single-page application uses browser code and wants modern sign-in. Which redirect type and flow matter.
Question 460
A redirect URI changes from HTTP to HTTPS in production and sign-in starts failing. What should be updated?
- Configure a public client platform and supported PKCE authorization code flow.
- Use a service principal with approved application permissions.
- Register the exact HTTPS callback URL and remove obsolete redirects after testing.
- Use confidential client authentication with certificate or approved secret.
Explanation
Correct Answer
C:The identity platform compares the response address to configured redirect URIs. This matters here because a redirect URI changes from HTTP to HTTPS in production and sign-in starts failing.
Incorrect Answers
A:Native apps cannot safely protect a reusable client secret.
B:An unattended job must not depend on an employee's delegated token.
D:Server-side confidential clients can protect credentials during token exchange. This matters here because a redirect URI changes from HTTP to HTTPS in production and sign-in starts failing.