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.
Question 111A business portal stores usernames and passwords locally even though it needs only employee email claims from Entra ID. Which observation best validates the chosen approach? Compare Windows domain join needs with cloud application sign-in requirements for the campus. Confirm tokens use the correct issuer and expiration and contain only necessary claims. Sign in through the IdP and inspect token audience and claim validity at the application. Test a valid university-issued assertion and an untrusted institution assertion separately. ExplanationCorrect Answer B:Confirm tokens use the correct issuer and expiration and contain only necessary claims. This test checks the expected result of: Delegate authentication to the organization's identity provider and validate the app's required claims. It matters because: The portal can rely on a trusted provider rather than hold and verify a second password database. 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. A more meaningful verification is to confirm tokens use the correct issuer and expiration and contain only necessary claims. C:An identity provider authenticates principals and issues tokens that relying applications can validate. The relevant acceptance check is to confirm tokens use the correct issuer and expiration and contain only necessary claims. D:Federated identity preserves the home organization's authentication while enabling delegated trust for the target application. Proving this correction calls for a check to confirm tokens use the correct issuer and expiration and contain only necessary claims.
Question 112A business portal stores usernames and passwords locally even though it needs only employee email claims from Entra ID. Which governance action most directly addresses the recurring risk? Rotate trust keys and review cross-organization sign-in agreements. Maintain directory synchronization and legacy-protocol assumptions explicitly. Review the registered application and its redirect URIs regularly. Govern connected applications and trusted IdP configuration centrally. ExplanationCorrect Answer C:Review the registered application and its redirect URIs regularly. Maintaining this control reduces recurrence because: The portal can rely on a trusted provider rather than hold and verify a second password database. The immediate response remains: Delegate authentication to the organization's identity provider and validate the app's required claims. Other Answers A:Federated identity preserves the home organization's authentication while enabling delegated trust for the target application. The lasting safeguard is to review the registered application and its redirect URIs regularly. B:AD DS provides traditional domain and directory services while Entra ID is a cloud identity platform with different protocols and object behavior. The stronger recurring control is to review the registered application and its redirect URIs regularly. D:An identity provider authenticates principals and issues tokens that relying applications can validate. Reducing this risk requires a practice to review the registered application and its redirect URIs regularly.
Question 113A supplier's account is deleted from the buyer's tenant but its previous external session remains accepted by a custom app indefinitely. Which action most directly resolves the security or identity requirement? Use a trusted external identity federation model with appropriate claims and account mapping. Establish an approved federated or cross-tenant trust arrangement with the external identity provider. 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 D:Removing a directory object does not itself ensure every external application stops accepting cached sessions immediately. To confirm, revoke an external user and verify access ends after the required revocation policy. Other Answers A:Federated identity preserves the home organization's authentication while enabling delegated trust for the target application. The corrective action for this requirement is to apply session expiration and token validation along with user lifecycle revocation safeguards. B:Federation lets an application accept an authentication assertion from a trusted identity system. A more relevant action is to apply session expiration and token validation along with user lifecycle revocation safeguards. C:Authentication alone does not prevent insecure direct object references to another tenant's records. The corrective action for this requirement is to apply session expiration and token validation along with user lifecycle revocation safeguards.
Question 114A supplier's account is deleted from the buyer's tenant but its previous external session remains accepted by a custom app indefinitely. Which technical distinction is decisive in this case? Removing a directory object does not itself ensure every external application stops accepting cached sessions immediately. Authentication alone does not prevent insecure direct object references to another tenant's records. Federated identity preserves the home organization's authentication while enabling delegated trust for the target application. Federation lets an application accept an authentication assertion from a trusted identity system. ExplanationCorrect Answer A:Removing a directory object does not itself ensure every external application stops accepting cached sessions immediately. This is the principle behind: Apply session expiration and token validation along with user lifecycle revocation safeguards. The evidence to inspect is: Revoke an external user and verify access ends after the required revocation policy. Other Answers B:Authentication alone does not prevent insecure direct object references to another tenant's records. By contrast, removing a directory object does not itself ensure every external application stops accepting cached sessions immediately. C:Federated identity preserves the home organization's authentication while enabling delegated trust for the target application. By contrast, removing a directory object does not itself ensure every external application stops accepting cached sessions immediately. D:Federation lets an application accept an authentication assertion from a trusted identity system. In the stated system, removing a directory object does not itself ensure every external application stops accepting cached sessions immediately.
Question 115A supplier's account is deleted from the buyer's tenant but its previous external session remains accepted by a custom app indefinitely. Which observation best validates the chosen approach? Test a partner sign-in and verify issuer, audience, and allowed tenant identity claims. Try another customer's invoice ID from a legitimate session and verify the request is denied. Revoke an external user and verify access ends after the required revocation policy. Test a valid university-issued assertion and an untrusted institution assertion separately. ExplanationCorrect Answer C:Revoke an external user and verify access ends after the required revocation policy. This test checks the expected result of: Apply session expiration and token validation along with user lifecycle revocation safeguards. It matters because: Removing a directory object does not itself ensure every external application stops accepting cached sessions immediately. Other Answers A:Federation lets an application accept an authentication assertion from a trusted identity system. Proving this correction calls for a check to revoke an external user and verify access ends after the required revocation policy. B:Authentication alone does not prevent insecure direct object references to another tenant's records. A more meaningful verification is to revoke an external user and verify access ends after the required revocation policy. D:Federated identity preserves the home organization's authentication while enabling delegated trust for the target application. A more meaningful verification is to revoke an external user and verify access ends after the required revocation policy.
Question 116A supplier's account is deleted from the buyer's tenant but its previous external session remains accepted by a custom app indefinitely. Which governance action most directly addresses the recurring risk? Review federation trust, certificate rollover, and partner offboarding. Document token-lifetime and offboarding behavior for federated services. Rotate trust keys and review cross-organization sign-in agreements. Include object authorization tests in application release gates. ExplanationCorrect Answer B:Document token-lifetime and offboarding behavior for federated services. Maintaining this control reduces recurrence because: Removing a directory object does not itself ensure every external application stops accepting cached sessions immediately. The immediate response remains: Apply session expiration and token validation along with user lifecycle revocation safeguards. Other Answers A:Federation lets an application accept an authentication assertion from a trusted identity system. Reducing this risk requires a practice to document token-lifetime and offboarding behavior for federated services. C:Federated identity preserves the home organization's authentication while enabling delegated trust for the target application. A more direct preventive measure is to document token-lifetime and offboarding behavior for federated services. D:Authentication alone does not prevent insecure direct object references to another tenant's records. A more direct preventive measure is to document token-lifetime and offboarding behavior for federated services.
Question 117A contractor changes departments and an internal application keeps access based solely on a stale locally copied employee table. Which action most directly resolves the security or identity requirement? Verify the authenticated user first and then evaluate group membership for authorization. Refresh identity and entitlement data from an authoritative directory source with appropriate lifecycle hooks. Revoke the contractor's role and resource grants independently of any credential changes. Use a trusted external identity federation model with appropriate claims and account mapping. ExplanationCorrect Answer B:Directory-backed identity and current entitlements prevent abandoned local copies from retaining obsolete access decisions. To confirm, move a test user to another department and confirm protected app entitlements update. Other Answers A:Directory attributes and groups support access decisions only after a trusted identity is established. The required change instead is to refresh identity and entitlement data from an authoritative directory source with appropriate lifecycle hooks. C:Changing credentials does not confer or remove role-based authorization by itself. The required change instead is to refresh identity and entitlement data from an authoritative directory source with appropriate lifecycle hooks. D:Federated identity preserves the home organization's authentication while enabling delegated trust for the target application. The required change instead is to refresh identity and entitlement data from an authoritative directory source with appropriate lifecycle hooks.
Question 118A contractor changes departments and an internal application keeps access based solely on a stale locally copied employee table. Which technical distinction is decisive in this case? Federated identity preserves the home organization's authentication while enabling delegated trust for the target application. Directory attributes and groups support access decisions only after a trusted identity is established. Directory-backed identity and current entitlements prevent abandoned local copies from retaining obsolete access decisions. Changing credentials does not confer or remove role-based authorization by itself. ExplanationCorrect Answer C:Directory-backed identity and current entitlements prevent abandoned local copies from retaining obsolete access decisions. This is the principle behind: Refresh identity and entitlement data from an authoritative directory source with appropriate lifecycle hooks. The evidence to inspect is: Move a test user to another department and confirm protected app entitlements update. Other Answers A:Federated identity preserves the home organization's authentication while enabling delegated trust for the target application. In the stated system, directory-backed identity and current entitlements prevent abandoned local copies from retaining obsolete access decisions. B:Directory attributes and groups support access decisions only after a trusted identity is established. In the stated system, directory-backed identity and current entitlements prevent abandoned local copies from retaining obsolete access decisions. D:Changing credentials does not confer or remove role-based authorization by itself. In the stated system, directory-backed identity and current entitlements prevent abandoned local copies from retaining obsolete access decisions.
Question 119A contractor changes departments and an internal application keeps access based solely on a stale locally copied employee table. Which observation best validates the chosen approach? Move a test user to another department and confirm protected app entitlements update. Attempt the repository request after role revocation and verify access is denied despite valid sign-in. Test a valid university-issued assertion and an untrusted institution assertion separately. Sign in as a different employee and verify a forged department value does not grant extra access. ExplanationCorrect Answer A:Move a test user to another department and confirm protected app entitlements update. This test checks the expected result of: Refresh identity and entitlement data from an authoritative directory source with appropriate lifecycle hooks. It matters because: Directory-backed identity and current entitlements prevent abandoned local copies from retaining obsolete access decisions. Other Answers B:Changing credentials does not confer or remove role-based authorization by itself. The failure is checked more directly by a test to move a test user to another department and confirm protected app entitlements update. C:Federated identity preserves the home organization's authentication while enabling delegated trust for the target application. The failure is checked more directly by a test to move a test user to another department and confirm protected app entitlements update. 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 move a test user to another department and confirm protected app entitlements update.
Question 120A contractor changes departments and an internal application keeps access based solely on a stale locally copied employee table. Which governance action most directly addresses the recurring risk? Automate contractor access removal with termination workflows. Use identity lifecycle integrations and periodic stale-access reviews. Rotate trust keys and review cross-organization sign-in agreements. Protect group ownership and membership changes with approvals. ExplanationCorrect Answer B:Use identity lifecycle integrations and periodic stale-access reviews. Maintaining this control reduces recurrence because: Directory-backed identity and current entitlements prevent abandoned local copies from retaining obsolete access decisions. The immediate response remains: Refresh identity and entitlement data from an authoritative directory source with appropriate lifecycle hooks. Other Answers A:Changing credentials does not confer or remove role-based authorization by itself. A more direct preventive measure is to use identity lifecycle integrations and periodic stale-access reviews. C:Federated identity preserves the home organization's authentication while enabling delegated trust for the target application. A more direct preventive measure is to use identity lifecycle integrations and periodic stale-access reviews. D:Directory attributes and groups support access decisions only after a trusted identity is established. A more direct preventive measure is to use identity lifecycle integrations and periodic stale-access reviews.