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 64

Question 630

At fictional Narrowbay Services, a software-security team is conducting an application release-readiness meeting under a documented customer-data protection mandate. The case observation is: A deployment policy blocks unscanned images, but engineers bypass it by disabling the policy for an entire cluster. 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 Narrowbay Services, enforce protected branches, scoped runners, short-lived credentials and pipeline security tests.
  2. For the an application release-readiness meeting at fictional Narrowbay Services, measure exception age and enforce automatic revocation plus independent post-release review.
  3. For the an application release-readiness meeting at fictional Narrowbay Services, audit the toolchain inventory and require approvals for pipeline package changes.
  4. For the an application release-readiness meeting at fictional Narrowbay Services, 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:

Security exceptions should be constrained to the smallest credible exposure rather than disabling shared controls. Admission tests reject unscanned images outside the approved narrow exception and automatically restore enforcement at expiry.

Incorrect Answers

A:

This response concerns protected ci secrets. Here, a deployment policy blocks unscanned images, but engineers bypass it by disabling the policy for an entire cluster. The confirming evidence is: Admission tests reject unscanned images outside the approved narrow exception and automatically restore enforcement at expiry.

C:

Focusing on pipeline dependency trust would leave this problem unresolved: A deployment policy blocks unscanned images, but engineers bypass it by disabling the policy for an entire cluster.

D:

Build artifact provenance concerns another aspect of the problem. Security exceptions should be constrained to the smallest credible exposure rather than disabling shared controls.

Question 631

At fictional Tanglebrook Public Works, a software-security team is conducting a service integration assurance review while preserving independent evidence of control effectiveness. The case observation is: The organization signs releases using a shared long-lived key stored on a build server accessible to many teams. The team must select a defensible control or assessment. Which security design action most directly addresses the documented problem?

  1. For the a service integration assurance review at fictional Tanglebrook Public Works, detect live-versus-declared configuration drift and restore least-privilege policy through controlled change.
  2. For the a service integration assurance review at fictional Tanglebrook Public Works, separate environment identities, accounts or boundaries and enforce explicit cross-environment denial.
  3. For the a service integration assurance review at fictional Tanglebrook Public Works, use isolated signing identities, restricted release authorization, short-lived credentials where supported, and auditable signing evidence.
  4. For the a service integration assurance review at fictional Tanglebrook Public Works, use a curated dependency registry, pinned versions, integrity verification and minimal build environment privileges.

Explanation

Writer-proposed answer: C (UNVERIFIED)

Preliminary individual option explanations — NOT expert validated

Correct Answer

C:

Artifact signatures only provide assurance when signer identity and key custody are trustworthy. A signed release can be traced to approved build provenance without exposing the signing credential to ordinary jobs.

Incorrect Answers

A:

This response concerns infrastructure as code drift. Here, the organization signs releases using a shared long-lived key stored on a build server accessible to many teams. The confirming evidence is: A signed release can be traced to approved build provenance without exposing the signing credential to ordinary jobs.

B:

Environment segregation concerns a different operational mechanism. Artifact signatures only provide assurance when signer identity and key custody are trustworthy.

D:

Pipeline dependency trust concerns another aspect of the problem. Artifact signatures only provide assurance when signer identity and key custody are trustworthy.

Question 632

At fictional Tanglebrook Public Works, a software-security team is conducting a service integration assurance review while preserving independent evidence of control effectiveness. The case observation is: The organization signs releases using a shared long-lived key stored on a build server accessible to many teams. 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 service integration assurance review at fictional Tanglebrook Public Works, a stolen staging credential cannot access production data or modify deployment infrastructure.
  2. For the a service integration assurance review at fictional Tanglebrook Public Works, rebuilt releases use approved package digests and cannot fetch unreviewed pipeline tooling.
  3. For the a service integration assurance review at fictional Tanglebrook Public Works, untrusted contributions cannot access release secrets, while approved builds still publish traceable signed artifacts.
  4. For the a service integration assurance review at fictional Tanglebrook Public Works, a signed release can be traced to approved build provenance without exposing the signing credential to ordinary jobs.

Explanation

Writer-proposed answer: D (UNVERIFIED)

Preliminary individual option explanations — NOT expert validated

Correct Answer

D:

Artifact signatures only provide assurance when signer identity and key custody are trustworthy. A signed release can be traced to approved build provenance without exposing the signing credential to ordinary jobs.

Incorrect Answers

A:

