McAfee-Secured Website

Exam Code: KEO1

Exam Name: Secure Software Design

Certification Provider: WGU University

100% WGU University KEO1 Guaranteed Success With Testking Training Materials

Get Real KEO1 Exam Questions & Expert Verified Answers as Experienced on the Real Exam!

66 Questions & Answers with Testing Engine

"Secure Software Design Exam", also known as KEO1 exam, is a WGU University certification exam.

Pass your tests with the always up-to-date KEO1 Exam Engine. Your KEO1 training materials keep you at the head of the pack!

Satisfaction Guaranteed

Money Back Guarantee

Testking provides hassle-free money back guarantee with our products. That is because we have 100% trust in the abilities of our professional and experience product team, and our record is a proof of that.

99.6% PASS RATE
Was: $137.49
Now: $124.99

WGU University KEO1 Practice Test 5

Question 40

At fictional Amberline Manufacturing, a software-security team is conducting a supplier and application control assessment under a defined risk appetite and change authorization. The case observation is: A purchased billing platform gives a supplier permanent privileged access to production troubleshooting consoles long after onboarding. The team must select a defensible control or assessment. Which repeatable engineering safeguard would most directly reduce recurrence?

  1. For the a supplier and application control assessment at fictional Amberline Manufacturing, automate data-sharing schema checks and periodically reassess third-party retention and access requirements.
  2. For the a supplier and application control assessment at fictional Amberline Manufacturing, enforce dependency review, signed artifact policies, inventory monitoring, and exception expiry in the build pipeline.
  3. For the a supplier and application control assessment at fictional Amberline Manufacturing, maintain a supplier risk register with renewal reviews, evidence expiry dates, breach-notification tests, and documented exit triggers.
  4. For the a supplier and application control assessment at fictional Amberline Manufacturing, review external access quarterly and automatically revoke unused or expired privileged support grants.

Explanation

Writer-proposed answer: D (UNVERIFIED)

Preliminary individual option explanations — NOT expert validated

Correct Answer

D:

External support access is a privileged trust boundary that requires controllable authorization and accountability. Session records show bounded permissions, expiration, approval identity, and independent review of support activity.

Incorrect Answers

A:

This response concerns third-party data processing boundary. Here, a purchased billing platform gives a supplier permanent privileged access to production troubleshooting consoles long after onboarding. The confirming evidence is: Session records show bounded permissions, expiration, approval identity, and independent review of support activity.

B:

Transitive dependency provenance concerns a different operational mechanism. External support access is a privileged trust boundary that requires controllable authorization and accountability.

C:

Focusing on supplier security requirements would leave this problem unresolved: A purchased billing platform gives a supplier permanent privileged access to production troubleshooting consoles long after onboarding.

Question 41

At fictional Goldhaven Robotics, a software-security team is conducting an application release-readiness meeting within a practical least-privilege design. The case observation is: A newly selected identity component is approaching vendor support end while downstream applications depend on its proprietary authentication SDK. The team must select a defensible control or assessment. Which security design action most directly addresses the documented problem?

  1. For the an application release-readiness meeting at fictional Goldhaven Robotics, evaluate supported migration choices, lifecycle dates, compensating controls, and a funded replacement decision before production adoption.
  2. For the an application release-readiness meeting at fictional Goldhaven Robotics, define incident notification channels, escalation timelines, evidence preservation, and shared responsibilities with the supplier.
  3. For the an application release-readiness meeting at fictional Goldhaven Robotics, replace standing access with time-bound, least-privilege support sessions subject to explicit approval and audit logging.
  4. For the an application release-readiness meeting at fictional Goldhaven Robotics, 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:

Product lifecycle and support guarantees are security design inputs, not tasks deferred until a vulnerability appears. Architecture decision records show a supported target, compatibility test results, sunset milestones, and accountable ownership.

Incorrect Answers

B:

Supplier incident escalation concerns a different operational mechanism. Product lifecycle and support guarantees are security design inputs, not tasks deferred until a vulnerability appears.

C:

Focusing on vendor remote-support scope would leave this problem unresolved: A newly selected identity component is approaching vendor support end while downstream applications depend on its proprietary authentication SDK.

