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 58

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.

Question 571

At fictional Yarrow Valley Clinics, a software-security team is conducting a secure acquisition and deployment review while protecting cross-tenant boundaries. The case observation is: A deployment job downloads a container image by mutable latest tag without checking its origin or digest. The team must select a defensible control or assessment. Which security design action most directly addresses the documented problem?

  1. For the a secure acquisition and deployment review at fictional Yarrow Valley Clinics, move secrets into managed runtime injection with access-scoped workload identity and rotate committed credentials.
  2. For the a secure acquisition and deployment review at fictional Yarrow Valley Clinics, detect live-versus-declared configuration drift and restore least-privilege policy through controlled change.
  3. For the a secure acquisition and deployment review at fictional Yarrow Valley Clinics, pin images by digest, verify approved attestations and signatures, and preserve release-to-source traceability.
  4. For the a secure acquisition and deployment review at fictional Yarrow Valley Clinics, separate untrusted build execution from privileged release jobs and grant ephemeral tokens only to reviewed protected workflows.

Explanation

Writer-proposed answer: C (UNVERIFIED)

Preliminary individual option explanations — NOT expert validated

Correct Answer

C:

Reproducible provenance limits substitution risks between build and deployment. Deployment logs bind commit, builder identity, signed digest, and running workload artifact across environments.

Incorrect Answers

A:

This response concerns runtime secret injection. Here, a deployment job downloads a container image by mutable latest tag without checking its origin or digest. The confirming evidence is: Deployment logs bind commit, builder identity, signed digest, and running workload artifact across environments.

B:

Infrastructure as code drift concerns a different operational mechanism. Reproducible provenance limits substitution risks between build and deployment.

D:

Protected ci secrets concerns another aspect of the problem. Reproducible provenance limits substitution risks between build and deployment.

Question 572

At fictional Yarrow Valley Clinics, a software-security team is conducting a secure acquisition and deployment review while protecting cross-tenant boundaries. The case observation is: A deployment job downloads a container image by mutable latest tag without checking its origin or digest. 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 secure acquisition and deployment review at fictional Yarrow Valley Clinics, a signed release can be traced to approved build provenance without exposing the signing credential to ordinary jobs.
  2. For the a secure acquisition and deployment review at fictional Yarrow Valley Clinics, admission tests reject unscanned images outside the approved narrow exception and automatically restore enforcement at expiry.
  3. For the a secure acquisition and deployment review at fictional Yarrow Valley Clinics, untrusted contributions cannot access release secrets, while approved builds still publish traceable signed artifacts.
  4. For the a secure acquisition and deployment review at fictional Yarrow Valley Clinics, deployment logs bind commit, builder identity, signed digest, and running workload artifact across environments.

Explanation

Writer-proposed answer: D (UNVERIFIED)

Preliminary individual option explanations — NOT expert validated

Correct Answer

D:

Reproducible provenance limits substitution risks between build and deployment. Deployment logs bind commit, builder identity, signed digest, and running workload artifact across environments.

Incorrect Answers

A:

This response concerns release signing identity. Here, a deployment job downloads a container image by mutable latest tag without checking its origin or digest. The confirming evidence is: Deployment logs bind commit, builder identity, signed digest, and running workload artifact across environments.

B:

Automated security policy exception concerns a different operational mechanism. Reproducible provenance limits substitution risks between build and deployment.

C:

Focusing on protected ci secrets would leave this problem unresolved: A deployment job downloads a container image by mutable latest tag without checking its origin or digest.

Question 573

At fictional Yarrow Valley Clinics, a software-security team is conducting a secure acquisition and deployment review while protecting cross-tenant boundaries. The case observation is: A deployment job downloads a container image by mutable latest tag without checking its origin or digest. The team must select a defensible control or assessment. Which secure-design principle best explains the appropriate approach?

  1. For the a secure acquisition and deployment review at fictional Yarrow Valley Clinics, reproducible provenance limits substitution risks between build and deployment.
  2. For the a secure acquisition and deployment review at fictional Yarrow Valley Clinics, build tools are part of the trusted computing base and deserve supply-chain governance.
  3. For the a secure acquisition and deployment review at fictional Yarrow Valley Clinics, environment boundaries limit blast radius and preserve independent trust and change control.
  4. For the a secure acquisition and deployment review at fictional Yarrow Valley Clinics, cI/CD pipelines are privileged software supply-chain systems requiring explicit trust boundaries.

