Microsoft SC-300 Practice Test 56
Question 550
A company's connected organization was added with a broad consumer domain by mistake. What should be corrected?
- Add the supplier as a connected organization for entitlement management.
- Replace the broad domain with the intended trusted partner identity domain.
- Review and revoke retained access package assignments based on lifecycle policy.
- Create a dedicated finance catalog with scoped ownership and resources.
Explanation
Correct Answer
B:An overly broad connected organization can expose request eligibility to unrelated people. This matters here because a company's connected organization was added with a broad consumer domain by mistake.
Incorrect Answers
A:Connected organizations model eligible external partner populations for requests. This matters here because a company's connected organization was added with a broad consumer domain by mistake.
C:Request-eligibility changes may not instantly revoke already granted external access. This matters here because a company's connected organization was added with a broad consumer domain by mistake.
D:Business-aligned catalog boundaries simplify delegated entitlement governance. This matters here because a company's connected organization was added with a broad consumer domain by mistake.
Question 551
A package allows users from all connected organizations when only one department should be eligible. What policy edit fits?
- Select only the specified connected organizations.
- Restrict requester eligibility to the approved connected organization and groups where supported.
- Do not create an approved assignment for that denied request.
- Add the supplier as a connected organization for entitlement management.
Explanation
Correct Answer
B:External package policies must target the actual authorized partner population. This matters here because a package allows users from all connected organizations when only one department should be eligible. What policy….
Incorrect Answers
A:Connected organization targeting narrows which outside users may request access. This matters here because a package allows users from all connected organizations when only one department should be eligible. What policy….
C:Denied requests must not grant access to packaged resources. This matters here because a package allows users from all connected organizations when only one department should be eligible. What policy….
D:Connected organizations model eligible external partner populations for requests. This matters here because a package allows users from all connected organizations when only one department should be eligible. What policy….
Question 552
A guest is already an invited B2B user but cannot request a package for another partner. Which boundary must be checked?
- Use entitlement management external user lifecycle removal settings.
- Review connected organization membership and the access package's request policy.
- Select only the specified connected organizations.
- Add the supplier as a connected organization for entitlement management.
Explanation
Correct Answer
B:Being a guest in a tenant does not automatically satisfy external entitlement request eligibility. This matters here because a guest is already an invited B2B user but cannot request a package for another partner. Which boundary must be checked.
Incorrect Answers
A:External user lifecycle policies can delete or block guests after access ends. Being a guest in a tenant does not automatically satisfy external entitlement request eligibility.
C:Connected organization targeting narrows which outside users may request access. This matters here because a guest is already an invited B2B user but cannot request a package for another partner. Which boundary must be checked.
D:Connected organizations model eligible external partner populations for requests. This matters here because a guest is already an invited B2B user but cannot request a package for another partner. Which boundary must be checked.
Question 553
An external consultant receives an access package for a six-week engagement. What happens at configured expiration?
- Use entitlement management external user lifecycle removal settings.
- Set finite access package assignment duration with no unrestricted renewal.
- Expire the access package assignment and remove its governed resource access.
- Review all direct and indirect resource grants before deleting the guest.
Explanation
Correct Answer
C:Entitlement expiry provides automatic access lifecycle control. This matters here because an external consultant receives an access package for a six-week engagement. What happens at configured expiration.
Incorrect Answers
A:External user lifecycle policies can delete or block guests after access ends.
B:Time-bounded grants reduce lingering supplier access.
D:Package-based lifecycle does not substitute for auditing unrelated assignments.
Question 554
A guest has no remaining access package assignments and has been inactive for the configured retention period. What feature may clean up the identity?
- Restrict catalog resource ownership and addition privileges.
- Separate expiration of package access from removal of the guest directory identity.
- Set finite access package assignment duration with no unrestricted renewal.
- Use entitlement management external user lifecycle removal settings.
Explanation
Correct Answer
D:External user lifecycle policies can delete or block guests after access ends. This matters here because a guest has no remaining access package assignments and has been inactive for the configured retention period. What….
Incorrect Answers
A:Catalog owner roles govern which administrators can attach resources. This matters here because a guest has no remaining access package assignments and has been inactive for the configured retention period. What….
B:Revoking resource grants does not always delete the guest object immediately.
C:Time-bounded grants reduce lingering supplier access. This matters here because a guest has no remaining access package assignments and has been inactive for the configured retention period. What….
Question 555
A partner employee switches departments but retains an old entitlement package. What recurring control helps?
- Inspect downstream provisioning and deprovisioning logs.
- Use assignment expiration or access reviews to revalidate need.
- Remove the supplier's active package assignment and downstream resource access.
- Configure sponsor-based approval in the package request policy.
Explanation
Correct Answer
B:Temporary partner access should be periodically justified. This matters here because a partner employee switches departments but retains an old entitlement package. What recurring control helps.
Incorrect Answers
A:Access package revocation may require a connector's provisioning cycle to reach the target app.
C:Contract termination should not wait for a scheduled expiry date.
D:Approval policies can route decisions to identified business sponsors.
Question 556
An external package must automatically end when the business engagement finishes. What lifecycle setting is relevant?
- Restrict the package request policy to the intended internal user group.
- Set finite access package assignment duration with no unrestricted renewal.
- Use entitlement management external user lifecycle removal settings.
- Separate expiration of package access from removal of the guest directory identity.
Explanation
Correct Answer
B:Time-bounded grants reduce lingering supplier access. This matters here because an external package must automatically end when the business engagement finishes. What lifecycle setting is relevant.
Incorrect Answers
A:Eligibility scope determines who can request the package. This matters here because an external package must automatically end when the business engagement finishes. What lifecycle setting is relevant.
C:External user lifecycle policies can delete or block guests after access ends. This matters here because an external package must automatically end when the business engagement finishes. What lifecycle setting is relevant.
D:Revoking resource grants does not always delete the guest object immediately. This matters here because an external package must automatically end when the business engagement finishes. What lifecycle setting is relevant.
Question 557
A guest's package expired but the account remains in the directory. Why is that possible?
- Remove the supplier's active package assignment and downstream resource access.
- Create a dedicated finance catalog with scoped ownership and resources.
- Disable unauthorized package extensions and require a fresh request.
- Separate expiration of package access from removal of the guest directory identity.
Explanation
Correct Answer
D:Revoking resource grants does not always delete the guest object immediately. This matters here because a guest's package expired but the account remains in the directory. Why is that possible.
Incorrect Answers
A:Contract termination should not wait for a scheduled expiry date. This matters here because a guest's package expired but the account remains in the directory. Why is that possible.
B:Business-aligned catalog boundaries simplify delegated entitlement governance. This matters here because a guest's package expired but the account remains in the directory. Why is that possible.
C:Extension settings and expiry policies control renewals.
Question 558
A business wants external users to re-request access after expiry instead of indefinitely extending. Which option applies?
- Use entitlement management external user lifecycle removal settings.
- Replace the broad domain with the intended trusted partner identity domain.
- Disable unauthorized package extensions and require a fresh request.
- Expire the access package assignment and remove its governed resource access.
Explanation
Correct Answer
C:Extension settings and expiry policies control renewals. This matters here because a business wants external users to re-request access after expiry instead of indefinitely extending. Which option….
Incorrect Answers
A:External user lifecycle policies can delete or block guests after access ends. This matters here because a business wants external users to re-request access after expiry instead of indefinitely extending. Which option….
B:An overly broad connected organization can expose request eligibility to unrelated people. This matters here because a business wants external users to re-request access after expiry instead of indefinitely extending. Which option….
D:Entitlement expiry provides automatic access lifecycle control. This matters here because a business wants external users to re-request access after expiry instead of indefinitely extending. Which option….
Question 559
An invited contractor is inactive and has an approved unrelated application assignment. What offboarding precaution is essential?
- Review all direct and indirect resource grants before deleting the guest.
- Separate expiration of package access from removal of the guest directory identity.
- Add the supplier as a connected organization for entitlement management.
- Expire the access package assignment and remove its governed resource access.
Explanation
Correct Answer
A:Package-based lifecycle does not substitute for auditing unrelated assignments. This matters here because an invited contractor is inactive and has an approved unrelated application assignment. What offboarding precaution….
Incorrect Answers
B:Revoking resource grants does not always delete the guest object immediately. This matters here because an invited contractor is inactive and has an approved unrelated application assignment. What offboarding precaution….
C:Connected organizations model eligible external partner populations for requests. This matters here because an invited contractor is inactive and has an approved unrelated application assignment. What offboarding precaution….
D:Entitlement expiry provides automatic access lifecycle control. This matters here because an invited contractor is inactive and has an approved unrelated application assignment. What offboarding precaution….
Question 560
A supplier’s project ended early but its guest identity still has an active access package and unrelated direct app assignment. Which TWO offboarding actions are needed? (Select TWO.)
- Wait for the package’s distant expiration without taking any action.
- Remove or terminate the active access package assignment.
- Audit and revoke unrelated direct app assignments under the supplier offboarding policy.
- Delete the entire shared enterprise app to remove the guest.
- Assume removing the guest from one resource revokes every other grant automatically.
Explanation
Correct Answers
B:Ending the package removes the bundle’s governed grants before scheduled expiry.
C:Package expiration does not automatically revoke every independent resource grant.
Incorrect Answers
A:The engagement has ended and access should not remain unnecessarily active.
D:Removing the application would disrupt unrelated legitimate users.
E:Separate direct or group assignments may continue outside the package.