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 57

Question 560

At fictional Elmcrest Freight, a software-security team is conducting a secure acquisition and deployment review without interrupting essential service availability. The case observation is: A scanner assigns a high CVSS score to a library issue even though the vulnerable path is unreachable in this product, while an overlooked lower-scored flaw exposes customer data. The team must select a defensible control or assessment. Which repeatable engineering safeguard would most directly reduce recurrence?

  1. For the a secure acquisition and deployment review at fictional Elmcrest Freight, use risk-based triage workflows and sample low-confidence findings for recurring patterns.
  2. For the a secure acquisition and deployment review at fictional Elmcrest Freight, version the permission matrix with policy changes and block merges on privileged regression failures.
  3. For the a secure acquisition and deployment review at fictional Elmcrest Freight, map each high-risk threat scenario to automated negative tests during design review.
  4. For the a secure acquisition and deployment review at fictional Elmcrest Freight, refresh prioritization as attack conditions, product usage, and vulnerability intelligence change.

Explanation

Writer-proposed answer: D (UNVERIFIED)

Preliminary individual option explanations — NOT expert validated

Correct Answer

D:

Generic severity scores aid prioritization but product-specific risk requires context and reachability. The risk register explains affected code paths and business impact, with reproducible evidence for remediation order.

Incorrect Answers

A:

This response concerns sast and dast interpretation. Here, a scanner assigns a high CVSS score to a library issue even though the vulnerable path is unreachable in this product, while an overlooked lower-scored flaw exposes customer data. The confirming evidence is: The risk register explains affected code paths and business impact, with reproducible evidence for remediation order.

B:

Authorization regression matrix concerns a different operational mechanism. Generic severity scores aid prioritization but product-specific risk requires context and reachability.

C:

Focusing on threat-based security test design would leave this problem unresolved: A scanner assigns a high CVSS score to a library issue even though the vulnerable path is unreachable in this product, while an overlooked lower-scored flaw exposes customer data.

Question 561

At fictional Kingsgate Mutual, a software-security team is conducting a new feature threat-model workshop within the approved release and rollback constraints. The case observation is: A pull-request build from an untrusted fork can access deployment tokens and production signing credentials. 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 Kingsgate Mutual, separate untrusted build execution from privileged release jobs and grant ephemeral tokens only to reviewed protected workflows.
  2. For the a new feature threat-model workshop at fictional Kingsgate Mutual, use a curated dependency registry, pinned versions, integrity verification and minimal build environment privileges.
  3. For the a new feature threat-model workshop at fictional Kingsgate Mutual, create scoped, expiring exceptions with recorded risk ownership while keeping global admission controls enforced.
  4. For the a new feature threat-model workshop at fictional Kingsgate Mutual, move secrets into managed runtime injection with access-scoped workload identity and rotate committed credentials.

Explanation

Writer-proposed answer: A (UNVERIFIED)

Preliminary individual option explanations — NOT expert validated

Correct Answer

A:

CI/CD pipelines are privileged software supply-chain systems requiring explicit trust boundaries. Untrusted contributions cannot access release secrets, while approved builds still publish traceable signed artifacts.

Incorrect Answers

B:

Pipeline dependency trust concerns a different operational mechanism. CI/CD pipelines are privileged software supply-chain systems requiring explicit trust boundaries.

C:

Focusing on automated security policy exception would leave this problem unresolved: A pull-request build from an untrusted fork can access deployment tokens and production signing credentials.

D:

Runtime secret injection concerns another aspect of the problem. CI/CD pipelines are privileged software supply-chain systems requiring explicit trust boundaries.

Question 562

At fictional Kingsgate Mutual, a software-security team is conducting a new feature threat-model workshop within the approved release and rollback constraints. The case observation is: A pull-request build from an untrusted fork can access deployment tokens and production signing credentials. 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 Kingsgate Mutual, admission tests reject unscanned images outside the approved narrow exception and automatically restore enforcement at expiry.
  2. For the a new feature threat-model workshop at fictional Kingsgate Mutual, untrusted contributions cannot access release secrets, while approved builds still publish traceable signed artifacts.
  3. For the a new feature threat-model workshop at fictional Kingsgate Mutual, repository scans are clean, service startup retrieves scoped secrets, and former committed keys are invalid.
  4. For the a new feature threat-model workshop at fictional Kingsgate Mutual, deployment logs bind commit, builder identity, signed digest, and running workload artifact across environments.

Explanation

Writer-proposed answer: B (UNVERIFIED)

Preliminary individual option explanations — NOT expert validated

Correct Answer

B:

CI/CD pipelines are privileged software supply-chain systems requiring explicit trust boundaries. Untrusted contributions cannot access release secrets, while approved builds still publish traceable signed artifacts.