Explanation

Writer-proposed answer: A (UNVERIFIED)

Preliminary individual option explanations — NOT expert validated

Correct Answer

A:

Reproducible provenance limits substitution risks between build and deployment. Deployment logs bind commit, builder identity, signed digest, and running workload artifact across environments.

Incorrect Answers

B:

Pipeline dependency trust concerns a different operational mechanism. Reproducible provenance limits substitution risks between build and deployment.

C:

Focusing on environment segregation would leave this problem unresolved: A deployment job downloads a container image by mutable latest tag without checking its origin or digest.

D:

Protected ci secrets concerns another aspect of the problem. Reproducible provenance limits substitution risks between build and deployment.

Question 574

At fictional Yarrow Valley Clinics, a software-security team is conducting a secure acquisition and deployment review while protecting cross-tenant boundaries. The case observation is: A deployment job downloads a container image by mutable latest tag without checking its origin or digest. 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 secure acquisition and deployment review at fictional Yarrow Valley Clinics, a broad override can permit unrelated vulnerable or untrusted software to launch.
  2. For the a secure acquisition and deployment review at fictional Yarrow Valley Clinics, an attacker or accidental tag update may replace the intended release without changing deployment configuration.
  3. For the a secure acquisition and deployment review at fictional Yarrow Valley Clinics, a malicious build dependency may compromise source, secrets or release artifacts.
  4. For the a secure acquisition and deployment review at fictional Yarrow Valley Clinics, malicious contributions may exfiltrate credentials and publish compromised releases.

Explanation

Writer-proposed answer: B (UNVERIFIED)

Preliminary individual option explanations — NOT expert validated

Correct Answer

B:

Reproducible provenance limits substitution risks between build and deployment. Deployment logs bind commit, builder identity, signed digest, and running workload artifact across environments.

Incorrect Answers

A:

This response concerns automated security policy exception. Here, a deployment job downloads a container image by mutable latest tag without checking its origin or digest. The confirming evidence is: Deployment logs bind commit, builder identity, signed digest, and running workload artifact across environments.

C:

Focusing on pipeline dependency trust would leave this problem unresolved: A deployment job downloads a container image by mutable latest tag without checking its origin or digest.

D:

Protected ci secrets concerns another aspect of the problem. Reproducible provenance limits substitution risks between build and deployment.

Question 575

At fictional Yarrow Valley Clinics, a software-security team is conducting a secure acquisition and deployment review while protecting cross-tenant boundaries. The case observation is: A deployment job downloads a container image by mutable latest tag without checking its origin or digest. 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 Yarrow Valley Clinics, schedule drift checks and block insecure manual changes with policy as code.
  2. For the a secure acquisition and deployment review at fictional Yarrow Valley Clinics, enforce protected branches, scoped runners, short-lived credentials and pipeline security tests.
  3. For the a secure acquisition and deployment review at fictional Yarrow Valley Clinics, continuously verify artifact signatures and prohibit unpinned production dependencies.
  4. For the a secure acquisition and deployment review at fictional Yarrow Valley Clinics, test isolation controls and review environment role trust policies after platform changes.

Explanation

Writer-proposed answer: C (UNVERIFIED)

Preliminary individual option explanations — NOT expert validated

Correct Answer

C:

Reproducible provenance limits substitution risks between build and deployment. Deployment logs bind commit, builder identity, signed digest, and running workload artifact across environments.

Incorrect Answers

A:

This response concerns infrastructure as code drift. Here, a deployment job downloads a container image by mutable latest tag without checking its origin or digest. The confirming evidence is: Deployment logs bind commit, builder identity, signed digest, and running workload artifact across environments.

B:

Protected ci secrets concerns a different operational mechanism. Reproducible provenance limits substitution risks between build and deployment.

D:

