Question 80An acquired company asks its employees to use their home tenant to sign in to a partner app without creating a new password in the partner directory. Which governance action most directly addresses the recurring risk? Rotate trust keys and review cross-organization sign-in agreements. Review federation trust, certificate rollover, and partner offboarding. Govern connected applications and trusted IdP configuration centrally. Review the registered application and its redirect URIs regularly. ExplanationCorrect Answer B:Review federation trust, certificate rollover, and partner offboarding. Maintaining this control reduces recurrence because: Federation lets an application accept an authentication assertion from a trusted identity system. The immediate response remains: Establish an approved federated or cross-tenant trust arrangement with the external identity provider. Other Answers A:Federated identity preserves the home organization's authentication while enabling delegated trust for the target application. A more direct preventive measure is to review federation trust, certificate rollover, and partner offboarding. C:An identity provider authenticates principals and issues tokens that relying applications can validate. The stronger recurring control is to review federation trust, certificate rollover, and partner offboarding. 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 review federation trust, certificate rollover, and partner offboarding.
Question 81A hotel group confuses users' display names with reliable identities and grants access by matching a name that multiple staff share. Which action most directly resolves the security or identity requirement? Use immutable identity identifiers and authenticated accounts, not display-name strings, to authorize resources. Verify the authenticated user first and then evaluate group membership for authorization. Enforce object-level authorization for every invoice request based on the authenticated customer identity. Inspect authorization at the resource and guest's effective group assignments rather than repeating MFA. ExplanationCorrect Answer A:Display names may be duplicated or renamed and do not uniquely prove a principal. To confirm, rename a test user and confirm authorized resources remain tied to the correct account ID. Other Answers B:Directory attributes and groups support access decisions only after a trusted identity is established. This failure calls for a decision to use immutable identity identifiers and authenticated accounts, not display-name strings, to authorize resources. C:Authentication alone does not prevent insecure direct object references to another tenant's records. This failure calls for a decision to use immutable identity identifiers and authenticated accounts, not display-name strings, to authorize resources. D:An identity can be strongly authenticated yet have no permission to the target resource. The required change instead is to use immutable identity identifiers and authenticated accounts, not display-name strings, to authorize resources.
Question 82A hotel group confuses users' display names with reliable identities and grants access by matching a name that multiple staff share. Which technical distinction is decisive in this case? Directory attributes and groups support access decisions only after a trusted identity is established. Display names may be duplicated or renamed and do not uniquely prove a principal. Authentication alone does not prevent insecure direct object references to another tenant's records. An identity can be strongly authenticated yet have no permission to the target resource. ExplanationCorrect Answer B:Display names may be duplicated or renamed and do not uniquely prove a principal. This is the principle behind: Use immutable identity identifiers and authenticated accounts, not display-name strings, to authorize resources. The evidence to inspect is: Rename a test user and confirm authorized resources remain tied to the correct account ID. Other Answers A:Directory attributes and groups support access decisions only after a trusted identity is established. By contrast, display names may be duplicated or renamed and do not uniquely prove a principal. C:Authentication alone does not prevent insecure direct object references to another tenant's records. By contrast, display names may be duplicated or renamed and do not uniquely prove a principal. D:An identity can be strongly authenticated yet have no permission to the target resource. In the stated system, display names may be duplicated or renamed and do not uniquely prove a principal.
Question 83A hotel group confuses users' display names with reliable identities and grants access by matching a name that multiple staff share. Which observation best validates the chosen approach? Rename a test user and confirm authorized resources remain tied to the correct account ID. Compare the authenticated guest's role memberships against the target site's access policy. Try another customer's invoice ID from a legitimate session and verify the request is denied. Sign in as a different employee and verify a forged department value does not grant extra access. ExplanationCorrect Answer A:Rename a test user and confirm authorized resources remain tied to the correct account ID. This test checks the expected result of: Use immutable identity identifiers and authenticated accounts, not display-name strings, to authorize resources. It matters because: Display names may be duplicated or renamed and do not uniquely prove a principal. Other Answers B:An identity can be strongly authenticated yet have no permission to the target resource. Proving this correction calls for a check to rename a test user and confirm authorized resources remain tied to the correct account ID. C:Authentication alone does not prevent insecure direct object references to another tenant's records. The failure is checked more directly by a test to rename a test user and confirm authorized resources remain tied to the correct account ID. D:Directory attributes and groups support access decisions only after a trusted identity is established. The failure is checked more directly by a test to rename a test user and confirm authorized resources remain tied to the correct account ID.
Question 84A hotel group confuses users' display names with reliable identities and grants access by matching a name that multiple staff share. Which governance action most directly addresses the recurring risk? Include object authorization tests in application release gates. Audit applications for authorization decisions based on mutable labels. Include access-review results in guest user lifecycle audits. Protect group ownership and membership changes with approvals. ExplanationCorrect Answer B:Audit applications for authorization decisions based on mutable labels. Maintaining this control reduces recurrence because: Display names may be duplicated or renamed and do not uniquely prove a principal. The immediate response remains: Use immutable identity identifiers and authenticated accounts, not display-name strings, to authorize resources. Other Answers A:Authentication alone does not prevent insecure direct object references to another tenant's records. A more direct preventive measure is to audit applications for authorization decisions based on mutable labels. C:An identity can be strongly authenticated yet have no permission to the target resource. The lasting safeguard is to audit applications for authorization decisions based on mutable labels. D:Directory attributes and groups support access decisions only after a trusted identity is established. A more direct preventive measure is to audit applications for authorization decisions based on mutable labels.
Question 85A customer portal accepts a valid login and then allows access to every account's invoice by changing a URL identifier. Which action most directly resolves the security or identity requirement? Revoke the contractor's role and resource grants independently of any credential changes. Verify the authenticated user first and then evaluate group membership for authorization. Enforce object-level authorization for every invoice request based on the authenticated customer identity. Apply session expiration and token validation along with user lifecycle revocation safeguards. ExplanationCorrect Answer C:Authentication alone does not prevent insecure direct object references to another tenant's records. To confirm, try another customer's invoice ID from a legitimate session and verify the request is denied. Other Answers A:Changing credentials does not confer or remove role-based authorization by itself. A more relevant action is to enforce object-level authorization for every invoice request based on the authenticated customer identity. B:Directory attributes and groups support access decisions only after a trusted identity is established. A more relevant action is to enforce object-level authorization for every invoice request based on the authenticated customer identity. D:Removing a directory object does not itself ensure every external application stops accepting cached sessions immediately. A more relevant action is to enforce object-level authorization for every invoice request based on the authenticated customer identity.
Question 86A customer portal accepts a valid login and then allows access to every account's invoice by changing a URL identifier. Which technical distinction is decisive in this case? Directory attributes and groups support access decisions only after a trusted identity is established. Changing credentials does not confer or remove role-based authorization by itself. Authentication alone does not prevent insecure direct object references to another tenant's records. Removing a directory object does not itself ensure every external application stops accepting cached sessions immediately. ExplanationCorrect Answer C:Authentication alone does not prevent insecure direct object references to another tenant's records. This is the principle behind: Enforce object-level authorization for every invoice request based on the authenticated customer identity. The evidence to inspect is: Try another customer's invoice ID from a legitimate session and verify the request is denied. Other Answers A:Directory attributes and groups support access decisions only after a trusted identity is established. In the stated system, authentication alone does not prevent insecure direct object references to another tenant's records. B:Changing credentials does not confer or remove role-based authorization by itself. In the stated system, authentication alone does not prevent insecure direct object references to another tenant's records. D:Removing a directory object does not itself ensure every external application stops accepting cached sessions immediately. In the stated system, authentication alone does not prevent insecure direct object references to another tenant's records.
Question 87A customer portal accepts a valid login and then allows access to every account's invoice by changing a URL identifier. 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. Attempt the repository request after role revocation and verify access is denied despite valid sign-in. Revoke an external user and verify access ends after the required revocation policy. ExplanationCorrect Answer B:Try another customer's invoice ID from a legitimate session and verify the request is denied. This test checks the expected result of: Enforce object-level authorization for every invoice request based on the authenticated customer identity. It matters because: Authentication alone does not prevent insecure direct object references to another tenant's records. Other Answers A:Directory attributes and groups support access decisions only after a trusted identity is established. Proving this correction calls for a check to try another customer's invoice ID from a legitimate session and verify the request is denied. C:Changing credentials does not confer or remove role-based authorization by itself. Proving this correction calls for a check to try another customer's invoice ID from a legitimate session and verify the request is denied. D:Removing a directory object does not itself ensure every external application stops accepting cached sessions immediately. Proving this correction calls for a check to try another customer's invoice ID from a legitimate session and verify the request is denied.
Question 88A customer portal accepts a valid login and then allows access to every account's invoice by changing a URL identifier. Which governance action most directly addresses the recurring risk? Include object authorization tests in application release gates. Automate contractor access removal with termination workflows. Document token-lifetime and offboarding behavior for federated services. Protect group ownership and membership changes with approvals. ExplanationCorrect Answer A:Include object authorization tests in application release gates. Maintaining this control reduces recurrence because: Authentication alone does not prevent insecure direct object references to another tenant's records. The immediate response remains: Enforce object-level authorization for every invoice request based on the authenticated customer identity. Other Answers B:Changing credentials does not confer or remove role-based authorization by itself. Reducing this risk requires a practice to include object authorization tests in application release gates. C:Removing a directory object does not itself ensure every external application stops accepting cached sessions immediately. Reducing this risk requires a practice to include object authorization tests in application release gates. D:Directory attributes and groups support access decisions only after a trusted identity is established. Reducing this risk requires a practice to include object authorization tests in application release gates.
Question 89A clinic's identity provider validates employee sign-ins but a legacy application trusts tokens without checking which app they were issued for. Which action most directly resolves the security or identity requirement? Integrate a trusted identity provider for centralized authentication where supported. Validate token audience, issuer, expiry, and signature for each relying application. Establish an approved federated or cross-tenant trust arrangement with the external identity provider. Apply session expiration and token validation along with user lifecycle revocation safeguards. ExplanationCorrect Answer B:A signed identity token is only trustworthy for its intended recipient and valid trust context. To confirm, present a token from a different application and confirm the clinic app rejects it. Other Answers A:An identity provider authenticates principals and issues tokens that relying applications can validate. The corrective action for this requirement is to validate token audience, issuer, expiry, and signature for each relying application. C:Federation lets an application accept an authentication assertion from a trusted identity system. This failure calls for a decision to validate token audience, issuer, expiry, and signature for each relying application. D:Removing a directory object does not itself ensure every external application stops accepting cached sessions immediately. The required change instead is to validate token audience, issuer, expiry, and signature for each relying application.
Question 90A clinic's identity provider validates employee sign-ins but a legacy application trusts tokens without checking which app they were issued for. Which technical distinction is decisive in this case? An identity provider authenticates principals and issues tokens that relying applications can validate. Removing a directory object does not itself ensure every external application stops accepting cached sessions immediately. Federation lets an application accept an authentication assertion from a trusted identity system. A signed identity token is only trustworthy for its intended recipient and valid trust context. ExplanationCorrect Answer D:A signed identity token is only trustworthy for its intended recipient and valid trust context. This is the principle behind: Validate token audience, issuer, expiry, and signature for each relying application. The evidence to inspect is: Present a token from a different application and confirm the clinic app rejects it. Other Answers A:An identity provider authenticates principals and issues tokens that relying applications can validate. By contrast, a signed identity token is only trustworthy for its intended recipient and valid trust context. B:Removing a directory object does not itself ensure every external application stops accepting cached sessions immediately. In the stated system, a signed identity token is only trustworthy for its intended recipient and valid trust context. C:Federation lets an application accept an authentication assertion from a trusted identity system. In the stated system, a signed identity token is only trustworthy for its intended recipient and valid trust context.