Incorrect Answers

A:

This response concerns automated security policy exception. Here, a pull-request build from an untrusted fork can access deployment tokens and production signing credentials. The confirming evidence is: Untrusted contributions cannot access release secrets, while approved builds still publish traceable signed artifacts.

C:

Focusing on runtime secret injection would leave this problem unresolved: A pull-request build from an untrusted fork can access deployment tokens and production signing credentials.

D:

Build artifact provenance concerns another aspect of the problem. CI/CD pipelines are privileged software supply-chain systems requiring explicit trust boundaries.

Question 563

At fictional Kingsgate Mutual, a software-security team is conducting a new feature threat-model workshop within the approved release and rollback constraints. The case observation is: A pull-request build from an untrusted fork can access deployment tokens and production signing credentials. 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 Kingsgate Mutual, declarative desired state is not protection unless effective deployed state is monitored and enforced.
  2. For the a new feature threat-model workshop at fictional Kingsgate Mutual, reproducible provenance limits substitution risks between build and deployment.
  3. For the a new feature threat-model workshop at fictional Kingsgate Mutual, cI/CD pipelines are privileged software supply-chain systems requiring explicit trust boundaries.
  4. For the a new feature threat-model workshop at fictional Kingsgate Mutual, build tools are part of the trusted computing base and deserve supply-chain governance.

Explanation

Writer-proposed answer: C (UNVERIFIED)

Preliminary individual option explanations — NOT expert validated

Correct Answer

C:

CI/CD pipelines are privileged software supply-chain systems requiring explicit trust boundaries. Untrusted contributions cannot access release secrets, while approved builds still publish traceable signed artifacts.

Incorrect Answers

A:

This response concerns infrastructure as code drift. Here, a pull-request build from an untrusted fork can access deployment tokens and production signing credentials. The confirming evidence is: Untrusted contributions cannot access release secrets, while approved builds still publish traceable signed artifacts.

B:

Build artifact provenance concerns a different operational mechanism. CI/CD pipelines are privileged software supply-chain systems requiring explicit trust boundaries.

D:

Pipeline dependency trust concerns another aspect of the problem. CI/CD pipelines are privileged software supply-chain systems requiring explicit trust boundaries.

Question 564

At fictional Kingsgate Mutual, a software-security team is conducting a new feature threat-model workshop within the approved release and rollback constraints. The case observation is: A pull-request build from an untrusted fork can access deployment tokens and production signing credentials. 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 Kingsgate Mutual, a weaker staging host may become a path to production compromise.
  2. For the a new feature threat-model workshop at fictional Kingsgate Mutual, a stolen signing key can make malicious artifacts appear authentic.
  3. For the a new feature threat-model workshop at fictional Kingsgate Mutual, a malicious build dependency may compromise source, secrets or release artifacts.
  4. For the a new feature threat-model workshop at fictional Kingsgate Mutual, malicious contributions may exfiltrate credentials and publish compromised releases.

Explanation

Writer-proposed answer: D (UNVERIFIED)

Preliminary individual option explanations — NOT expert validated

Correct Answer

D:

CI/CD pipelines are privileged software supply-chain systems requiring explicit trust boundaries. Untrusted contributions cannot access release secrets, while approved builds still publish traceable signed artifacts.

Incorrect Answers

A:

This response concerns environment segregation. Here, a pull-request build from an untrusted fork can access deployment tokens and production signing credentials. The confirming evidence is: Untrusted contributions cannot access release secrets, while approved builds still publish traceable signed artifacts.

B:

Release signing identity concerns a different operational mechanism. CI/CD pipelines are privileged software supply-chain systems requiring explicit trust boundaries.

C:

Focusing on pipeline dependency trust would leave this problem unresolved: A pull-request build from an untrusted fork can access deployment tokens and production signing credentials.

Question 565

At fictional Kingsgate Mutual, a software-security team is conducting a new feature threat-model workshop within the approved release and rollback constraints. The case observation is: A pull-request build from an untrusted fork can access deployment tokens and production signing credentials. 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 Kingsgate Mutual, enforce protected branches, scoped runners, short-lived credentials and pipeline security tests.
  2. For the a new feature threat-model workshop at fictional Kingsgate Mutual, continuously verify artifact signatures and prohibit unpinned production dependencies.
  3. For the a new feature threat-model workshop at fictional Kingsgate Mutual, test isolation controls and review environment role trust policies after platform changes.
  4. For the a new feature threat-model workshop at fictional Kingsgate Mutual, schedule drift checks and block insecure manual changes with policy as code.

Explanation

Writer-proposed answer: A (UNVERIFIED)

Preliminary individual option explanations — NOT expert validated

Correct Answer

A:

