Question 60A charity stores sensitive donor data in a compliant region and assumes the region alone proves every privacy obligation has been met. Which governance action most directly addresses the recurring risk? Document key custody, rotation, and recovery in the data protection standard. Maintain a data protection assessment covering the full record lifecycle. Maintain a responsibility matrix for each cloud service and validate it when the service model changes. Audit sensitive-data permissions independently from internet edge filtering. ExplanationCorrect Answer B:Maintain a data protection assessment covering the full record lifecycle. Maintaining this control reduces recurrence because: Data residency is one element of governance, not a replacement for privacy principles or security controls. The immediate response remains: Combine data-location controls with access, retention, lawful-use, and audit safeguards. Other Answers A:Encryption protects data confidentiality while hashing is a one-way integrity-oriented transformation, not reversible data encryption. The lasting safeguard is to maintain a data protection assessment covering the full record lifecycle. C:The shared responsibility model assigns provider infrastructure protection separately from customer configuration, identity, and data controls. A more direct preventive measure is to maintain a data protection assessment covering the full record lifecycle. D:Defense-in-depth requires controls close to identities and data because network filtering cannot judge every authorized session. A more direct preventive measure is to maintain a data protection assessment covering the full record lifecycle.
Question 61An employee enters a correct password but the app denies access because the employee lacks a required finance role. Which action most directly resolves the security or identity requirement? Revoke the contractor's role and resource grants independently of any credential changes. Distinguish successful authentication from resource authorization and correct the role assignment only if approved. Delegate authentication to the organization's identity provider and validate the app's required claims. Reset the employee password again and assume sign-in success automatically grants the finance application role. ExplanationCorrect Answer B:Authentication establishes an identity, while authorization determines what that identity may access. To confirm, verify sign-in succeeded and test the finance permission check separately. Other Answers A:Changing credentials does not confer or remove role-based authorization by itself. The required change instead is to distinguish successful authentication from resource authorization and correct the role assignment only if approved. C:The portal can rely on a trusted provider rather than hold and verify a second password database. The required change instead is to distinguish successful authentication from resource authorization and correct the role assignment only if approved. D:Reset the employee password again and assume sign-in success automatically grants the finance application role. Resetting a password does not add the missing approved finance authorization. The relevant mechanism is: Authentication establishes an identity, while authorization determines what that identity may access. The uniquely targeted response is: Distinguish successful authentication from resource authorization and correct the role assignment only if approved.
Question 62An employee enters a correct password but the app denies access because the employee lacks a required finance role. Which technical distinction is decisive in this case? An identity can be strongly authenticated yet have no permission to the target resource. Authentication establishes an identity, while authorization determines what that identity may access. Changing credentials does not confer or remove role-based authorization by itself. The portal can rely on a trusted provider rather than hold and verify a second password database. ExplanationCorrect Answer B:Authentication establishes an identity, while authorization determines what that identity may access. This is the principle behind: Distinguish successful authentication from resource authorization and correct the role assignment only if approved. The evidence to inspect is: Verify sign-in succeeded and test the finance permission check separately. Other Answers A:An identity can be strongly authenticated yet have no permission to the target resource. In the stated system, authentication establishes an identity, while authorization determines what that identity may access. C:Changing credentials does not confer or remove role-based authorization by itself. By contrast, authentication establishes an identity, while authorization determines what that identity may access. D:The portal can rely on a trusted provider rather than hold and verify a second password database. By contrast, authentication establishes an identity, while authorization determines what that identity may access.
Question 63An employee enters a correct password but the app denies access because the employee lacks a required finance role. Which observation best validates the chosen approach? Attempt the repository request after role revocation and verify access is denied despite valid sign-in. Confirm tokens use the correct issuer and expiration and contain only necessary claims. Compare the authenticated guest's role memberships against the target site's access policy. Verify sign-in succeeded and test the finance permission check separately. ExplanationCorrect Answer D:Verify sign-in succeeded and test the finance permission check separately. This test checks the expected result of: Distinguish successful authentication from resource authorization and correct the role assignment only if approved. It matters because: Authentication establishes an identity, while authorization determines what that identity may access. Other Answers A:Changing credentials does not confer or remove role-based authorization by itself. The relevant acceptance check is to verify sign-in succeeded and test the finance permission check separately. B:The portal can rely on a trusted provider rather than hold and verify a second password database. The relevant acceptance check is to verify sign-in succeeded and test the finance permission check separately. C:An identity can be strongly authenticated yet have no permission to the target resource. The failure is checked more directly by a test to verify sign-in succeeded and test the finance permission check separately.
Question 64An employee enters a correct password but the app denies access because the employee lacks a required finance role. Which governance action most directly addresses the recurring risk? Automate contractor access removal with termination workflows. Keep identity proof and application permission audits as separate controls. Review the registered application and its redirect URIs regularly. Include access-review results in guest user lifecycle audits. ExplanationCorrect Answer B:Keep identity proof and application permission audits as separate controls. Maintaining this control reduces recurrence because: Authentication establishes an identity, while authorization determines what that identity may access. The immediate response remains: Distinguish successful authentication from resource authorization and correct the role assignment only if approved. Other Answers A:Changing credentials does not confer or remove role-based authorization by itself. A more direct preventive measure is to keep identity proof and application permission audits as separate controls. C:The portal can rely on a trusted provider rather than hold and verify a second password database. A more direct preventive measure is to keep identity proof and application permission audits as separate controls. D:An identity can be strongly authenticated yet have no permission to the target resource. The lasting safeguard is to keep identity proof and application permission audits as separate controls.
Question 65A developer thinks a password reset grants a former contractor renewed permission to view a confidential repository. Which action most directly resolves the security or identity requirement? 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. Enforce object-level authorization for every invoice request based on the authenticated customer identity. Distinguish successful authentication from resource authorization and correct the role assignment only if approved. ExplanationCorrect Answer B:Changing credentials does not confer or remove role-based authorization by itself. To confirm, attempt the repository request after role revocation and verify access is denied despite valid sign-in. Other Answers A:Directory-backed identity and current entitlements prevent abandoned local copies from retaining obsolete access decisions. The required change instead is to revoke the contractor's role and resource grants independently of any credential changes. C:Authentication alone does not prevent insecure direct object references to another tenant's records. The required change instead is to revoke the contractor's role and resource grants independently of any credential changes. D:Authentication establishes an identity, while authorization determines what that identity may access. This failure calls for a decision to revoke the contractor's role and resource grants independently of any credential changes.
Question 66A developer thinks a password reset grants a former contractor renewed permission to view a confidential repository. Which technical distinction is decisive in this case? Directory-backed identity and current entitlements prevent abandoned local copies from retaining obsolete access decisions. Authentication establishes an identity, while authorization determines what that identity may access. Authentication alone does not prevent insecure direct object references to another tenant's records. Changing credentials does not confer or remove role-based authorization by itself. ExplanationCorrect Answer D:Changing credentials does not confer or remove role-based authorization by itself. This is the principle behind: Revoke the contractor's role and resource grants independently of any credential changes. The evidence to inspect is: Attempt the repository request after role revocation and verify access is denied despite valid sign-in. Other Answers A:Directory-backed identity and current entitlements prevent abandoned local copies from retaining obsolete access decisions. In the stated system, changing credentials does not confer or remove role-based authorization by itself. B:Authentication establishes an identity, while authorization determines what that identity may access. In the stated system, changing credentials does not confer or remove role-based authorization by itself. C:Authentication alone does not prevent insecure direct object references to another tenant's records. In the stated system, changing credentials does not confer or remove role-based authorization by itself.
Question 67A developer thinks a password reset grants a former contractor renewed permission to view a confidential repository. Which observation best validates the chosen approach? Attempt the repository request after role revocation and verify access is denied despite valid sign-in. Verify sign-in succeeded and test the finance permission check separately. Try another customer's invoice ID from a legitimate session and verify the request is denied. Move a test user to another department and confirm protected app entitlements update. ExplanationCorrect Answer A:Attempt the repository request after role revocation and verify access is denied despite valid sign-in. This test checks the expected result of: Revoke the contractor's role and resource grants independently of any credential changes. It matters because: Changing credentials does not confer or remove role-based authorization by itself. Other Answers B:Authentication establishes an identity, while authorization determines what that identity may access. The relevant acceptance check is to attempt the repository request after role revocation and verify access is denied despite valid sign-in. 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 attempt the repository request after role revocation and verify access is denied despite valid sign-in. D:Directory-backed identity and current entitlements prevent abandoned local copies from retaining obsolete access decisions. The failure is checked more directly by a test to attempt the repository request after role revocation and verify access is denied despite valid sign-in.
Question 68A developer thinks a password reset grants a former contractor renewed permission to view a confidential repository. Which governance action most directly addresses the recurring risk? Include object authorization tests in application release gates. Use identity lifecycle integrations and periodic stale-access reviews. Keep identity proof and application permission audits as separate controls. Automate contractor access removal with termination workflows. ExplanationCorrect Answer D:Automate contractor access removal with termination workflows. Maintaining this control reduces recurrence because: Changing credentials does not confer or remove role-based authorization by itself. The immediate response remains: Revoke the contractor's role and resource grants independently of any credential changes. Other Answers A:Authentication alone does not prevent insecure direct object references to another tenant's records. The stronger recurring control is to automate contractor access removal with termination workflows. B:Directory-backed identity and current entitlements prevent abandoned local copies from retaining obsolete access decisions. The stronger recurring control is to automate contractor access removal with termination workflows. C:Authentication establishes an identity, while authorization determines what that identity may access. The lasting safeguard is to automate contractor access removal with termination workflows.
Question 69A SaaS app asks every department to store its own employee passwords despite a central corporate identity directory. 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. Validate token audience, issuer, expiry, and signature for each relying application. Integrate a trusted identity provider for centralized authentication where supported. Establish an approved federated or cross-tenant trust arrangement with the external identity provider. ExplanationCorrect Answer C:An identity provider authenticates principals and issues tokens that relying applications can validate. To confirm, sign in through the IdP and inspect token audience and claim validity at the application. Other Answers A:The portal can rely on a trusted provider rather than hold and verify a second password database. A more relevant action is to integrate a trusted identity provider for centralized authentication where supported. B:A signed identity token is only trustworthy for its intended recipient and valid trust context. This failure calls for a decision to integrate a trusted identity provider for centralized authentication where supported. D:Federation lets an application accept an authentication assertion from a trusted identity system. The required change instead is to integrate a trusted identity provider for centralized authentication where supported.
Question 70A SaaS app asks every department to store its own employee passwords despite a central corporate identity directory. Which technical distinction is decisive in this case? A signed identity token is only trustworthy for its intended recipient and valid trust context. The portal can rely on a trusted provider rather than hold and verify a second password database. An identity provider authenticates principals and issues tokens that relying applications can validate. Federation lets an application accept an authentication assertion from a trusted identity system. ExplanationCorrect Answer C:An identity provider authenticates principals and issues tokens that relying applications can validate. This is the principle behind: Integrate a trusted identity provider for centralized authentication where supported. The evidence to inspect is: Sign in through the IdP and inspect token audience and claim validity at the application. Other Answers A:A signed identity token is only trustworthy for its intended recipient and valid trust context. By contrast, an identity provider authenticates principals and issues tokens that relying applications can validate. B:The portal can rely on a trusted provider rather than hold and verify a second password database. In the stated system, an identity provider authenticates principals and issues tokens that relying applications can validate. D:Federation lets an application accept an authentication assertion from a trusted identity system. By contrast, an identity provider authenticates principals and issues tokens that relying applications can validate.