D:

Supplier security requirements concerns another aspect of the problem. Product lifecycle and support guarantees are security design inputs, not tasks deferred until a vulnerability appears.

Question 42

At fictional Goldhaven Robotics, a software-security team is conducting an application release-readiness meeting within a practical least-privilege design. The case observation is: A newly selected identity component is approaching vendor support end while downstream applications depend on its proprietary authentication SDK. The team must select a defensible control or assessment. Which independent verification evidence would most directly show that the proposed action succeeded?

  1. For the an application release-readiness meeting at fictional Goldhaven Robotics, an approval record includes license compatibility, supported versions, vulnerability disposition, and named maintenance owner.
  2. For the an application release-readiness meeting at fictional Goldhaven Robotics, architecture decision records show a supported target, compatibility test results, sunset milestones, and accountable ownership.
  3. For the an application release-readiness meeting at fictional Goldhaven Robotics, the reproducible build and software bill of materials identify the complete dependency lineage and a verified approved artifact digest.
  4. For the an application release-readiness meeting at fictional Goldhaven Robotics, 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:

Product lifecycle and support guarantees are security design inputs, not tasks deferred until a vulnerability appears. Architecture decision records show a supported target, compatibility test results, sunset milestones, and accountable ownership.

Incorrect Answers

A:

This response concerns open-source license and security review. Here, a newly selected identity component is approaching vendor support end while downstream applications depend on its proprietary authentication SDK. The confirming evidence is: Architecture decision records show a supported target, compatibility test results, sunset milestones, and accountable ownership.

C:

Focusing on transitive dependency provenance would leave this problem unresolved: A newly selected identity component is approaching vendor support end while downstream applications depend on its proprietary authentication SDK.

D:

Acquired software security testing concerns another aspect of the problem. Product lifecycle and support guarantees are security design inputs, not tasks deferred until a vulnerability appears.

Question 43

At fictional Goldhaven Robotics, a software-security team is conducting an application release-readiness meeting within a practical least-privilege design. The case observation is: A newly selected identity component is approaching vendor support end while downstream applications depend on its proprietary authentication SDK. The team must select a defensible control or assessment. Which secure-design principle best explains the appropriate approach?

  1. For the an application release-readiness meeting at fictional Goldhaven Robotics, vendor claims require evidence proportional to deployment risk and cannot replace configuration-specific assurance.
  2. For the an application release-readiness meeting at fictional Goldhaven Robotics, incident accountability must span contractual and operational boundaries between service consumer and supplier.
  3. For the an application release-readiness meeting at fictional Goldhaven Robotics, product lifecycle and support guarantees are security design inputs, not tasks deferred until a vulnerability appears.
  4. For the an application release-readiness meeting at fictional Goldhaven Robotics, secure acquisition establishes assurance requirements before reliance on software outside the buyer's direct development control.

Explanation

Writer-proposed answer: C (UNVERIFIED)

Preliminary individual option explanations — NOT expert validated

Correct Answer

C:

Product lifecycle and support guarantees are security design inputs, not tasks deferred until a vulnerability appears. Architecture decision records show a supported target, compatibility test results, sunset milestones, and accountable ownership.

Incorrect Answers

A:

This response concerns acquired software security testing. Here, a newly selected identity component is approaching vendor support end while downstream applications depend on its proprietary authentication SDK. The confirming evidence is: Architecture decision records show a supported target, compatibility test results, sunset milestones, and accountable ownership.

B:

Supplier incident escalation concerns a different operational mechanism. Product lifecycle and support guarantees are security design inputs, not tasks deferred until a vulnerability appears.

D:

Supplier security requirements concerns another aspect of the problem. Product lifecycle and support guarantees are security design inputs, not tasks deferred until a vulnerability appears.

Question 44