Environment segregation concerns another aspect of the problem. Reproducible provenance limits substitution risks between build and deployment.

Question 576

At fictional Foxham Utilities, a software-security team is conducting a DevSecOps security control gate within a practical least-privilege design. The case observation is: A deployment job downloads a container image by mutable latest tag without checking its origin or digest. The team must select a defensible control or assessment. Which security design action most directly addresses the documented problem?

  1. For the a DevSecOps security control gate at fictional Foxham Utilities, separate environment identities, accounts or boundaries and enforce explicit cross-environment denial.
  2. For the a DevSecOps security control gate at fictional Foxham Utilities, move secrets into managed runtime injection with access-scoped workload identity and rotate committed credentials.
  3. For the a DevSecOps security control gate at fictional Foxham Utilities, use isolated signing identities, restricted release authorization, short-lived credentials where supported, and auditable signing evidence.
  4. For the a DevSecOps security control gate at fictional Foxham Utilities, pin images by digest, verify approved attestations and signatures, and preserve release-to-source traceability.

Explanation

Writer-proposed answer: D (UNVERIFIED)

Preliminary individual option explanations — NOT expert validated

Correct Answer

D:

Reproducible provenance limits substitution risks between build and deployment. Deployment logs bind commit, builder identity, signed digest, and running workload artifact across environments.

Incorrect Answers

A:

This response concerns environment segregation. Here, a deployment job downloads a container image by mutable latest tag without checking its origin or digest. The confirming evidence is: Deployment logs bind commit, builder identity, signed digest, and running workload artifact across environments.

B:

Runtime secret injection concerns a different operational mechanism. Reproducible provenance limits substitution risks between build and deployment.

C:

Focusing on release signing identity would leave this problem unresolved: A deployment job downloads a container image by mutable latest tag without checking its origin or digest.

Question 577

At fictional Foxham Utilities, a software-security team is conducting a DevSecOps security control gate within a practical least-privilege design. The case observation is: A deployment job downloads a container image by mutable latest tag without checking its origin or digest. 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 DevSecOps security control gate at fictional Foxham Utilities, deployment logs bind commit, builder identity, signed digest, and running workload artifact across environments.
  2. For the a DevSecOps security control gate at fictional Foxham Utilities, untrusted contributions cannot access release secrets, while approved builds still publish traceable signed artifacts.
  3. For the a DevSecOps security control gate at fictional Foxham Utilities, continuous configuration assessment reports no unauthorized public access and records the corrective deployment.
  4. For the a DevSecOps security control gate at fictional Foxham Utilities, rebuilt releases use approved package digests and cannot fetch unreviewed pipeline tooling.

Explanation

Writer-proposed answer: A (UNVERIFIED)

Preliminary individual option explanations — NOT expert validated

Correct Answer

A:

Reproducible provenance limits substitution risks between build and deployment. Deployment logs bind commit, builder identity, signed digest, and running workload artifact across environments.

Incorrect Answers

B:

Protected ci secrets concerns a different operational mechanism. Reproducible provenance limits substitution risks between build and deployment.

C:

Focusing on infrastructure as code drift would leave this problem unresolved: A deployment job downloads a container image by mutable latest tag without checking its origin or digest.

D:

Pipeline dependency trust concerns another aspect of the problem. Reproducible provenance limits substitution risks between build and deployment.

Question 578

At fictional Foxham Utilities, a software-security team is conducting a DevSecOps security control gate within a practical least-privilege design. The case observation is: A deployment job downloads a container image by mutable latest tag without checking its origin or digest. The team must select a defensible control or assessment. Which secure-design principle best explains the appropriate approach?

  1. For the a DevSecOps security control gate at fictional Foxham Utilities, secrets should be managed by an access-controlled lifecycle rather than source-control distribution.
  2. For the a DevSecOps security control gate at fictional Foxham Utilities, reproducible provenance limits substitution risks between build and deployment.
  3. For the a DevSecOps security control gate at fictional Foxham Utilities, artifact signatures only provide assurance when signer identity and key custody are trustworthy.
  4. For the a DevSecOps security control gate at fictional Foxham Utilities, cI/CD pipelines are privileged software supply-chain systems requiring explicit trust boundaries.