CI/CD pipelines are privileged software supply-chain systems requiring explicit trust boundaries. Untrusted contributions cannot access release secrets, while approved builds still publish traceable signed artifacts.

Incorrect Answers

B:

Build artifact provenance concerns a different operational mechanism. CI/CD pipelines are privileged software supply-chain systems requiring explicit trust boundaries.

C:

Focusing on environment segregation would leave this problem unresolved: A pull-request build from an untrusted fork can access deployment tokens and production signing credentials.

D:

Infrastructure as code drift concerns another aspect of the problem. CI/CD pipelines are privileged software supply-chain systems requiring explicit trust boundaries.

Question 566

At fictional Riverwick Foundation, a software-security team is conducting a quarterly architecture change assessment while preserving independent evidence of control effectiveness. The case observation is: A pull-request build from an untrusted fork can access deployment tokens and production signing credentials. The team must select a defensible control or assessment. Which security design action most directly addresses the documented problem?

  1. For the a quarterly architecture change assessment at fictional Riverwick Foundation, move secrets into managed runtime injection with access-scoped workload identity and rotate committed credentials.
  2. For the a quarterly architecture change assessment at fictional Riverwick Foundation, separate untrusted build execution from privileged release jobs and grant ephemeral tokens only to reviewed protected workflows.
  3. For the a quarterly architecture change assessment at fictional Riverwick Foundation, pin images by digest, verify approved attestations and signatures, and preserve release-to-source traceability.
  4. For the a quarterly architecture change assessment at fictional Riverwick Foundation, use isolated signing identities, restricted release authorization, short-lived credentials where supported, and auditable signing evidence.

Explanation

Writer-proposed answer: B (UNVERIFIED)

Preliminary individual option explanations — NOT expert validated

Correct Answer

B:

CI/CD pipelines are privileged software supply-chain systems requiring explicit trust boundaries. Untrusted contributions cannot access release secrets, while approved builds still publish traceable signed artifacts.

Incorrect Answers

A:

This response concerns runtime secret injection. Here, a pull-request build from an untrusted fork can access deployment tokens and production signing credentials. The confirming evidence is: Untrusted contributions cannot access release secrets, while approved builds still publish traceable signed artifacts.

C:

Focusing on build artifact provenance would leave this problem unresolved: A pull-request build from an untrusted fork can access deployment tokens and production signing credentials.

D:

Release signing identity concerns another aspect of the problem. CI/CD pipelines are privileged software supply-chain systems requiring explicit trust boundaries.

Question 567

At fictional Riverwick Foundation, a software-security team is conducting a quarterly architecture change assessment while preserving independent evidence of control effectiveness. The case observation is: A pull-request build from an untrusted fork can access deployment tokens and production signing credentials. 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 quarterly architecture change assessment at fictional Riverwick Foundation, a signed release can be traced to approved build provenance without exposing the signing credential to ordinary jobs.
  2. For the a quarterly architecture change assessment at fictional Riverwick Foundation, admission tests reject unscanned images outside the approved narrow exception and automatically restore enforcement at expiry.
  3. For the a quarterly architecture change assessment at fictional Riverwick Foundation, untrusted contributions cannot access release secrets, while approved builds still publish traceable signed artifacts.
  4. For the a quarterly architecture change assessment at fictional Riverwick Foundation, continuous configuration assessment reports no unauthorized public access and records the corrective deployment.

Explanation

Writer-proposed answer: C (UNVERIFIED)

Preliminary individual option explanations — NOT expert validated

Correct Answer

C:

CI/CD pipelines are privileged software supply-chain systems requiring explicit trust boundaries. Untrusted contributions cannot access release secrets, while approved builds still publish traceable signed artifacts.

Incorrect Answers

A:

This response concerns release signing identity. Here, a pull-request build from an untrusted fork can access deployment tokens and production signing credentials. The confirming evidence is: Untrusted contributions cannot access release secrets, while approved builds still publish traceable signed artifacts.

B:

Automated security policy exception concerns a different operational mechanism. CI/CD pipelines are privileged software supply-chain systems requiring explicit trust boundaries.

D:

Infrastructure as code drift concerns another aspect of the problem. CI/CD pipelines are privileged software supply-chain systems requiring explicit trust boundaries.

Question 568

At fictional Riverwick Foundation, a software-security team is conducting a quarterly architecture change assessment while preserving independent evidence of control effectiveness. The case observation is: A pull-request build from an untrusted fork can access deployment tokens and production signing credentials. The team must select a defensible control or assessment. Which secure-design principle best explains the appropriate approach?

  1. For the a quarterly architecture change assessment at fictional Riverwick Foundation, build tools are part of the trusted computing base and deserve supply-chain governance.
  2. For the a quarterly architecture change assessment at fictional Riverwick Foundation, secrets should be managed by an access-controlled lifecycle rather than source-control distribution.
  3. For the a quarterly architecture change assessment at fictional Riverwick Foundation, reproducible provenance limits substitution risks between build and deployment.
  4. For the a quarterly architecture change assessment at fictional Riverwick Foundation, cI/CD pipelines are privileged software supply-chain systems requiring explicit trust boundaries.