At fictional Goldhaven Robotics, a software-security team is conducting an application release-readiness meeting within a practical least-privilege design. The case observation is: A newly selected identity component is approaching vendor support end while downstream applications depend on its proprietary authentication SDK. The team must select a defensible control or assessment. Which consequence is most directly associated with leaving this documented problem unresolved?

  1. For the an application release-readiness meeting at fictional Goldhaven Robotics, an untrusted dependency could introduce malicious code or unsupported components into releases without an obvious direct dependency change.
  2. For the an application release-readiness meeting at fictional Goldhaven Robotics, excess personal data may be exposed through a breach or retained beyond legitimate processing needs.
  3. For the an application release-readiness meeting at fictional Goldhaven Robotics, a hidden license conflict or abandoned vulnerable library can disrupt release and create future remediation debt.
  4. For the an application release-readiness meeting at fictional Goldhaven Robotics, unsupported authentication software can remain in critical paths without timely security fixes or a viable rollback.

Explanation

Writer-proposed answer: D (UNVERIFIED)

Preliminary individual option explanations — NOT expert validated

Correct Answer

D:

Product lifecycle and support guarantees are security design inputs, not tasks deferred until a vulnerability appears. Architecture decision records show a supported target, compatibility test results, sunset milestones, and accountable ownership.

Incorrect Answers

A:

This response concerns transitive dependency provenance. Here, a newly selected identity component is approaching vendor support end while downstream applications depend on its proprietary authentication SDK. The confirming evidence is: Architecture decision records show a supported target, compatibility test results, sunset milestones, and accountable ownership.

B:

Third-party data processing boundary concerns a different operational mechanism. Product lifecycle and support guarantees are security design inputs, not tasks deferred until a vulnerability appears.

C:

Focusing on open-source license and security review would leave this problem unresolved: A newly selected identity component is approaching vendor support end while downstream applications depend on its proprietary authentication SDK.

Question 45

At fictional Goldhaven Robotics, a software-security team is conducting an application release-readiness meeting within a practical least-privilege design. The case observation is: A newly selected identity component is approaching vendor support end while downstream applications depend on its proprietary authentication SDK. The team must select a defensible control or assessment. Which repeatable engineering safeguard would most directly reduce recurrence?

  1. For the an application release-readiness meeting at fictional Goldhaven Robotics, track supplier support dates and run migration readiness reviews before components reach end of life.
  2. For the an application release-readiness meeting at fictional Goldhaven Robotics, automate data-sharing schema checks and periodically reassess third-party retention and access requirements.
  3. For the an application release-readiness meeting at fictional Goldhaven Robotics, require versioned component approval with scheduled advisories review and a documented replacement path.
  4. For the an application release-readiness meeting at fictional Goldhaven Robotics, maintain a supplier risk register with renewal reviews, evidence expiry dates, breach-notification tests, and documented exit triggers.

Explanation

Writer-proposed answer: A (UNVERIFIED)

Preliminary individual option explanations — NOT expert validated

Correct Answer

A:

Product lifecycle and support guarantees are security design inputs, not tasks deferred until a vulnerability appears. Architecture decision records show a supported target, compatibility test results, sunset milestones, and accountable ownership.

Incorrect Answers

B:

Third-party data processing boundary concerns a different operational mechanism. Product lifecycle and support guarantees are security design inputs, not tasks deferred until a vulnerability appears.

C:

Focusing on open-source license and security review would leave this problem unresolved: A newly selected identity component is approaching vendor support end while downstream applications depend on its proprietary authentication SDK.

D:

Supplier security requirements concerns another aspect of the problem. Product lifecycle and support guarantees are security design inputs, not tasks deferred until a vulnerability appears.

Question 46

At fictional Northwick Labs, a software-security team is conducting a new feature threat-model workshop with an auditable vulnerability remediation process. The case observation is: A newly selected identity component is approaching vendor support end while downstream applications depend on its proprietary authentication SDK. The team must select a defensible control or assessment. Which security design action most directly addresses the documented problem?

  1. For the a new feature threat-model workshop at fictional Northwick Labs, define verifiable vendor security requirements and contractual acceptance criteria before purchasing the service.
  2. For the a new feature threat-model workshop at fictional Northwick Labs, evaluate supported migration choices, lifecycle dates, compensating controls, and a funded replacement decision before production adoption.
  3. For the a new feature threat-model workshop at fictional Northwick Labs, establish a risk-based evaluation using authoritative attestation, configuration review, a scoped technical assessment, and documented exceptions.
  4. For the a new feature threat-model workshop at fictional Northwick Labs, define incident notification channels, escalation timelines, evidence preservation, and shared responsibilities with the supplier.