This response concerns environment segregation. Here, the organization signs releases using a shared long-lived key stored on a build server accessible to many teams. The confirming evidence is: A signed release can be traced to approved build provenance without exposing the signing credential to ordinary jobs.

B:

Pipeline dependency trust concerns a different operational mechanism. Artifact signatures only provide assurance when signer identity and key custody are trustworthy.

C:

Focusing on protected ci secrets would leave this problem unresolved: The organization signs releases using a shared long-lived key stored on a build server accessible to many teams.

Question 633

At fictional Tanglebrook Public Works, a software-security team is conducting a service integration assurance review while preserving independent evidence of control effectiveness. The case observation is: The organization signs releases using a shared long-lived key stored on a build server accessible to many teams. The team must select a defensible control or assessment. Which secure-design principle best explains the appropriate approach?

  1. For the a service integration assurance review at fictional Tanglebrook Public Works, artifact signatures only provide assurance when signer identity and key custody are trustworthy.
  2. For the a service integration assurance review at fictional Tanglebrook Public Works, reproducible provenance limits substitution risks between build and deployment.
  3. For the a service integration assurance review at fictional Tanglebrook Public Works, cI/CD pipelines are privileged software supply-chain systems requiring explicit trust boundaries.
  4. For the a service integration assurance review at fictional Tanglebrook Public Works, declarative desired state is not protection unless effective deployed state is monitored and enforced.

Explanation

Writer-proposed answer: A (UNVERIFIED)

Preliminary individual option explanations — NOT expert validated

Correct Answer

A:

Artifact signatures only provide assurance when signer identity and key custody are trustworthy. A signed release can be traced to approved build provenance without exposing the signing credential to ordinary jobs.

Incorrect Answers

B:

Build artifact provenance concerns a different operational mechanism. Artifact signatures only provide assurance when signer identity and key custody are trustworthy.

C:

Focusing on protected ci secrets would leave this problem unresolved: The organization signs releases using a shared long-lived key stored on a build server accessible to many teams.

D:

Infrastructure as code drift concerns another aspect of the problem. Artifact signatures only provide assurance when signer identity and key custody are trustworthy.

Question 634

At fictional Tanglebrook Public Works, a software-security team is conducting a service integration assurance review while preserving independent evidence of control effectiveness. The case observation is: The organization signs releases using a shared long-lived key stored on a build server accessible to many teams. 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 service integration assurance review at fictional Tanglebrook Public Works, compromised repository history may continue exposing usable credentials.
  2. For the a service integration assurance review at fictional Tanglebrook Public Works, a stolen signing key can make malicious artifacts appear authentic.
  3. For the a service integration assurance review at fictional Tanglebrook Public Works, a broad override can permit unrelated vulnerable or untrusted software to launch.
  4. For the a service integration assurance review at fictional Tanglebrook Public Works, sensitive objects can be exposed even when repository templates look secure.

Explanation

Writer-proposed answer: B (UNVERIFIED)

Preliminary individual option explanations — NOT expert validated

Correct Answer

B:

Artifact signatures only provide assurance when signer identity and key custody are trustworthy. A signed release can be traced to approved build provenance without exposing the signing credential to ordinary jobs.

Incorrect Answers

A:

This response concerns runtime secret injection. Here, the organization signs releases using a shared long-lived key stored on a build server accessible to many teams. The confirming evidence is: A signed release can be traced to approved build provenance without exposing the signing credential to ordinary jobs.

C:

Focusing on automated security policy exception would leave this problem unresolved: The organization signs releases using a shared long-lived key stored on a build server accessible to many teams.

D:

Infrastructure as code drift concerns another aspect of the problem. Artifact signatures only provide assurance when signer identity and key custody are trustworthy.

Question 635

At fictional Tanglebrook Public Works, a software-security team is conducting a service integration assurance review while preserving independent evidence of control effectiveness. The case observation is: The organization signs releases using a shared long-lived key stored on a build server accessible to many teams. The team must select a defensible control or assessment. Which repeatable engineering safeguard would most directly reduce recurrence?

  1. For the a service integration assurance review at fictional Tanglebrook Public Works, enforce protected branches, scoped runners, short-lived credentials and pipeline security tests.
  2. For the a service integration assurance review at fictional Tanglebrook Public Works, run secret detection before commits and rotate any leaked credentials using an incident procedure.
  3. For the a service integration assurance review at fictional Tanglebrook Public Works, rotate and audit signing credentials and test that nonrelease jobs cannot produce trusted signatures.
  4. For the a service integration assurance review at fictional Tanglebrook Public Works, continuously verify artifact signatures and prohibit unpinned production dependencies.