Explanation

Writer-proposed answer: B (UNVERIFIED)

Preliminary individual option explanations — NOT expert validated

Correct Answer

B:

Reproducible provenance limits substitution risks between build and deployment. Deployment logs bind commit, builder identity, signed digest, and running workload artifact across environments.

Incorrect Answers

A:

This response concerns runtime secret injection. Here, a deployment job downloads a container image by mutable latest tag without checking its origin or digest. The confirming evidence is: Deployment logs bind commit, builder identity, signed digest, and running workload artifact across environments.

C:

Focusing on release signing identity would leave this problem unresolved: A deployment job downloads a container image by mutable latest tag without checking its origin or digest.

D:

Protected ci secrets concerns another aspect of the problem. Reproducible provenance limits substitution risks between build and deployment.

Question 579

At fictional Foxham Utilities, a software-security team is conducting a DevSecOps security control gate within a practical least-privilege design. The case observation is: A deployment job downloads a container image by mutable latest tag without checking its origin or digest. 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 DevSecOps security control gate at fictional Foxham Utilities, a stolen signing key can make malicious artifacts appear authentic.
  2. For the a DevSecOps security control gate at fictional Foxham Utilities, a weaker staging host may become a path to production compromise.
  3. For the a DevSecOps security control gate at fictional Foxham Utilities, an attacker or accidental tag update may replace the intended release without changing deployment configuration.
  4. For the a DevSecOps security control gate at fictional Foxham Utilities, a broad override can permit unrelated vulnerable or untrusted software to launch.

Explanation

Writer-proposed answer: C (UNVERIFIED)

Preliminary individual option explanations — NOT expert validated

Correct Answer

C:

Reproducible provenance limits substitution risks between build and deployment. Deployment logs bind commit, builder identity, signed digest, and running workload artifact across environments.

Incorrect Answers

A:

This response concerns release signing identity. Here, a deployment job downloads a container image by mutable latest tag without checking its origin or digest. The confirming evidence is: Deployment logs bind commit, builder identity, signed digest, and running workload artifact across environments.

B:

Environment segregation concerns a different operational mechanism. Reproducible provenance limits substitution risks between build and deployment.

D:

Automated security policy exception concerns another aspect of the problem. Reproducible provenance limits substitution risks between build and deployment.

Question 580

At fictional Foxham Utilities, a software-security team is conducting a DevSecOps security control gate within a practical least-privilege design. The case observation is: A deployment job downloads a container image by mutable latest tag without checking its origin or digest. The team must select a defensible control or assessment. Which repeatable engineering safeguard would most directly reduce recurrence?

  1. For the a DevSecOps security control gate at fictional Foxham Utilities, audit the toolchain inventory and require approvals for pipeline package changes.
  2. For the a DevSecOps security control gate at fictional Foxham Utilities, enforce protected branches, scoped runners, short-lived credentials and pipeline security tests.
  3. For the a DevSecOps security control gate at fictional Foxham Utilities, schedule drift checks and block insecure manual changes with policy as code.
  4. For the a DevSecOps security control gate at fictional Foxham Utilities, continuously verify artifact signatures and prohibit unpinned production dependencies.

Explanation

Writer-proposed answer: D (UNVERIFIED)

Preliminary individual option explanations — NOT expert validated

Correct Answer

D:

Reproducible provenance limits substitution risks between build and deployment. Deployment logs bind commit, builder identity, signed digest, and running workload artifact across environments.

Incorrect Answers

A:

This response concerns pipeline dependency trust. Here, a deployment job downloads a container image by mutable latest tag without checking its origin or digest. The confirming evidence is: Deployment logs bind commit, builder identity, signed digest, and running workload artifact across environments.

B:

Protected ci secrets concerns a different operational mechanism. Reproducible provenance limits substitution risks between build and deployment.

C:

Focusing on infrastructure as code drift would leave this problem unresolved: A deployment job downloads a container image by mutable latest tag without checking its origin or digest.

Secure Software Design (KEO1) Practice Tests