Question 390 A purchased analytics tool requires global administrator access to collect only read-only metrics. What should be challenged? Define shared responsibility and contractual recovery commitments with supporting evidence Verify data residency, transfer obligations and actual processing locations Assess maintenance health, vulnerability history and alternative dependency options Require justifiable least-privilege integration permissions before onboarding Explanation Correct Answer D:Overbroad integration access increases business impact of vendor compromise. Incorrect Answers A:Outsourcing operations does not eliminate customer responsibility for continuity outcomes; this responds to the different circumstance in which a SaaS provider cannot explain its customer-data backup and recovery obligations, while the current case states that a purchased analytics tool requires global administrator access to collect only read-only metrics, calling for require justifiable least-privilege integration permissions before onboarding. B:The other scenario states that an organization's acquired HR platform stores employee data in an undisclosed region, where geographic processing can create legal and contractual exposure independent of application functionality; by contrast, the present case requires require justifiable least-privilege integration permissions before onboarding. C:This option fits a different fact pattern where an open-source library has a permissive license but no maintainer security response process: license terms do not establish ongoing security support; the current case instead requires require justifiable least-privilege integration permissions before onboarding.
Question 391 A supplier's attestation covers a different hosting product from the one being purchased. What should be verified? Require justifiable least-privilege integration permissions before onboarding Confirm report scope, control exclusions and relevant service boundaries Verify data residency, transfer obligations and actual processing locations Assess security, exit capabilities and data lifecycle obligations before contract award Explanation Correct Answer B:An assurance opinion for another product cannot be assumed to cover the purchased system. Incorrect Answers A:Overbroad integration access increases business impact of vendor compromise; it is relevant where a purchased analytics tool requires global administrator access to collect only read-only metrics, whereas the current facts require confirm report scope, control exclusions and relevant service boundaries to address the stated problem. C:The other scenario states that an organization's acquired HR platform stores employee data in an undisclosed region, where geographic processing can create legal and contractual exposure independent of application functionality; by contrast, the present case requires confirm report scope, control exclusions and relevant service boundaries. D:For the separate situation in which a corporation buys a billing platform without confirming whether the vendor supports encryption-key export and data deletion, acquired software can create long-lived dependency and privacy risks not visible in features; here the stated problem requires confirm report scope, control exclusions and relevant service boundaries.
Question 392 An organization's acquired HR platform stores employee data in an undisclosed region. What must due diligence establish? Define shared responsibility and contractual recovery commitments with supporting evidence Assess security, exit capabilities and data lifecycle obligations before contract award Verify data residency, transfer obligations and actual processing locations Require justifiable least-privilege integration permissions before onboarding Explanation Correct Answer C:Geographic processing can create legal and contractual exposure independent of application functionality. Incorrect Answers A:Outsourcing operations does not eliminate customer responsibility for continuity outcomes; although this helps when a SaaS provider cannot explain its customer-data backup and recovery obligations, it leaves the current case's need to verify data residency, transfer obligations and actual processing locations unresolved. B:Acquired software can create long-lived dependency and privacy risks not visible in features; although this helps when a corporation buys a billing platform without confirming whether the vendor supports encryption-key export and data deletion, it leaves the current case's need to verify data residency, transfer obligations and actual processing locations unresolved. D:Overbroad integration access increases business impact of vendor compromise; this responds to the different circumstance in which a purchased analytics tool requires global administrator access to collect only read-only metrics, while the current case states that an organization's acquired HR platform stores employee data in an undisclosed region, calling for verify data residency, transfer obligations and actual processing locations.
Question 393 An M&A team migrates acquired code without checking for secrets or licensing restrictions. What should transition planning do? Assess maintenance health, vulnerability history and alternative dependency options Require justifiable least-privilege integration permissions before onboarding Inventory embedded credentials, dependencies and license obligations before integration Define shared responsibility and contractual recovery commitments with supporting evidence Explanation Correct Answer C:Inherited software can import secrets and compliance exposure into the new environment. Incorrect Answers A:For the separate situation in which an open-source library has a permissive license but no maintainer security response process, license terms do not establish ongoing security support; here the stated problem requires inventory embedded credentials, dependencies and license obligations before integration. B:Overbroad integration access increases business impact of vendor compromise; this responds to the different circumstance in which a purchased analytics tool requires global administrator access to collect only read-only metrics, while the current case states that an M&A team migrates acquired code without checking for secrets or licensing restrictions, calling for inventory embedded credentials, dependencies and license obligations before integration. D:Outsourcing operations does not eliminate customer responsibility for continuity outcomes; although this helps when a SaaS provider cannot explain its customer-data backup and recovery obligations, it leaves the current case's need to inventory embedded credentials, dependencies and license obligations before integration unresolved.
Question 394 An application concatenates untrusted customer input into SQL statements. What coding control is required? Check object-level entitlements for every requested resource and tenant boundary Use parameterized database queries with server-side authorization and validation Use response behavior that minimizes account enumeration and log abuse patterns Apply output encoding appropriate to the rendering context and enforce safe content handling Explanation Correct Answer B:Bound parameters separate data from SQL structure and reduce injection risk. Incorrect Answers A:This option fits a different fact pattern where an API accepts an access token but skips authorization to individual tenant records: authentication proves a caller identity, not permission to access arbitrary records; the current case instead requires use parameterized database queries with server-side authorization and validation. C:Distinct reset outcomes disclose valid account identifiers to attackers; although this helps when a password reset endpoint returns different messages for existing and nonexistent accounts, it leaves the current case's need to use parameterized database queries with server-side authorization and validation unresolved. D:For the separate situation in which a web application reflects user comments as HTML without context-aware encoding, untrusted content can become executable script if HTML output contexts are unprotected; here the stated problem requires use parameterized database queries with server-side authorization and validation.
Question 395 A web application reflects user comments as HTML without context-aware encoding. What should developers do? Check object-level entitlements for every requested resource and tenant boundary Apply output encoding appropriate to the rendering context and enforce safe content handling Use parameterized database queries with server-side authorization and validation Restrict outbound URL destinations and block internal and link-local targets Explanation Correct Answer B:Untrusted content can become executable script if HTML output contexts are unprotected. Incorrect Answers A:The other scenario states that an API accepts an access token but skips authorization to individual tenant records, where authentication proves a caller identity, not permission to access arbitrary records; by contrast, the present case requires apply output encoding appropriate to the rendering context and enforce safe content handling. C:Bound parameters separate data from SQL structure and reduce injection risk; it is relevant where an application concatenates untrusted customer input into SQL statements, whereas the current facts require apply output encoding appropriate to the rendering context and enforce safe content handling to address the stated problem. D:This option fits a different fact pattern where a backend service follows user-supplied URLs and can reach cloud metadata endpoints: server-side request forgery can use application network privileges to reach protected services; the current case instead requires apply output encoding appropriate to the rendering context and enforce safe content handling.
Question 396 A file upload API trusts a browser-supplied filename to build local storage paths. What should it enforce? Use response behavior that minimizes account enumeration and log abuse patterns Canonicalize and constrain paths and store uploads outside executable locations Check object-level entitlements for every requested resource and tenant boundary Use constant-time verification through vetted cryptographic libraries Explanation Correct Answer B:Untrusted paths can traverse directories and write unintended files. Incorrect Answers A:This option fits a different fact pattern where a password reset endpoint returns different messages for existing and nonexistent accounts: distinct reset outcomes disclose valid account identifiers to attackers; the current case instead requires canonicalize and constrain paths and store uploads outside executable locations. C:The other scenario states that an API accepts an access token but skips authorization to individual tenant records, where authentication proves a caller identity, not permission to access arbitrary records; by contrast, the present case requires canonicalize and constrain paths and store uploads outside executable locations. D:Secret-dependent comparison timing can create an observable side channel; this responds to the different circumstance in which a payment service compares user-supplied signatures with an early-exit string comparison, while the current case states that a file upload API trusts a browser-supplied filename to build local storage paths, calling for canonicalize and constrain paths and store uploads outside executable locations.
Question 397 An API accepts an access token but skips authorization to individual tenant records. What must be added? Canonicalize and constrain paths and store uploads outside executable locations Restrict outbound URL destinations and block internal and link-local targets Check object-level entitlements for every requested resource and tenant boundary Use parameterized database queries with server-side authorization and validation Explanation Correct Answer C:Authentication proves a caller identity, not permission to access arbitrary records. Incorrect Answers A:Untrusted paths can traverse directories and write unintended files; this responds to the different circumstance in which a file upload API trusts a browser-supplied filename to build local storage paths, while the current case states that an API accepts an access token but skips authorization to individual tenant records, calling for check object-level entitlements for every requested resource and tenant boundary. B:This option fits a different fact pattern where a backend service follows user-supplied URLs and can reach cloud metadata endpoints: server-side request forgery can use application network privileges to reach protected services; the current case instead requires check object-level entitlements for every requested resource and tenant boundary. D:Bound parameters separate data from SQL structure and reduce injection risk; it is relevant where an application concatenates untrusted customer input into SQL statements, whereas the current facts require check object-level entitlements for every requested resource and tenant boundary to address the stated problem.
Question 398 A password reset endpoint returns different messages for existing and nonexistent accounts. What should be mitigated? Use constant-time verification through vetted cryptographic libraries Use response behavior that minimizes account enumeration and log abuse patterns Use parameterized database queries with server-side authorization and validation Check object-level entitlements for every requested resource and tenant boundary Explanation Correct Answer B:Distinct reset outcomes disclose valid account identifiers to attackers. Incorrect Answers A:Secret-dependent comparison timing can create an observable side channel; although this helps when a payment service compares user-supplied signatures with an early-exit string comparison, it leaves the current case's need to use response behavior that minimizes account enumeration and log abuse patterns unresolved. C:This option fits a different fact pattern where an application concatenates untrusted customer input into SQL statements: bound parameters separate data from SQL structure and reduce injection risk; the current case instead requires use response behavior that minimizes account enumeration and log abuse patterns. D:The other scenario states that an API accepts an access token but skips authorization to individual tenant records, where authentication proves a caller identity, not permission to access arbitrary records; by contrast, the present case requires use response behavior that minimizes account enumeration and log abuse patterns.
Question 399 A backend service follows user-supplied URLs and can reach cloud metadata endpoints. What should developers enforce? Restrict outbound URL destinations and block internal and link-local targets Apply output encoding appropriate to the rendering context and enforce safe content handling Use constant-time verification through vetted cryptographic libraries Canonicalize and constrain paths and store uploads outside executable locations Explanation Correct Answer A:Server-side request forgery can use application network privileges to reach protected services. Incorrect Answers B:The other scenario states that a web application reflects user comments as HTML without context-aware encoding, where untrusted content can become executable script if HTML output contexts are unprotected; by contrast, the present case requires restrict outbound URL destinations and block internal and link-local targets. C:This option fits a different fact pattern where a payment service compares user-supplied signatures with an early-exit string comparison: secret-dependent comparison timing can create an observable side channel; the current case instead requires restrict outbound URL destinations and block internal and link-local targets. D:Untrusted paths can traverse directories and write unintended files; although this helps when a file upload API trusts a browser-supplied filename to build local storage paths, it leaves the current case's need to restrict outbound URL destinations and block internal and link-local targets unresolved.
Question 400 A payment service compares user-supplied signatures with an early-exit string comparison. What implementation fix is appropriate? Use constant-time verification through vetted cryptographic libraries Add rate limits to signature verification but retain the secret-dependent early-exit comparison Increase the signature key length while retaining the same early-exit comparison logic Hash both signatures and then compare the resulting digests with the same early-exit function Explanation Correct Answer A:Secret-dependent comparison timing can create an observable side channel. Incorrect Answers B:Throttling may reduce the attack sampling rate, but leaving the timing-dependent comparison permits a side-channel at the same verification step. C:Key strength does not remove secret-dependent timing leakage from how expected and received signatures are compared. D:A preceding hash does not guarantee constant-time equality; the comparison can still reveal secret-dependent progress and should be replaced.