Explanation

Writer-proposed answer: C (UNVERIFIED)

Preliminary individual option explanations — NOT expert validated

Correct Answer

C:

Artifact signatures only provide assurance when signer identity and key custody are trustworthy. A signed release can be traced to approved build provenance without exposing the signing credential to ordinary jobs.

Incorrect Answers

A:

This response concerns protected ci secrets. Here, the organization signs releases using a shared long-lived key stored on a build server accessible to many teams. The confirming evidence is: A signed release can be traced to approved build provenance without exposing the signing credential to ordinary jobs.

B:

Runtime secret injection concerns a different operational mechanism. Artifact signatures only provide assurance when signer identity and key custody are trustworthy.

D:

Build artifact provenance concerns another aspect of the problem. Artifact signatures only provide assurance when signer identity and key custody are trustworthy.

Question 636

At fictional Brookfield Data Trust, a software-security team is conducting a supplier and application control assessment under a defined risk appetite and change authorization. The case observation is: The organization signs releases using a shared long-lived key stored on a build server accessible to many teams. The team must select a defensible control or assessment. Which security design action most directly addresses the documented problem?

  1. For the a supplier and application control assessment at fictional Brookfield Data Trust, use a curated dependency registry, pinned versions, integrity verification and minimal build environment privileges.
  2. For the a supplier and application control assessment at fictional Brookfield Data Trust, separate untrusted build execution from privileged release jobs and grant ephemeral tokens only to reviewed protected workflows.
  3. For the a supplier and application control assessment at fictional Brookfield Data Trust, create scoped, expiring exceptions with recorded risk ownership while keeping global admission controls enforced.
  4. For the a supplier and application control assessment at fictional Brookfield Data Trust, use isolated signing identities, restricted release authorization, short-lived credentials where supported, and auditable signing evidence.

Explanation

Writer-proposed answer: D (UNVERIFIED)

Preliminary individual option explanations — NOT expert validated

Correct Answer

D:

Artifact signatures only provide assurance when signer identity and key custody are trustworthy. A signed release can be traced to approved build provenance without exposing the signing credential to ordinary jobs.

Incorrect Answers

A:

This response concerns pipeline dependency trust. Here, the organization signs releases using a shared long-lived key stored on a build server accessible to many teams. The confirming evidence is: A signed release can be traced to approved build provenance without exposing the signing credential to ordinary jobs.

B:

Protected ci secrets concerns a different operational mechanism. Artifact signatures only provide assurance when signer identity and key custody are trustworthy.

C:

Focusing on automated security policy exception would leave this problem unresolved: The organization signs releases using a shared long-lived key stored on a build server accessible to many teams.

Question 637

At fictional Brookfield Data Trust, a software-security team is conducting a supplier and application control assessment under a defined risk appetite and change authorization. The case observation is: The organization signs releases using a shared long-lived key stored on a build server accessible to many teams. 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 supplier and application control assessment at fictional Brookfield Data Trust, a signed release can be traced to approved build provenance without exposing the signing credential to ordinary jobs.
  2. For the a supplier and application control assessment at fictional Brookfield Data Trust, admission tests reject unscanned images outside the approved narrow exception and automatically restore enforcement at expiry.
  3. For the a supplier and application control assessment at fictional Brookfield Data Trust, a stolen staging credential cannot access production data or modify deployment infrastructure.
  4. For the a supplier and application control assessment at fictional Brookfield Data Trust, deployment logs bind commit, builder identity, signed digest, and running workload artifact across environments.

Explanation

Writer-proposed answer: A (UNVERIFIED)

Preliminary individual option explanations — NOT expert validated

Correct Answer

A:

Artifact signatures only provide assurance when signer identity and key custody are trustworthy. A signed release can be traced to approved build provenance without exposing the signing credential to ordinary jobs.

Incorrect Answers

B:

Automated security policy exception concerns a different operational mechanism. Artifact signatures only provide assurance when signer identity and key custody are trustworthy.

C:

Focusing on environment segregation would leave this problem unresolved: The organization signs releases using a shared long-lived key stored on a build server accessible to many teams.

D:

Build artifact provenance concerns another aspect of the problem. Artifact signatures only provide assurance when signer identity and key custody are trustworthy.

Question 638

