Microsoft SC-300 Practice Test 40
Question 390
A team plans to replace a gMSA with a shared ordinary user account whose password never expires. What security tradeoff applies?
- Replace delegated user tokens with a managed identity or service principal as appropriate.
- Retain managed service credentials or adopt a supported workload identity rather than unmanaged shared passwords.
- Choose a supported on-premises managed service account or compatible identity mechanism.
- Use a group managed service account where the service supports it.
Explanation
Correct Answer
B:Unmanaged shared service passwords increase credential exposure and manual rotation risk. This matters here because a team plans to replace a gMSA with a shared ordinary user account whose password never expires. What security….
Incorrect Answers
A:Unattended application work needs a workload identity rather than a human session. This matters here because a team plans to replace a gMSA with a shared ordinary user account whose password never expires. What security….
C:Azure managed identity endpoints are not universally available to arbitrary on-premises services. This matters here because a team plans to replace a gMSA with a shared ordinary user account whose password never expires. What security….
D:GMSAs provide locally managed domain service credentials with automatic password management. This matters here because a team plans to replace a gMSA with a shared ordinary user account whose password never expires. What security….
Question 391
A SaaS provider sends a SAML metadata document for workforce sign-in. Which Entra integration should be configured?
- Configure Microsoft Entra preauthentication for the Application Proxy app.
- Create the enterprise application SAML-based single sign-on connection.
- Configure OIDC or OpenID Connect sign-in with registered redirect URIs.
- Use supported password-based SSO for that enterprise app where appropriate.
Explanation
Correct Answer
B:SAML enterprise app configuration manages trust, reply URL and assertion signing information.
Incorrect Answers
A:Entra preauthentication supports Conditional Access before passing users to the backend.
C:OIDC code flow uses registered callbacks and token claims rather than SAML assertions. SAML enterprise app configuration manages trust, reply URL and assertion signing information.
D:Application compatibility determines which SSO method is available.
Question 392
A vendor app redirects users back with an OIDC authorization code. Which protocol-specific setup matters?
- Check consent and API permissions independently of user assignment.
- Use supported password-based SSO for that enterprise app where appropriate.
- Review SAML claims mapping and NameID source attribute.
- Configure OIDC or OpenID Connect sign-in with registered redirect URIs.
Explanation
Correct Answer
D:OIDC code flow uses registered callbacks and token claims rather than SAML assertions.
Incorrect Answers
A:Assignment to a front-end app does not automatically grant the app its downstream API scopes. OIDC code flow uses registered callbacks and token claims rather than SAML assertions.
B:Application compatibility determines which SSO method is available. This matters here because a vendor app redirects users back with an OIDC authorization code. Which protocol-specific setup matters.
C:The app may require an immutable or expected identifier different from the user's display name. OIDC code flow uses registered callbacks and token claims rather than SAML assertions.
Question 393
A SAML app rejects the response with audience mismatch. What claim must be checked?
- Use supported password-based SSO for that enterprise app where appropriate.
- Match the SAML entity ID or audience to the service provider's expected identifier.
- Set up SAML SSO and verify the identity-provider initiation behavior supported by the app.
- Configure application provisioning in addition to SSO.
Explanation
Correct Answer
B:The relying party validates assertion audience against its configured application identity.
Incorrect Answers
A:Application compatibility determines which SSO method is available. This matters here because a SAML app rejects the response with audience mismatch. What claim must be checked.
C:SAML can support identity-provider-initiated sign-in where the service provider allows it.
D:Authentication federation does not automatically create accounts unless provisioning is configured.
Question 394
Users sign in to a SaaS app but land on the wrong callback endpoint. Which enterprise SSO property should be checked?
- Update the trusted SAML signing certificate or metadata.
- Configure Microsoft Entra preauthentication for the Application Proxy app.
- Correct the approved reply or redirect URL.
- Treat the app registration as the definition and the service principal as the tenant instance.
Explanation
Correct Answer
C:The application's callback must match the endpoint registered with the identity provider.
Incorrect Answers
A:Service providers validate signatures using the expected issuer key material.
B:Entra preauthentication supports Conditional Access before passing users to the backend. This matters here because users sign in to a SaaS app but land on the wrong callback endpoint. Which enterprise SSO property should be checked.
D:Application objects and enterprise service principals have different lifecycle and tenant roles.
Question 395
A SAML assertion is rejected after signing-certificate rollover. Which federation artifact needs maintenance?
- Match the SAML entity ID or audience to the service provider's expected identifier.
- Check application user or group assignment separately.
- Update the trusted SAML signing certificate or metadata.
- Assign the enterprise app and check its user visibility settings.
Explanation
Correct Answer
C:Service providers validate signatures using the expected issuer key material. This matters here because a SAML assertion is rejected after signing-certificate rollover. Which federation artifact needs maintenance.
Incorrect Answers
A:The relying party validates assertion audience against its configured application identity. This matters here because a SAML assertion is rejected after signing-certificate rollover. Which federation artifact needs maintenance.
B:Tenant admin consent grants API scope, not necessarily end-user enterprise app access.
D:My Apps access reflects app assignments and end-user visibility.
Question 396
A company wants IdP-initiated SSO to a supported SAML app. Which configuration should be tested?
- Assign the user or approved group to the enterprise application.
- Use supported password-based SSO for that enterprise app where appropriate.
- Check application user or group assignment separately.
- Set up SAML SSO and verify the identity-provider initiation behavior supported by the app.
Explanation
Correct Answer
D:SAML can support identity-provider-initiated sign-in where the service provider allows it. This matters here because a company wants IdP-initiated SSO to a supported SAML app. Which configuration should be tested.
Incorrect Answers
A:Successful sign-in does not satisfy an app's required user assignment policy.
B:Application compatibility determines which SSO method is available. This matters here because a company wants IdP-initiated SSO to a supported SAML app. Which configuration should be tested.
C:Tenant admin consent grants API scope, not necessarily end-user enterprise app access. This matters here because a company wants IdP-initiated SSO to a supported SAML app. Which configuration should be tested.
Question 397
An enterprise is onboarding a SAML SaaS application. Employees must authenticate using Entra, and only approved groups may launch it. Which TWO configurations are needed? (Select TWO.)
- Store employees’ Entra passwords in the SaaS application.
- Require application assignment and assign approved groups to the enterprise app.
- Configure SAML single sign-on with correct application entity ID and reply URL.
- Assume successful Entra login grants every user all SaaS app roles.
- Disable SAML assertion signature verification at the service provider.
Explanation
Correct Answers
B:App assignments limit who can access the application despite valid directory sign-in.
C:The SAML trust and callback configuration enable federated authentication.
Incorrect Answers
A:Federation does not require disclosing workforce passwords to the SaaS.
D:Authentication is separate from enterprise application authorization.
E:Trust validation must be preserved for secure federated SSO.
Question 398
A user can sign in to Entra but sees an enterprise application deny access because assignment is required. What should be changed?
- Assign the user or approved group to the enterprise application.
- Use supported password-based SSO for that enterprise app where appropriate.
- Grant the Enterprise Application Administrator role tenant-wide to the denied end user.
- Configure OIDC or OpenID Connect sign-in with registered redirect URIs.
Explanation
Correct Answer
A:Successful sign-in does not satisfy an app's required user assignment policy. This matters here because a user can sign in to Entra but sees an enterprise application deny access because assignment is required.
Incorrect Answers
B:Application compatibility determines which SSO method is available. This matters here because a user can sign in to Entra but sees an enterprise application deny access because assignment is required.
C:Application administration permits managing app objects and does not grant the application assignment required for sign-in; it also needlessly increases privilege.
D:OIDC code flow uses registered callbacks and token claims instead of SAML assertions.
Question 399
An SSO rollout must use an existing external IdP without copying employee passwords into the SaaS. What identity model fits?
- Configure federation between Entra and the SaaS using a supported protocol.
- Require supported publisher verification or approved app conditions in user consent policy.
- Review SAML claims mapping and NameID source attribute.
- Create the enterprise application SAML-based single sign-on connection.
Explanation
Correct Answer
A:Federation exchanges signed identity assertions or tokens rather than disclosing directory passwords.
Incorrect Answers
B:Verified publisher metadata is one input to safer user-consent governance.
C:The app may require an immutable or expected identifier different from the user's display name. Federation exchanges signed identity assertions or tokens rather than disclosing directory passwords.
D:SAML enterprise app configuration manages trust, reply URL and assertion signing information. This matters here because an SSO rollout must use an existing external IdP without copying employee passwords into the SaaS. What identity….
Question 400
A cloud app only supports password-based single sign-on rather than SAML. Which alternative should be evaluated?
- Use supported password-based SSO for that enterprise app where appropriate.
- Select Sync only assigned users and groups when supported.
- Assign the enterprise app and check its user visibility settings.
- Review SAML claims mapping and NameID source attribute.
Explanation
Correct Answer
A:Application compatibility determines which SSO method is available. This matters here because a cloud app only supports password-based single sign-on rather than SAML. Which alternative should be evaluated.
Incorrect Answers
B:Provisioning scope can be restricted to app assignment rather than all directory users.
C:My Apps access reflects app assignments and end-user visibility. This matters here because a cloud app only supports password-based single sign-on rather than SAML. Which alternative should be evaluated.
D:The app may require an immutable or expected identifier different from the user's display name.