Explanation

Writer-proposed answer: B (UNVERIFIED)

Preliminary individual option explanations — NOT expert validated

Correct Answer

B:

Product lifecycle and support guarantees are security design inputs, not tasks deferred until a vulnerability appears. Architecture decision records show a supported target, compatibility test results, sunset milestones, and accountable ownership.

Incorrect Answers

A:

This response concerns supplier security requirements. Here, a newly selected identity component is approaching vendor support end while downstream applications depend on its proprietary authentication SDK. The confirming evidence is: Architecture decision records show a supported target, compatibility test results, sunset milestones, and accountable ownership.

C:

Focusing on acquired software security testing would leave this problem unresolved: A newly selected identity component is approaching vendor support end while downstream applications depend on its proprietary authentication SDK.

D:

Supplier incident escalation concerns another aspect of the problem. Product lifecycle and support guarantees are security design inputs, not tasks deferred until a vulnerability appears.

Question 47

At fictional Northwick Labs, a software-security team is conducting a new feature threat-model workshop with an auditable vulnerability remediation process. The case observation is: A newly selected identity component is approaching vendor support end while downstream applications depend on its proprietary authentication SDK. The team must select a defensible control or assessment. Which independent verification evidence would most directly show that the proposed action succeeded?

  1. For the a new feature threat-model workshop at fictional Northwick Labs, session records show bounded permissions, expiration, approval identity, and independent review of support activity.
  2. For the a new feature threat-model workshop at fictional Northwick Labs, the reproducible build and software bill of materials identify the complete dependency lineage and a verified approved artifact digest.
  3. For the a new feature threat-model workshop at fictional Northwick Labs, architecture decision records show a supported target, compatibility test results, sunset milestones, and accountable ownership.
  4. For the a new feature threat-model workshop at fictional Northwick Labs, 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:

Product lifecycle and support guarantees are security design inputs, not tasks deferred until a vulnerability appears. Architecture decision records show a supported target, compatibility test results, sunset milestones, and accountable ownership.

Incorrect Answers

A:

This response concerns vendor remote-support scope. Here, a newly selected identity component is approaching vendor support end while downstream applications depend on its proprietary authentication SDK. The confirming evidence is: Architecture decision records show a supported target, compatibility test results, sunset milestones, and accountable ownership.

B:

Transitive dependency provenance concerns a different operational mechanism. Product lifecycle and support guarantees are security design inputs, not tasks deferred until a vulnerability appears.

D:

Supplier security requirements concerns another aspect of the problem. Product lifecycle and support guarantees are security design inputs, not tasks deferred until a vulnerability appears.

Question 48

At fictional Northwick Labs, a software-security team is conducting a new feature threat-model workshop with an auditable vulnerability remediation process. The case observation is: A newly selected identity component is approaching vendor support end while downstream applications depend on its proprietary authentication SDK. The team must select a defensible control or assessment. Which secure-design principle best explains the appropriate approach?

  1. For the a new feature threat-model workshop at fictional Northwick Labs, incident accountability must span contractual and operational boundaries between service consumer and supplier.
  2. For the a new feature threat-model workshop at fictional Northwick Labs, provenance and dependency inventory reduce software supply-chain uncertainty but do not by themselves prove a component is vulnerability-free.
  3. For the a new feature threat-model workshop at fictional Northwick Labs, external support access is a privileged trust boundary that requires controllable authorization and accountability.
  4. For the a new feature threat-model workshop at fictional Northwick Labs, product lifecycle and support guarantees are security design inputs, not tasks deferred until a vulnerability appears.

Explanation

Writer-proposed answer: D (UNVERIFIED)

Preliminary individual option explanations — NOT expert validated

Correct Answer

D:

Product lifecycle and support guarantees are security design inputs, not tasks deferred until a vulnerability appears. Architecture decision records show a supported target, compatibility test results, sunset milestones, and accountable ownership.

