Microsoft SC-300 Practice Test 44
Question 430
A SaaS app requests Directory.ReadWrite.All application permission. What review is required before granting?
- Require privileged admin consent after reviewing the necessity of the high-impact permission.
- Verify current tenant context and service principal before granting admin consent.
- Assign the group to the Reader app role in the enterprise application.
- Configure user consent policy for verified publishers and selected low-risk scopes.
Explanation
Correct Answer
A:Tenant-wide application permissions can access directory data without a signed-in user.
Incorrect Answers
B:Admin consent acts on the current tenant's application instance and permission grants. This matters here because a SaaS app requests Directory.ReadWrite.All application permission. What review is required before granting.
C:App role assignments express application privileges for the selected principals. This matters here because a SaaS app requests Directory.ReadWrite.All application permission. What review is required before granting.
D:User consent can be limited to permissions meeting a defined risk threshold. This matters here because a SaaS app requests Directory.ReadWrite.All application permission. What review is required before granting.
Question 431
A user approves an app requesting only approved low-risk delegated scopes. What policy permits this?
- Configure user consent policy for verified publishers and selected low-risk scopes.
- Inspect existing OAuth2 permission grants and app-role assignments.
- Review the provisioning attribute mapping for jobTitle.
- Revoke unnecessary grants and investigate the consenting user and application.
Explanation
Correct Answer
A:User consent can be limited to permissions meeting a defined risk threshold. This matters here because a user approves an app requesting only approved low-risk delegated scopes. What policy permits this.
Incorrect Answers
B:Requested permissions and previously issued consent grants are separate records.
C:Attribute mappings determine which source properties are synchronized to the app. This matters here because a user approves an app requesting only approved low-risk delegated scopes. What policy permits this.
D:OAuth grants can persist as app authorization even after a user stops interacting with the app. User consent can be limited to permissions meeting a defined risk threshold.
Question 432
A developer sees Need admin approval after requesting a restricted API permission. What workflow should be configured?
- Match the SAML entity ID or audience to the service provider's expected identifier.
- Check application user or group assignment separately.
- Revoke unnecessary grants and investigate the consenting user and application.
- Use the administrator consent request workflow.
Explanation
Correct Answer
D:Admin consent workflow routes high-privilege requests for authorized review. This matters here because a developer sees Need admin approval after requesting a restricted API permission. What workflow should be configured.
Incorrect Answers
A:The relying party validates assertion audience against its configured application identity. This matters here because a developer sees Need admin approval after requesting a restricted API permission. What workflow should be configured.
B:Tenant admin consent grants API scope, not necessarily end-user enterprise app access. This matters here because a developer sees Need admin approval after requesting a restricted API permission. What workflow should be configured.
C:OAuth grants can persist as app authorization even after a user stops interacting with the app. Admin consent workflow routes high-privilege requests for authorized review.
Question 433
An enterprise app has admin consent for Graph but users still cannot launch it. What different requirement might be missing?
- Check application user or group assignment separately.
- Deploy multiple healthy connectors in a connector group.
- Revoke unnecessary grants and investigate the consenting user and application.
- Use the administrator consent request workflow.
Explanation
Correct Answer
A:Tenant admin consent grants API scope, not necessarily end-user enterprise app access. This matters here because an enterprise app has admin consent for Graph but users still cannot launch it. What different requirement might be….
Incorrect Answers
B:Connector redundancy avoids single-server dependence for published applications. This matters here because an enterprise app has admin consent for Graph but users still cannot launch it. What different requirement might be….
C:OAuth grants can persist as app authorization even after a user stops interacting with the app. Tenant admin consent grants API scope, not necessarily end-user enterprise app access.
D:Admin consent workflow routes high-privilege requests for authorized review. This matters here because an enterprise app has admin consent for Graph but users still cannot launch it. What different requirement might be….
Question 434
A security team wants to restrict OAuth consent to apps verified by a publisher. Which setting is relevant?
- Check application user or group assignment separately.
- Update the trusted SAML signing certificate or metadata.
- Require supported publisher verification or approved app conditions in user consent policy.
- Review effective user-consent policy and the complete requested scope set.
Explanation
Correct Answer
C:Verified publisher metadata is one input to safer user-consent governance. This matters here because a security team wants to restrict OAuth consent to apps verified by a publisher. Which setting is relevant.
Incorrect Answers
A:Tenant admin consent grants API scope, not necessarily end-user enterprise app access. This matters here because a security team wants to restrict OAuth consent to apps verified by a publisher. Which setting is relevant.
B:Service providers validate signatures using the expected issuer key material. This matters here because a security team wants to restrict OAuth consent to apps verified by a publisher. Which setting is relevant.
D:The full permission request and tenant policy determine whether admin consent is required.
Question 435
An engineer removes an app's API permission request but a consent grant persists. What object should be audited?
- Require privileged admin consent after reviewing the necessity of the high-impact permission.
- Check application user or group assignment separately.
- Assign the group to the Reader app role in the enterprise application.
- Inspect existing OAuth2 permission grants and app-role assignments.
Explanation
Correct Answer
D:Requested permissions and previously issued consent grants are separate records. This matters here because an engineer removes an app's API permission request but a consent grant persists. What object should be audited.
Incorrect Answers
A:Tenant-wide application permissions can access directory data without a signed-in user. This matters here because an engineer removes an app's API permission request but a consent grant persists. What object should be audited.
B:Tenant admin consent grants API scope, not necessarily end-user enterprise app access. This matters here because an engineer removes an app's API permission request but a consent grant persists. What object should be audited.
C:App role assignments express application privileges for the selected principals. This matters here because an engineer removes an app's API permission request but a consent grant persists. What object should be audited.
Question 436
A consent request is approved for the wrong tenant. What should be checked?
- Verify current tenant context and service principal before granting admin consent.
- Check application user or group assignment separately.
- Inspect detailed provisioning logs for the affected object and mapping step.
- Configure user consent policy for verified publishers and selected low-risk scopes.
Explanation
Correct Answer
A:Admin consent acts on the current tenant's application instance and permission grants. This matters here because a consent request is approved for the wrong tenant.
Incorrect Answers
B:Tenant admin consent grants API scope, not necessarily end-user enterprise app access. This matters here because a consent request is approved for the wrong tenant.
C:Provisioning logs reveal matching, transformation and downstream API errors. This matters here because a consent request is approved for the wrong tenant.
D:User consent can be limited to permissions meeting a defined risk threshold. This matters here because a consent request is approved for the wrong tenant.
Question 437
A SaaS vendor claims admin consent is needed for User.Read only, but your policy allows low-risk consent. What should be evaluated?
- Remove the contractor's enterprise app assignment or governing group membership.
- Review effective user-consent policy and the complete requested scope set.
- Require privileged admin consent after reviewing the necessity of the high-impact permission.
- Check application user or group assignment separately.
Explanation
Correct Answer
B:The full permission request and tenant policy determine whether admin consent is required. This matters here because a SaaS vendor claims admin consent is needed for User.Read only, but your policy allows low-risk consent.
Incorrect Answers
A:Application authorization can be revoked without deleting the shared service principal. This matters here because a SaaS vendor claims admin consent is needed for User.Read only, but your policy allows low-risk consent.
C:Tenant-wide application permissions can access directory data without a signed-in user. This matters here because a SaaS vendor claims admin consent is needed for User.Read only, but your policy allows low-risk consent.
D:Tenant admin consent grants API scope, not necessarily end-user enterprise app access. The full permission request and tenant policy determine whether admin consent is required.
Question 438
A suspicious OAuth app receives unusually broad delegated permissions. What immediate governance action helps?
- Inspect existing OAuth2 permission grants and app-role assignments.
- Revoke unnecessary grants and investigate the consenting user and application.
- Require privileged admin consent after reviewing the necessity of the high-impact permission.
- Assign the application owner role to the approved person.
Explanation
Correct Answer
B:OAuth grants can persist as app authorization even after a user stops interacting with the app.
Incorrect Answers
A:Requested permissions and previously issued consent grants are separate records. OAuth grants can persist as app authorization even after a user stops interacting with the app.
C:Tenant-wide application permissions can access directory data without a signed-in user. OAuth grants can persist as app authorization even after a user stops interacting with the app.
D:Application ownership delegates management of that app without tenant-wide administrator role grants. OAuth grants can persist as app authorization even after a user stops interacting with the app.
Question 439
An organization wants to group related enterprise apps in a single end-user view. What feature should it use?
- Review application collection membership and classification.
- Configure Kerberos constrained delegation for the supported app and connector.
- Create an enterprise application collection and include the approved apps.
- Verify its assignment, visibility and membership in the collection.
Explanation
Correct Answer
C:Application collections organize related apps for discoverability and management. This matters here because an organization wants to group related enterprise apps in a single end-user view. What feature should it use.
Incorrect Answers
A:Collections can be curated without changing each app's OAuth API permissions.
B:KCD can translate cloud identity authentication into supported backend Windows authentication. This matters here because an organization wants to group related enterprise apps in a single end-user view. What feature should it use.
D:End-user presentation depends on both organization and actual access. This matters here because an organization wants to group related enterprise apps in a single end-user view. What feature should it use.
Question 440
A user complains two unrelated apps are mixed in one collection. What should be changed?
- Review application collection membership and classification.
- Update the Application Proxy internal URL and connection configuration.
- Enforce enterprise app assignments and Conditional Access independently of collections.
- Update the collection definitions and membership grouping.
Explanation
Correct Answer
A:Collections can be curated without changing each app's OAuth API permissions. This matters here because a user complains two unrelated apps are mixed in one collection.
Incorrect Answers
B:The connector's internal target must reflect the app's reachable backend. This matters here because a user complains two unrelated apps are mixed in one collection.
C:Collections do not replace tenant authentication and authorization controls.
D:App grouping is a presentation and organization mechanism.