At fictional Brookfield Data Trust, a software-security team is conducting a supplier and application control assessment under a defined risk appetite and change authorization. The case observation is: The organization signs releases using a shared long-lived key stored on a build server accessible to many teams. The team must select a defensible control or assessment. Which secure-design principle best explains the appropriate approach?

  1. For the a supplier and application control assessment at fictional Brookfield Data Trust, declarative desired state is not protection unless effective deployed state is monitored and enforced.
  2. For the a supplier and application control assessment at fictional Brookfield Data Trust, artifact signatures only provide assurance when signer identity and key custody are trustworthy.
  3. For the a supplier and application control assessment at fictional Brookfield Data Trust, build tools are part of the trusted computing base and deserve supply-chain governance.
  4. For the a supplier and application control assessment at fictional Brookfield Data Trust, 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:

Artifact signatures only provide assurance when signer identity and key custody are trustworthy. A signed release can be traced to approved build provenance without exposing the signing credential to ordinary jobs.

Incorrect Answers

A:

This response concerns infrastructure as code drift. Here, the organization signs releases using a shared long-lived key stored on a build server accessible to many teams. The confirming evidence is: A signed release can be traced to approved build provenance without exposing the signing credential to ordinary jobs.

C:

Focusing on pipeline dependency trust would leave this problem unresolved: The organization signs releases using a shared long-lived key stored on a build server accessible to many teams.

D:

Protected ci secrets concerns another aspect of the problem. Artifact signatures only provide assurance when signer identity and key custody are trustworthy.

Question 639

At fictional Brookfield Data Trust, a software-security team is conducting a supplier and application control assessment under a defined risk appetite and change authorization. The case observation is: The organization signs releases using a shared long-lived key stored on a build server accessible to many teams. 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 supplier and application control assessment at fictional Brookfield Data Trust, a weaker staging host may become a path to production compromise.
  2. For the a supplier and application control assessment at fictional Brookfield Data Trust, an attacker or accidental tag update may replace the intended release without changing deployment configuration.
  3. For the a supplier and application control assessment at fictional Brookfield Data Trust, a stolen signing key can make malicious artifacts appear authentic.
  4. For the a supplier and application control assessment at fictional Brookfield Data Trust, malicious contributions may exfiltrate credentials and publish compromised releases.

Explanation

Writer-proposed answer: C (UNVERIFIED)

Preliminary individual option explanations — NOT expert validated

Correct Answer

C:

Artifact signatures only provide assurance when signer identity and key custody are trustworthy. A signed release can be traced to approved build provenance without exposing the signing credential to ordinary jobs.

Incorrect Answers

A:

This response concerns environment segregation. Here, the organization signs releases using a shared long-lived key stored on a build server accessible to many teams. The confirming evidence is: A signed release can be traced to approved build provenance without exposing the signing credential to ordinary jobs.

B:

Build artifact provenance concerns a different operational mechanism. Artifact signatures only provide assurance when signer identity and key custody are trustworthy.

D:

Protected ci secrets concerns another aspect of the problem. Artifact signatures only provide assurance when signer identity and key custody are trustworthy.

Question 640

At fictional Brookfield Data Trust, a software-security team is conducting a supplier and application control assessment under a defined risk appetite and change authorization. The case observation is: The organization signs releases using a shared long-lived key stored on a build server accessible to many teams. 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 Brookfield Data Trust, continuously verify artifact signatures and prohibit unpinned production dependencies.
  2. For the a supplier and application control assessment at fictional Brookfield Data Trust, measure exception age and enforce automatic revocation plus independent post-release review.
  3. For the a supplier and application control assessment at fictional Brookfield Data Trust, enforce protected branches, scoped runners, short-lived credentials and pipeline security tests.
  4. For the a supplier and application control assessment at fictional Brookfield Data Trust, rotate and audit signing credentials and test that nonrelease jobs cannot produce trusted signatures.

Explanation

Writer-proposed answer: D (UNVERIFIED)

Preliminary individual option explanations — NOT expert validated

Correct Answer

D:

Artifact signatures only provide assurance when signer identity and key custody are trustworthy. A signed release can be traced to approved build provenance without exposing the signing credential to ordinary jobs.

Incorrect Answers

A:

This response concerns build artifact provenance. Here, the organization signs releases using a shared long-lived key stored on a build server accessible to many teams. The confirming evidence is: A signed release can be traced to approved build provenance without exposing the signing credential to ordinary jobs.

B:

Automated security policy exception concerns a different operational mechanism. Artifact signatures only provide assurance when signer identity and key custody are trustworthy.

C:

Focusing on protected ci secrets would leave this problem unresolved: The organization signs releases using a shared long-lived key stored on a build server accessible to many teams.

Secure Software Design (KEO1) Practice Tests