Incorrect Answers

A:

This response concerns supplier incident escalation. Here, a newly selected identity component is approaching vendor support end while downstream applications depend on its proprietary authentication SDK. The confirming evidence is: Architecture decision records show a supported target, compatibility test results, sunset milestones, and accountable ownership.

B:

Transitive dependency provenance concerns a different operational mechanism. Product lifecycle and support guarantees are security design inputs, not tasks deferred until a vulnerability appears.

C:

Focusing on vendor remote-support scope would leave this problem unresolved: A newly selected identity component is approaching vendor support end while downstream applications depend on its proprietary authentication SDK.

Question 49

At fictional Northwick Labs, a software-security team is conducting a new feature threat-model workshop with an auditable vulnerability remediation process. The case observation is: A newly selected identity component is approaching vendor support end while downstream applications depend on its proprietary authentication SDK. The team must select a defensible control or assessment. Which consequence is most directly associated with leaving this documented problem unresolved?

  1. For the a new feature threat-model workshop at fictional Northwick Labs, unsupported authentication software can remain in critical paths without timely security fixes or a viable rollback.
  2. For the a new feature threat-model workshop at fictional Northwick Labs, a hidden license conflict or abandoned vulnerable library can disrupt release and create future remediation debt.
  3. For the a new feature threat-model workshop at fictional Northwick Labs, late or unreliable notification may delay containment, breach assessment, and regulatory decisions.
  4. For the a new feature threat-model workshop at fictional Northwick Labs, the organization may deploy insecure defaults that supplier certifications did not evaluate.

Explanation

Writer-proposed answer: A (UNVERIFIED)

Preliminary individual option explanations — NOT expert validated

Correct Answer

A:

Product lifecycle and support guarantees are security design inputs, not tasks deferred until a vulnerability appears. Architecture decision records show a supported target, compatibility test results, sunset milestones, and accountable ownership.

Incorrect Answers

B:

Open-source license and security review concerns a different operational mechanism. Product lifecycle and support guarantees are security design inputs, not tasks deferred until a vulnerability appears.

C:

Focusing on supplier incident escalation would leave this problem unresolved: A newly selected identity component is approaching vendor support end while downstream applications depend on its proprietary authentication SDK.

D:

Acquired software security testing concerns another aspect of the problem. Product lifecycle and support guarantees are security design inputs, not tasks deferred until a vulnerability appears.

Question 50

At fictional Northwick Labs, a software-security team is conducting a new feature threat-model workshop with an auditable vulnerability remediation process. The case observation is: A newly selected identity component is approaching vendor support end while downstream applications depend on its proprietary authentication SDK. The team must select a defensible control or assessment. Which repeatable engineering safeguard would most directly reduce recurrence?

  1. For the a new feature threat-model workshop at fictional Northwick Labs, repeat technical assurance after major vendor releases or configuration and integration changes.
  2. For the a new feature threat-model workshop at fictional Northwick Labs, track supplier support dates and run migration readiness reviews before components reach end of life.
  3. For the a new feature threat-model workshop at fictional Northwick Labs, automate data-sharing schema checks and periodically reassess third-party retention and access requirements.
  4. For the a new feature threat-model workshop at fictional Northwick Labs, 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:

Product lifecycle and support guarantees are security design inputs, not tasks deferred until a vulnerability appears. Architecture decision records show a supported target, compatibility test results, sunset milestones, and accountable ownership.

Incorrect Answers

A:

This response concerns acquired software security testing. Here, a newly selected identity component is approaching vendor support end while downstream applications depend on its proprietary authentication SDK. The confirming evidence is: Architecture decision records show a supported target, compatibility test results, sunset milestones, and accountable ownership.

C:

Focusing on third-party data processing boundary would leave this problem unresolved: A newly selected identity component is approaching vendor support end while downstream applications depend on its proprietary authentication SDK.

D:

Supplier security requirements concerns another aspect of the problem. Product lifecycle and support guarantees are security design inputs, not tasks deferred until a vulnerability appears.

Secure Software Design (KEO1) Practice Tests