Question 100An organization grants access by department group and treats the department label itself as proof the request came from the expected employee. Which governance action most directly addresses the recurring risk? Include access-review results in guest user lifecycle audits. Protect group ownership and membership changes with approvals. Govern connected applications and trusted IdP configuration centrally. Audit applications for authorization decisions based on mutable labels. ExplanationCorrect Answer B:Protect group ownership and membership changes with approvals. Maintaining this control reduces recurrence because: Directory attributes and groups support access decisions only after a trusted identity is established. The immediate response remains: Verify the authenticated user first and then evaluate group membership for authorization. Other Answers A:An identity can be strongly authenticated yet have no permission to the target resource. The lasting safeguard is to protect group ownership and membership changes with approvals. C:An identity provider authenticates principals and issues tokens that relying applications can validate. The stronger recurring control is to protect group ownership and membership changes with approvals. D:Display names may be duplicated or renamed and do not uniquely prove a principal. A more direct preventive measure is to protect group ownership and membership changes with approvals.
Question 101A university's student app requires sign-in from another institution using that institution's account, not manual recreation of local accounts. Which action most directly resolves the security or identity requirement? Delegate authentication to the organization's identity provider and validate the app's required claims. Use a trusted external identity federation model with appropriate claims and account mapping. Apply session expiration and token validation along with user lifecycle revocation safeguards. Establish an approved federated or cross-tenant trust arrangement with the external identity provider. ExplanationCorrect Answer B:Federated identity preserves the home organization's authentication while enabling delegated trust for the target application. To confirm, test a valid university-issued assertion and an untrusted institution assertion separately. Other Answers A:The portal can rely on a trusted provider rather than hold and verify a second password database. The required change instead is to use a trusted external identity federation model with appropriate claims and account mapping. C:Removing a directory object does not itself ensure every external application stops accepting cached sessions immediately. The required change instead is to use a trusted external identity federation model with appropriate claims and account mapping. D:Federation lets an application accept an authentication assertion from a trusted identity system. This failure calls for a decision to use a trusted external identity federation model with appropriate claims and account mapping.
Question 102A university's student app requires sign-in from another institution using that institution's account, not manual recreation of local accounts. Which technical distinction is decisive in this case? Federation lets an application accept an authentication assertion from a trusted identity system. Removing a directory object does not itself ensure every external application stops accepting cached sessions immediately. The portal can rely on a trusted provider rather than hold and verify a second password database. Federated identity preserves the home organization's authentication while enabling delegated trust for the target application. ExplanationCorrect Answer D:Federated identity preserves the home organization's authentication while enabling delegated trust for the target application. This is the principle behind: Use a trusted external identity federation model with appropriate claims and account mapping. The evidence to inspect is: Test a valid university-issued assertion and an untrusted institution assertion separately. Other Answers A:Federation lets an application accept an authentication assertion from a trusted identity system. In the stated system, federated identity preserves the home organization's authentication while enabling delegated trust for the target application. B:Removing a directory object does not itself ensure every external application stops accepting cached sessions immediately. In the stated system, federated identity preserves the home organization's authentication while enabling delegated trust for the target application. C:The portal can rely on a trusted provider rather than hold and verify a second password database. In the stated system, federated identity preserves the home organization's authentication while enabling delegated trust for the target application.
Question 103A university's student app requires sign-in from another institution using that institution's account, not manual recreation of local accounts. Which observation best validates the chosen approach? Test a valid university-issued assertion and an untrusted institution assertion separately. Test a partner sign-in and verify issuer, audience, and allowed tenant identity claims. Confirm tokens use the correct issuer and expiration and contain only necessary claims. Revoke an external user and verify access ends after the required revocation policy. ExplanationCorrect Answer A:Test a valid university-issued assertion and an untrusted institution assertion separately. This test checks the expected result of: Use a trusted external identity federation model with appropriate claims and account mapping. It matters because: Federated identity preserves the home organization's authentication while enabling delegated trust for the target application. Other Answers B:Federation lets an application accept an authentication assertion from a trusted identity system. The relevant acceptance check is to test a valid university-issued assertion and an untrusted institution assertion separately. C:The portal can rely on a trusted provider rather than hold and verify a second password database. The failure is checked more directly by a test to test a valid university-issued assertion and an untrusted institution assertion separately. D:Removing a directory object does not itself ensure every external application stops accepting cached sessions immediately. The failure is checked more directly by a test to test a valid university-issued assertion and an untrusted institution assertion separately.
Question 104A university's student app requires sign-in from another institution using that institution's account, not manual recreation of local accounts. Which governance action most directly addresses the recurring risk? Review federation trust, certificate rollover, and partner offboarding. Rotate trust keys and review cross-organization sign-in agreements. Document token-lifetime and offboarding behavior for federated services. Review the registered application and its redirect URIs regularly. ExplanationCorrect Answer B:Rotate trust keys and review cross-organization sign-in agreements. Maintaining this control reduces recurrence because: Federated identity preserves the home organization's authentication while enabling delegated trust for the target application. The immediate response remains: Use a trusted external identity federation model with appropriate claims and account mapping. Other Answers A:Federation lets an application accept an authentication assertion from a trusted identity system. Reducing this risk requires a practice to rotate trust keys and review cross-organization sign-in agreements. C:Removing a directory object does not itself ensure every external application stops accepting cached sessions immediately. A more direct preventive measure is to rotate trust keys and review cross-organization sign-in agreements. D:The portal can rely on a trusted provider rather than hold and verify a second password database. A more direct preventive measure is to rotate trust keys and review cross-organization sign-in agreements.
Question 105A support portal logs successful MFA but cannot explain why a signed-in guest still cannot open a team site. Which action most directly resolves the security or identity requirement? Inspect authorization at the resource and guest's effective group assignments rather than repeating MFA. Repeat multifactor authentication without inspecting the team site membership or file access decision. Enforce object-level authorization for every invoice request based on the authenticated customer identity. Grant the guest a broad tenant-wide administrator role without examining the team site permissions. ExplanationCorrect Answer A:An identity can be strongly authenticated yet have no permission to the target resource. To confirm, compare the authenticated guest's role memberships against the target site's access policy. Other Answers B:Repeat multifactor authentication without inspecting the team site membership or file access decision. Repeating a successful identity challenge does not reveal or correct guest site authorization. The relevant mechanism is: An identity can be strongly authenticated yet have no permission to the target resource. The uniquely targeted response is: Inspect authorization at the resource and guest's effective group assignments rather than repeating MFA. C:Authentication alone does not prevent insecure direct object references to another tenant's records. This failure calls for a decision to inspect authorization at the resource and guest's effective group assignments rather than repeating MFA. D:Grant the guest a broad tenant-wide administrator role without examining the team site permissions. Broad administrative escalation is not a least-privilege response to an unresolved guest site authorization issue. The relevant mechanism is: An identity can be strongly authenticated yet have no permission to the target resource. The uniquely targeted response is: Inspect authorization at the resource and guest's effective group assignments rather than repeating MFA.
Question 106A support portal logs successful MFA but cannot explain why a signed-in guest still cannot open a team site. Which technical distinction is decisive in this case? Authentication establishes an identity, while authorization determines what that identity may access. An identity can be strongly authenticated yet have no permission to the target resource. Authentication alone does not prevent insecure direct object references to another tenant's records. Directory attributes and groups support access decisions only after a trusted identity is established. ExplanationCorrect Answer B:An identity can be strongly authenticated yet have no permission to the target resource. This is the principle behind: Inspect authorization at the resource and guest's effective group assignments rather than repeating MFA. The evidence to inspect is: Compare the authenticated guest's role memberships against the target site's access policy. Other Answers A:Authentication establishes an identity, while authorization determines what that identity may access. By contrast, an identity can be strongly authenticated yet have no permission to the target resource. C:Authentication alone does not prevent insecure direct object references to another tenant's records. By contrast, an identity can be strongly authenticated yet have no permission to the target resource. D:Directory attributes and groups support access decisions only after a trusted identity is established. By contrast, an identity can be strongly authenticated yet have no permission to the target resource.
Question 107A support portal logs successful MFA but cannot explain why a signed-in guest still cannot open a team site. Which observation best validates the chosen approach? Sign in as a different employee and verify a forged department value does not grant extra access. Try another customer's invoice ID from a legitimate session and verify the request is denied. Verify sign-in succeeded and test the finance permission check separately. Compare the authenticated guest's role memberships against the target site's access policy. ExplanationCorrect Answer D:Compare the authenticated guest's role memberships against the target site's access policy. This test checks the expected result of: Inspect authorization at the resource and guest's effective group assignments rather than repeating MFA. It matters because: An identity can be strongly authenticated yet have no permission to the target resource. Other Answers A:Directory attributes and groups support access decisions only after a trusted identity is established. The relevant acceptance check is to compare the authenticated guest's role memberships against the target site's access policy. B:Authentication alone does not prevent insecure direct object references to another tenant's records. The relevant acceptance check is to compare the authenticated guest's role memberships against the target site's access policy. C:Authentication establishes an identity, while authorization determines what that identity may access. A more meaningful verification is to compare the authenticated guest's role memberships against the target site's access policy.
Question 108A support portal logs successful MFA but cannot explain why a signed-in guest still cannot open a team site. Which governance action most directly addresses the recurring risk? Keep identity proof and application permission audits as separate controls. Protect group ownership and membership changes with approvals. Include object authorization tests in application release gates. Include access-review results in guest user lifecycle audits. ExplanationCorrect Answer D:Include access-review results in guest user lifecycle audits. Maintaining this control reduces recurrence because: An identity can be strongly authenticated yet have no permission to the target resource. The immediate response remains: Inspect authorization at the resource and guest's effective group assignments rather than repeating MFA. Other Answers A:Authentication establishes an identity, while authorization determines what that identity may access. The lasting safeguard is to include access-review results in guest user lifecycle audits. B:Directory attributes and groups support access decisions only after a trusted identity is established. The stronger recurring control is to include access-review results in guest user lifecycle audits. C:Authentication alone does not prevent insecure direct object references to another tenant's records. The stronger recurring control is to include access-review results in guest user lifecycle audits.
Question 109A business portal stores usernames and passwords locally even though it needs only employee email claims from Entra ID. Which action most directly resolves the security or identity requirement? Document the different directory roles and integrate hybrid identity only when required. Use a trusted external identity federation model with appropriate claims and account mapping. Integrate a trusted identity provider for centralized authentication where supported. Delegate authentication to the organization's identity provider and validate the app's required claims. ExplanationCorrect Answer D:The portal can rely on a trusted provider rather than hold and verify a second password database. To confirm, confirm tokens use the correct issuer and expiration and contain only necessary claims. Other Answers A:AD DS provides traditional domain and directory services while Entra ID is a cloud identity platform with different protocols and object behavior. This failure calls for a decision to delegate authentication to the organization's identity provider and validate the app's required claims. B:Federated identity preserves the home organization's authentication while enabling delegated trust for the target application. The corrective action for this requirement is to delegate authentication to the organization's identity provider and validate the app's required claims. C:An identity provider authenticates principals and issues tokens that relying applications can validate. The required change instead is to delegate authentication to the organization's identity provider and validate the app's required claims.
Question 110A business portal stores usernames and passwords locally even though it needs only employee email claims from Entra ID. Which technical distinction is decisive in this case? AD DS provides traditional domain and directory services while Entra ID is a cloud identity platform with different protocols and object behavior. An identity provider authenticates principals and issues tokens that relying applications can validate. The portal can rely on a trusted provider rather than hold and verify a second password database. Federated identity preserves the home organization's authentication while enabling delegated trust for the target application. ExplanationCorrect Answer C:The portal can rely on a trusted provider rather than hold and verify a second password database. This is the principle behind: Delegate authentication to the organization's identity provider and validate the app's required claims. The evidence to inspect is: Confirm tokens use the correct issuer and expiration and contain only necessary claims. Other Answers A:AD DS provides traditional domain and directory services while Entra ID is a cloud identity platform with different protocols and object behavior. In the stated system, the portal can rely on a trusted provider rather than hold and verify a second password database. B:An identity provider authenticates principals and issues tokens that relying applications can validate. By contrast, the portal can rely on a trusted provider rather than hold and verify a second password database. D:Federated identity preserves the home organization's authentication while enabling delegated trust for the target application. In the stated system, the portal can rely on a trusted provider rather than hold and verify a second password database.