Explanation

Writer-proposed answer: D (UNVERIFIED)

Preliminary individual option explanations — NOT expert validated

Correct Answer

D:

CI/CD pipelines are privileged software supply-chain systems requiring explicit trust boundaries. Untrusted contributions cannot access release secrets, while approved builds still publish traceable signed artifacts.

Incorrect Answers

A:

This response concerns pipeline dependency trust. Here, a pull-request build from an untrusted fork can access deployment tokens and production signing credentials. The confirming evidence is: Untrusted contributions cannot access release secrets, while approved builds still publish traceable signed artifacts.

B:

Runtime secret injection concerns a different operational mechanism. CI/CD pipelines are privileged software supply-chain systems requiring explicit trust boundaries.

C:

Focusing on build artifact provenance would leave this problem unresolved: A pull-request build from an untrusted fork can access deployment tokens and production signing credentials.

Question 569

At fictional Riverwick Foundation, a software-security team is conducting a quarterly architecture change assessment while preserving independent evidence of control effectiveness. The case observation is: A pull-request build from an untrusted fork can access deployment tokens and production signing credentials. 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 quarterly architecture change assessment at fictional Riverwick Foundation, malicious contributions may exfiltrate credentials and publish compromised releases.
  2. For the a quarterly architecture change assessment at fictional Riverwick Foundation, a broad override can permit unrelated vulnerable or untrusted software to launch.
  3. For the a quarterly architecture change assessment at fictional Riverwick Foundation, sensitive objects can be exposed even when repository templates look secure.
  4. For the a quarterly architecture change assessment at fictional Riverwick Foundation, an attacker or accidental tag update may replace the intended release without changing deployment configuration.

Explanation

Writer-proposed answer: A (UNVERIFIED)

Preliminary individual option explanations — NOT expert validated

Correct Answer

A:

CI/CD pipelines are privileged software supply-chain systems requiring explicit trust boundaries. Untrusted contributions cannot access release secrets, while approved builds still publish traceable signed artifacts.

Incorrect Answers

B:

Automated security policy exception concerns a different operational mechanism. CI/CD pipelines are privileged software supply-chain systems requiring explicit trust boundaries.

C:

Focusing on infrastructure as code drift would leave this problem unresolved: A pull-request build from an untrusted fork can access deployment tokens and production signing credentials.

D:

Build artifact provenance concerns another aspect of the problem. CI/CD pipelines are privileged software supply-chain systems requiring explicit trust boundaries.

Question 570

At fictional Riverwick Foundation, a software-security team is conducting a quarterly architecture change assessment while preserving independent evidence of control effectiveness. The case observation is: A pull-request build from an untrusted fork can access deployment tokens and production signing credentials. The team must select a defensible control or assessment. Which repeatable engineering safeguard would most directly reduce recurrence?

  1. For the a quarterly architecture change assessment at fictional Riverwick Foundation, schedule drift checks and block insecure manual changes with policy as code.
  2. For the a quarterly architecture change assessment at fictional Riverwick Foundation, enforce protected branches, scoped runners, short-lived credentials and pipeline security tests.
  3. For the a quarterly architecture change assessment at fictional Riverwick Foundation, rotate and audit signing credentials and test that nonrelease jobs cannot produce trusted signatures.
  4. For the a quarterly architecture change assessment at fictional Riverwick Foundation, continuously verify artifact signatures and prohibit unpinned production dependencies.

Explanation

Writer-proposed answer: B (UNVERIFIED)

Preliminary individual option explanations — NOT expert validated

Correct Answer

B:

CI/CD pipelines are privileged software supply-chain systems requiring explicit trust boundaries. Untrusted contributions cannot access release secrets, while approved builds still publish traceable signed artifacts.

Incorrect Answers

A:

This response concerns infrastructure as code drift. Here, a pull-request build from an untrusted fork can access deployment tokens and production signing credentials. The confirming evidence is: Untrusted contributions cannot access release secrets, while approved builds still publish traceable signed artifacts.

C:

Focusing on release signing identity would leave this problem unresolved: A pull-request build from an untrusted fork can access deployment tokens and production signing credentials.

D:

Build artifact provenance concerns another aspect of the problem. CI/CD pipelines are privileged software supply-chain systems requiring explicit trust boundaries.

Secure Software Design (KEO1) Practice Tests