WGU University KEO1 Practice Test 3
Question 20
At fictional Portside Payments, a software-security team is conducting a service integration assurance review under a specified incident response objective. The case observation is: A build includes a new transitive package whose maintainer and upstream source cannot be traced through the dependency manifest. The team must select a defensible control or assessment. Which repeatable engineering safeguard would most directly reduce recurrence?
- For the a service integration assurance review at fictional Portside Payments, review external access quarterly and automatically revoke unused or expired privileged support grants.
- For the a service integration assurance review at fictional Portside Payments, maintain a supplier risk register with renewal reviews, evidence expiry dates, breach-notification tests, and documented exit triggers.
- For the a service integration assurance review at fictional Portside Payments, require versioned component approval with scheduled advisories review and a documented replacement path.
- For the a service integration assurance review at fictional Portside Payments, enforce dependency review, signed artifact policies, inventory monitoring, and exception expiry in the build pipeline.
Explanation
Writer-proposed answer: D (UNVERIFIED)
Preliminary individual option explanations — NOT expert validated
Correct Answer
D:Provenance and dependency inventory reduce software supply-chain uncertainty but do not by themselves prove a component is vulnerability-free. The reproducible build and software bill of materials identify the complete dependency lineage and a verified approved artifact digest.
Incorrect Answers
A:This response concerns vendor remote-support scope. Here, a build includes a new transitive package whose maintainer and upstream source cannot be traced through the dependency manifest. The confirming evidence is: The reproducible build and software bill of materials identify the complete dependency lineage and a verified approved artifact digest.
B:Supplier security requirements concerns a different operational mechanism. Provenance and dependency inventory reduce software supply-chain uncertainty but do not by themselves prove a component is vulnerability-free.
C:Focusing on open-source license and security review would leave this problem unresolved: A build includes a new transitive package whose maintainer and upstream source cannot be traced through the dependency manifest.
Question 21
At fictional Fairwater Retail, a software-security team is conducting a regulated data-protection review without interrupting essential service availability. The case observation is: A project adds a third-party library because it passes functional tests, although license obligations, update cadence, and known vulnerabilities were not checked. The team must select a defensible control or assessment. Which security design action most directly addresses the documented problem?
- For the a regulated data-protection review at fictional Fairwater Retail, perform coordinated legal-license, maintenance, vulnerability, and ownership review before approving the library.
- For the a regulated data-protection review at fictional Fairwater Retail, minimize data shared with the processor, document permitted purposes, and test anonymization and data-retention controls.
- For the a regulated data-protection review at fictional Fairwater Retail, evaluate supported migration choices, lifecycle dates, compensating controls, and a funded replacement decision before production adoption.
- For the a regulated data-protection review at fictional Fairwater Retail, define verifiable vendor security requirements and contractual acceptance criteria before purchasing the service.
Explanation
Writer-proposed answer: A (UNVERIFIED)
Preliminary individual option explanations — NOT expert validated
Correct Answer
A:A third-party component is both a security dependency and a governance obligation throughout its lifecycle. An approval record includes license compatibility, supported versions, vulnerability disposition, and named maintenance owner.
Incorrect Answers
B:Third-party data processing boundary concerns a different operational mechanism. A third-party component is both a security dependency and a governance obligation throughout its lifecycle.
C:Focusing on software end-of-life dependency would leave this problem unresolved: A project adds a third-party library because it passes functional tests, although license obligations, update cadence, and known vulnerabilities were not checked.
D:Supplier security requirements concerns another aspect of the problem. A third-party component is both a security dependency and a governance obligation throughout its lifecycle.
Question 22
At fictional Fairwater Retail, a software-security team is conducting a regulated data-protection review without interrupting essential service availability. The case observation is: A project adds a third-party library because it passes functional tests, although license obligations, update cadence, and known vulnerabilities were not checked. The team must select a defensible control or assessment. Which independent verification evidence would most directly show that the proposed action succeeded?
- For the a regulated data-protection review at fictional Fairwater Retail, a completed vendor review maps each critical control to contract language, tested evidence, a responsible party, and an exit obligation.
- For the a regulated data-protection review at fictional Fairwater Retail, an approval record includes license compatibility, supported versions, vulnerability disposition, and named maintenance owner.
- For the a regulated data-protection review at fictional Fairwater Retail, session records show bounded permissions, expiration, approval identity, and independent review of support activity.
- For the a regulated data-protection review at fictional Fairwater Retail, independent procurement acceptance references test outcomes, security configuration, risk owner, and remediation conditions.
Explanation
Writer-proposed answer: B (UNVERIFIED)
Preliminary individual option explanations — NOT expert validated
Correct Answer
B:A third-party component is both a security dependency and a governance obligation throughout its lifecycle. An approval record includes license compatibility, supported versions, vulnerability disposition, and named maintenance owner.
Incorrect Answers
A:This response concerns supplier security requirements. Here, a project adds a third-party library because it passes functional tests, although license obligations, update cadence, and known vulnerabilities were not checked. The confirming evidence is: An approval record includes license compatibility, supported versions, vulnerability disposition, and named maintenance owner.
C:Focusing on vendor remote-support scope would leave this problem unresolved: A project adds a third-party library because it passes functional tests, although license obligations, update cadence, and known vulnerabilities were not checked.
D:Acquired software security testing concerns another aspect of the problem. A third-party component is both a security dependency and a governance obligation throughout its lifecycle.
Question 23
At fictional Fairwater Retail, a software-security team is conducting a regulated data-protection review without interrupting essential service availability. The case observation is: A project adds a third-party library because it passes functional tests, although license obligations, update cadence, and known vulnerabilities were not checked. The team must select a defensible control or assessment. Which secure-design principle best explains the appropriate approach?
- For the a regulated data-protection review at fictional Fairwater Retail, product lifecycle and support guarantees are security design inputs, not tasks deferred until a vulnerability appears.
- For the a regulated data-protection review at fictional Fairwater Retail, secure acquisition establishes assurance requirements before reliance on software outside the buyer's direct development control.
- For the a regulated data-protection review at fictional Fairwater Retail, a third-party component is both a security dependency and a governance obligation throughout its lifecycle.
- For the a regulated data-protection review at fictional Fairwater Retail, provenance and dependency inventory reduce software supply-chain uncertainty but do not by themselves prove a component is vulnerability-free.
Explanation
Writer-proposed answer: C (UNVERIFIED)
Preliminary individual option explanations — NOT expert validated
Correct Answer
C:A third-party component is both a security dependency and a governance obligation throughout its lifecycle. An approval record includes license compatibility, supported versions, vulnerability disposition, and named maintenance owner.
Incorrect Answers
A:This response concerns software end-of-life dependency. Here, a project adds a third-party library because it passes functional tests, although license obligations, update cadence, and known vulnerabilities were not checked. The confirming evidence is: An approval record includes license compatibility, supported versions, vulnerability disposition, and named maintenance owner.
B:Supplier security requirements concerns a different operational mechanism. A third-party component is both a security dependency and a governance obligation throughout its lifecycle.
D:Transitive dependency provenance concerns another aspect of the problem. A third-party component is both a security dependency and a governance obligation throughout its lifecycle.
Question 24
At fictional Fairwater Retail, a software-security team is conducting a regulated data-protection review without interrupting essential service availability. The case observation is: A project adds a third-party library because it passes functional tests, although license obligations, update cadence, and known vulnerabilities were not checked. The team must select a defensible control or assessment. Which consequence is most directly associated with leaving this documented problem unresolved?
- For the a regulated data-protection review at fictional Fairwater Retail, late or unreliable notification may delay containment, breach assessment, and regulatory decisions.
- For the a regulated data-protection review at fictional Fairwater Retail, the organization may deploy insecure defaults that supplier certifications did not evaluate.
- For the a regulated data-protection review at fictional Fairwater Retail, compromise of a supplier account could provide persistent unauthorized access to sensitive production systems.
- For the a regulated data-protection review at fictional Fairwater Retail, a hidden license conflict or abandoned vulnerable library can disrupt release and create future remediation debt.
Explanation
Writer-proposed answer: D (UNVERIFIED)
Preliminary individual option explanations — NOT expert validated
Correct Answer
D:A third-party component is both a security dependency and a governance obligation throughout its lifecycle. An approval record includes license compatibility, supported versions, vulnerability disposition, and named maintenance owner.
Incorrect Answers
A:This response concerns supplier incident escalation. Here, a project adds a third-party library because it passes functional tests, although license obligations, update cadence, and known vulnerabilities were not checked. The confirming evidence is: An approval record includes license compatibility, supported versions, vulnerability disposition, and named maintenance owner.
B:Acquired software security testing concerns a different operational mechanism. A third-party component is both a security dependency and a governance obligation throughout its lifecycle.
C:Focusing on vendor remote-support scope would leave this problem unresolved: A project adds a third-party library because it passes functional tests, although license obligations, update cadence, and known vulnerabilities were not checked.
Question 25
At fictional Fairwater Retail, a software-security team is conducting a regulated data-protection review without interrupting essential service availability. The case observation is: A project adds a third-party library because it passes functional tests, although license obligations, update cadence, and known vulnerabilities were not checked. The team must select a defensible control or assessment. Which repeatable engineering safeguard would most directly reduce recurrence?
- For the a regulated data-protection review at fictional Fairwater Retail, require versioned component approval with scheduled advisories review and a documented replacement path.
- For the a regulated data-protection review at fictional Fairwater Retail, review external access quarterly and automatically revoke unused or expired privileged support grants.
- For the a regulated data-protection review at fictional Fairwater Retail, track supplier support dates and run migration readiness reviews before components reach end of life.
- For the a regulated data-protection review at fictional Fairwater Retail, automate data-sharing schema checks and periodically reassess third-party retention and access requirements.
Explanation
Writer-proposed answer: A (UNVERIFIED)
Preliminary individual option explanations — NOT expert validated
Correct Answer
A:A third-party component is both a security dependency and a governance obligation throughout its lifecycle. An approval record includes license compatibility, supported versions, vulnerability disposition, and named maintenance owner.
Incorrect Answers
B:Vendor remote-support scope concerns a different operational mechanism. A third-party component is both a security dependency and a governance obligation throughout its lifecycle.
C:Focusing on software end-of-life dependency would leave this problem unresolved: A project adds a third-party library because it passes functional tests, although license obligations, update cadence, and known vulnerabilities were not checked.
D:Third-party data processing boundary concerns another aspect of the problem. A third-party component is both a security dependency and a governance obligation throughout its lifecycle.
Question 26
At fictional Meadowhall Diagnostics, a software-security team is conducting an application release-readiness meeting under a documented customer-data protection mandate. The case observation is: A project adds a third-party library because it passes functional tests, although license obligations, update cadence, and known vulnerabilities were not checked. The team must select a defensible control or assessment. Which security design action most directly addresses the documented problem?
- For the an application release-readiness meeting at fictional Meadowhall Diagnostics, establish a risk-based evaluation using authoritative attestation, configuration review, a scoped technical assessment, and documented exceptions.
- For the an application release-readiness meeting at fictional Meadowhall Diagnostics, perform coordinated legal-license, maintenance, vulnerability, and ownership review before approving the library.
- For the an application release-readiness meeting at fictional Meadowhall Diagnostics, define incident notification channels, escalation timelines, evidence preservation, and shared responsibilities with the supplier.
- For the an application release-readiness meeting at fictional Meadowhall Diagnostics, define verifiable vendor security requirements and contractual acceptance criteria before purchasing the service.
Explanation
Writer-proposed answer: B (UNVERIFIED)
Preliminary individual option explanations — NOT expert validated
Correct Answer
B:A third-party component is both a security dependency and a governance obligation throughout its lifecycle. An approval record includes license compatibility, supported versions, vulnerability disposition, and named maintenance owner.
Incorrect Answers
A:This response concerns acquired software security testing. Here, a project adds a third-party library because it passes functional tests, although license obligations, update cadence, and known vulnerabilities were not checked. The confirming evidence is: An approval record includes license compatibility, supported versions, vulnerability disposition, and named maintenance owner.
C:Focusing on supplier incident escalation would leave this problem unresolved: A project adds a third-party library because it passes functional tests, although license obligations, update cadence, and known vulnerabilities were not checked.
D:Supplier security requirements concerns another aspect of the problem. A third-party component is both a security dependency and a governance obligation throughout its lifecycle.
Question 27
At fictional Meadowhall Diagnostics, a software-security team is conducting an application release-readiness meeting under a documented customer-data protection mandate. The case observation is: A project adds a third-party library because it passes functional tests, although license obligations, update cadence, and known vulnerabilities were not checked. The team must select a defensible control or assessment. Which independent verification evidence would most directly show that the proposed action succeeded?
- For the an application release-readiness meeting at fictional Meadowhall Diagnostics, the reproducible build and software bill of materials identify the complete dependency lineage and a verified approved artifact digest.
- For the an application release-readiness meeting at fictional Meadowhall Diagnostics, transfer logs and sampling establish that only approved aggregate fields cross the vendor boundary and retention is enforced.
- For the an application release-readiness meeting at fictional Meadowhall Diagnostics, an approval record includes license compatibility, supported versions, vulnerability disposition, and named maintenance owner.
- For the an application release-readiness meeting at fictional Meadowhall Diagnostics, a completed vendor review maps each critical control to contract language, tested evidence, a responsible party, and an exit obligation.
Explanation
Writer-proposed answer: C (UNVERIFIED)
Preliminary individual option explanations — NOT expert validated
Correct Answer
C:A third-party component is both a security dependency and a governance obligation throughout its lifecycle. An approval record includes license compatibility, supported versions, vulnerability disposition, and named maintenance owner.
Incorrect Answers
A:This response concerns transitive dependency provenance. Here, a project adds a third-party library because it passes functional tests, although license obligations, update cadence, and known vulnerabilities were not checked. The confirming evidence is: An approval record includes license compatibility, supported versions, vulnerability disposition, and named maintenance owner.
B:Third-party data processing boundary concerns a different operational mechanism. A third-party component is both a security dependency and a governance obligation throughout its lifecycle.
D:Supplier security requirements concerns another aspect of the problem. A third-party component is both a security dependency and a governance obligation throughout its lifecycle.
Question 28
At fictional Meadowhall Diagnostics, a software-security team is conducting an application release-readiness meeting under a documented customer-data protection mandate. The case observation is: A project adds a third-party library because it passes functional tests, although license obligations, update cadence, and known vulnerabilities were not checked. The team must select a defensible control or assessment. Which secure-design principle best explains the appropriate approach?
- For the an application release-readiness meeting at fictional Meadowhall Diagnostics, data minimization and purpose limitation reduce exposure at third-party integration points.
- For the an application release-readiness meeting at fictional Meadowhall Diagnostics, external support access is a privileged trust boundary that requires controllable authorization and accountability.
- For the an application release-readiness meeting at fictional Meadowhall Diagnostics, product lifecycle and support guarantees are security design inputs, not tasks deferred until a vulnerability appears.
- For the an application release-readiness meeting at fictional Meadowhall Diagnostics, a third-party component is both a security dependency and a governance obligation throughout its lifecycle.
Explanation
Writer-proposed answer: D (UNVERIFIED)
Preliminary individual option explanations — NOT expert validated
Correct Answer
D:A third-party component is both a security dependency and a governance obligation throughout its lifecycle. An approval record includes license compatibility, supported versions, vulnerability disposition, and named maintenance owner.
Incorrect Answers
A:This response concerns third-party data processing boundary. Here, a project adds a third-party library because it passes functional tests, although license obligations, update cadence, and known vulnerabilities were not checked. The confirming evidence is: An approval record includes license compatibility, supported versions, vulnerability disposition, and named maintenance owner.
B:Vendor remote-support scope concerns a different operational mechanism. A third-party component is both a security dependency and a governance obligation throughout its lifecycle.
C:Focusing on software end-of-life dependency would leave this problem unresolved: A project adds a third-party library because it passes functional tests, although license obligations, update cadence, and known vulnerabilities were not checked.
Question 29
At fictional Meadowhall Diagnostics, a software-security team is conducting an application release-readiness meeting under a documented customer-data protection mandate. The case observation is: A project adds a third-party library because it passes functional tests, although license obligations, update cadence, and known vulnerabilities were not checked. The team must select a defensible control or assessment. Which consequence is most directly associated with leaving this documented problem unresolved?
- For the an application release-readiness meeting at fictional Meadowhall Diagnostics, a hidden license conflict or abandoned vulnerable library can disrupt release and create future remediation debt.
- For the an application release-readiness meeting at fictional Meadowhall Diagnostics, the organization can inherit unmitigated security obligations and have no enforceable response when weaknesses emerge.
- For the an application release-readiness meeting at fictional Meadowhall Diagnostics, the organization may deploy insecure defaults that supplier certifications did not evaluate.
- For the an application release-readiness meeting at fictional Meadowhall Diagnostics, an untrusted dependency could introduce malicious code or unsupported components into releases without an obvious direct dependency change.
Explanation
Writer-proposed answer: A (UNVERIFIED)
Preliminary individual option explanations — NOT expert validated
Correct Answer
A:A third-party component is both a security dependency and a governance obligation throughout its lifecycle. An approval record includes license compatibility, supported versions, vulnerability disposition, and named maintenance owner.
Incorrect Answers
B:Supplier security requirements concerns a different operational mechanism. A third-party component is both a security dependency and a governance obligation throughout its lifecycle.
C:Focusing on acquired software security testing would leave this problem unresolved: A project adds a third-party library because it passes functional tests, although license obligations, update cadence, and known vulnerabilities were not checked.
D:Transitive dependency provenance concerns another aspect of the problem. A third-party component is both a security dependency and a governance obligation throughout its lifecycle.
Question 30
At fictional Meadowhall Diagnostics, a software-security team is conducting an application release-readiness meeting under a documented customer-data protection mandate. The case observation is: A project adds a third-party library because it passes functional tests, although license obligations, update cadence, and known vulnerabilities were not checked. The team must select a defensible control or assessment. Which repeatable engineering safeguard would most directly reduce recurrence?
- For the an application release-readiness meeting at fictional Meadowhall Diagnostics, track supplier support dates and run migration readiness reviews before components reach end of life.
- For the an application release-readiness meeting at fictional Meadowhall Diagnostics, require versioned component approval with scheduled advisories review and a documented replacement path.
- For the an application release-readiness meeting at fictional Meadowhall Diagnostics, repeat technical assurance after major vendor releases or configuration and integration changes.
- For the an application release-readiness meeting at fictional Meadowhall Diagnostics, maintain a supplier risk register with renewal reviews, evidence expiry dates, breach-notification tests, and documented exit triggers.
Explanation
Writer-proposed answer: B (UNVERIFIED)
Preliminary individual option explanations — NOT expert validated
Correct Answer
B:A third-party component is both a security dependency and a governance obligation throughout its lifecycle. An approval record includes license compatibility, supported versions, vulnerability disposition, and named maintenance owner.
Incorrect Answers
A:This response concerns software end-of-life dependency. Here, a project adds a third-party library because it passes functional tests, although license obligations, update cadence, and known vulnerabilities were not checked. The confirming evidence is: An approval record includes license compatibility, supported versions, vulnerability disposition, and named maintenance owner.
C:Focusing on acquired software security testing would leave this problem unresolved: A project adds a third-party library because it passes functional tests, although license obligations, update cadence, and known vulnerabilities were not checked.
D:Supplier security requirements concerns another aspect of the problem. A third-party component is both a security dependency and a governance obligation throughout its lifecycle.