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 61

Question 600

At fictional Pineview Education, a software-security team is conducting a planned system modernization within the approved release and rollback constraints. The case observation is: A build pipeline installs development utilities from arbitrary internet packages without version constraints or checksum checks. The team must select a defensible control or assessment. Which repeatable engineering safeguard would most directly reduce recurrence?

  1. For the a planned system modernization at fictional Pineview Education, test isolation controls and review environment role trust policies after platform changes.
  2. For the a planned system modernization at fictional Pineview Education, continuously verify artifact signatures and prohibit unpinned production dependencies.
  3. For the a planned system modernization at fictional Pineview Education, enforce protected branches, scoped runners, short-lived credentials and pipeline security tests.
  4. For the a planned system modernization at fictional Pineview Education, audit the toolchain inventory and require approvals for pipeline package changes.

Explanation

Writer-proposed answer: D (UNVERIFIED)

Preliminary individual option explanations — NOT expert validated

Correct Answer

D:

Build tools are part of the trusted computing base and deserve supply-chain governance. Rebuilt releases use approved package digests and cannot fetch unreviewed pipeline tooling.

Incorrect Answers

A:

This response concerns environment segregation. Here, a build pipeline installs development utilities from arbitrary internet packages without version constraints or checksum checks. The confirming evidence is: Rebuilt releases use approved package digests and cannot fetch unreviewed pipeline tooling.

B:

Build artifact provenance concerns a different operational mechanism. Build tools are part of the trusted computing base and deserve supply-chain governance.

C:

Focusing on protected ci secrets would leave this problem unresolved: A build pipeline installs development utilities from arbitrary internet packages without version constraints or checksum checks.

Question 601

At fictional Violetgate Housing, a software-security team is conducting a security incident follow-up assessment under a defined risk appetite and change authorization. The case observation is: Production secrets are committed into a deployment manifest so every engineer cloning the repository receives them. The team must select a defensible control or assessment. Which security design action most directly addresses the documented problem?

  1. For the a security incident follow-up assessment at fictional Violetgate Housing, move secrets into managed runtime injection with access-scoped workload identity and rotate committed credentials.
  2. For the a security incident follow-up assessment at fictional Violetgate Housing, use isolated signing identities, restricted release authorization, short-lived credentials where supported, and auditable signing evidence.
  3. For the a security incident follow-up assessment at fictional Violetgate Housing, use a curated dependency registry, pinned versions, integrity verification and minimal build environment privileges.
  4. For the a security incident follow-up assessment at fictional Violetgate Housing, separate untrusted build execution from privileged release jobs and grant ephemeral tokens only to reviewed protected workflows.

Explanation

Writer-proposed answer: A (UNVERIFIED)

Preliminary individual option explanations — NOT expert validated

Correct Answer

A:

Secrets should be managed by an access-controlled lifecycle rather than source-control distribution. Repository scans are clean, service startup retrieves scoped secrets, and former committed keys are invalid.

Incorrect Answers

B:

Release signing identity concerns a different operational mechanism. Secrets should be managed by an access-controlled lifecycle rather than source-control distribution.

C:

Focusing on pipeline dependency trust would leave this problem unresolved: Production secrets are committed into a deployment manifest so every engineer cloning the repository receives them.

D:

Protected ci secrets concerns another aspect of the problem. Secrets should be managed by an access-controlled lifecycle rather than source-control distribution.

Question 602

At fictional Violetgate Housing, a software-security team is conducting a security incident follow-up assessment under a defined risk appetite and change authorization. The case observation is: Production secrets are committed into a deployment manifest so every engineer cloning the repository receives them. 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 security incident follow-up assessment at fictional Violetgate Housing, continuous configuration assessment reports no unauthorized public access and records the corrective deployment.
  2. For the a security incident follow-up assessment at fictional Violetgate Housing, repository scans are clean, service startup retrieves scoped secrets, and former committed keys are invalid.
  3. For the a security incident follow-up assessment at fictional Violetgate Housing, deployment logs bind commit, builder identity, signed digest, and running workload artifact across environments.
  4. For the a security incident follow-up assessment at fictional Violetgate Housing, admission tests reject unscanned images outside the approved narrow exception and automatically restore enforcement at expiry.

Explanation

Writer-proposed answer: B (UNVERIFIED)

Preliminary individual option explanations — NOT expert validated

Correct Answer

B:

Secrets should be managed by an access-controlled lifecycle rather than source-control distribution. Repository scans are clean, service startup retrieves scoped secrets, and former committed keys are invalid.

Incorrect Answers

A:

This response concerns infrastructure as code drift. Here, production secrets are committed into a deployment manifest so every engineer cloning the repository receives them. The confirming evidence is: Repository scans are clean, service startup retrieves scoped secrets, and former committed keys are invalid.

C:

Focusing on build artifact provenance would leave this problem unresolved: Production secrets are committed into a deployment manifest so every engineer cloning the repository receives them.

D:

Automated security policy exception concerns another aspect of the problem. Secrets should be managed by an access-controlled lifecycle rather than source-control distribution.

Question 603

At fictional Violetgate Housing, a software-security team is conducting a security incident follow-up assessment under a defined risk appetite and change authorization. The case observation is: Production secrets are committed into a deployment manifest so every engineer cloning the repository receives them. The team must select a defensible control or assessment. Which secure-design principle best explains the appropriate approach?

  1. For the a security incident follow-up assessment at fictional Violetgate Housing, security exceptions should be constrained to the smallest credible exposure rather than disabling shared controls.
  2. For the a security incident follow-up assessment at fictional Violetgate Housing, artifact signatures only provide assurance when signer identity and key custody are trustworthy.
  3. For the a security incident follow-up assessment at fictional Violetgate Housing, secrets should be managed by an access-controlled lifecycle rather than source-control distribution.
  4. For the a security incident follow-up assessment at fictional Violetgate Housing, cI/CD pipelines are privileged software supply-chain systems requiring explicit trust boundaries.

Explanation

Writer-proposed answer: C (UNVERIFIED)

Preliminary individual option explanations — NOT expert validated

Correct Answer

C:

Secrets should be managed by an access-controlled lifecycle rather than source-control distribution. Repository scans are clean, service startup retrieves scoped secrets, and former committed keys are invalid.

Incorrect Answers

A:

This response concerns automated security policy exception. Here, production secrets are committed into a deployment manifest so every engineer cloning the repository receives them. The confirming evidence is: Repository scans are clean, service startup retrieves scoped secrets, and former committed keys are invalid.

B:

Release signing identity concerns a different operational mechanism. Secrets should be managed by an access-controlled lifecycle rather than source-control distribution.

D:

Protected ci secrets concerns another aspect of the problem. Secrets should be managed by an access-controlled lifecycle rather than source-control distribution.

Question 604

At fictional Violetgate Housing, a software-security team is conducting a security incident follow-up assessment under a defined risk appetite and change authorization. The case observation is: Production secrets are committed into a deployment manifest so every engineer cloning the repository receives them. 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 security incident follow-up assessment at fictional Violetgate Housing, an attacker or accidental tag update may replace the intended release without changing deployment configuration.
  2. For the a security incident follow-up assessment at fictional Violetgate Housing, a weaker staging host may become a path to production compromise.
  3. For the a security incident follow-up assessment at fictional Violetgate Housing, sensitive objects can be exposed even when repository templates look secure.
  4. For the a security incident follow-up assessment at fictional Violetgate Housing, compromised repository history may continue exposing usable credentials.

Explanation

Writer-proposed answer: D (UNVERIFIED)

Preliminary individual option explanations — NOT expert validated

Correct Answer

D:

Secrets should be managed by an access-controlled lifecycle rather than source-control distribution. Repository scans are clean, service startup retrieves scoped secrets, and former committed keys are invalid.

Incorrect Answers

A:

This response concerns build artifact provenance. Here, production secrets are committed into a deployment manifest so every engineer cloning the repository receives them. The confirming evidence is: Repository scans are clean, service startup retrieves scoped secrets, and former committed keys are invalid.

B:

Environment segregation concerns a different operational mechanism. Secrets should be managed by an access-controlled lifecycle rather than source-control distribution.

C:

Focusing on infrastructure as code drift would leave this problem unresolved: Production secrets are committed into a deployment manifest so every engineer cloning the repository receives them.

Question 605

At fictional Violetgate Housing, a software-security team is conducting a security incident follow-up assessment under a defined risk appetite and change authorization. The case observation is: Production secrets are committed into a deployment manifest so every engineer cloning the repository receives them. The team must select a defensible control or assessment. Which repeatable engineering safeguard would most directly reduce recurrence?

  1. For the a security incident follow-up assessment at fictional Violetgate Housing, run secret detection before commits and rotate any leaked credentials using an incident procedure.
  2. For the a security incident follow-up assessment at fictional Violetgate Housing, test isolation controls and review environment role trust policies after platform changes.
  3. For the a security incident follow-up assessment at fictional Violetgate Housing, schedule drift checks and block insecure manual changes with policy as code.
  4. For the a security incident follow-up assessment at fictional Violetgate Housing, enforce protected branches, scoped runners, short-lived credentials and pipeline security tests.

Explanation

Writer-proposed answer: A (UNVERIFIED)

Preliminary individual option explanations — NOT expert validated

Correct Answer

A:

Secrets should be managed by an access-controlled lifecycle rather than source-control distribution. Repository scans are clean, service startup retrieves scoped secrets, and former committed keys are invalid.

Incorrect Answers

B:

Environment segregation concerns a different operational mechanism. Secrets should be managed by an access-controlled lifecycle rather than source-control distribution.

C:

Focusing on infrastructure as code drift would leave this problem unresolved: Production secrets are committed into a deployment manifest so every engineer cloning the repository receives them.

D:

Protected ci secrets concerns another aspect of the problem. Secrets should be managed by an access-controlled lifecycle rather than source-control distribution.

Question 606

At fictional Deepwood Tourism, a software-security team is conducting a regulated data-protection review while protecting cross-tenant boundaries. The case observation is: Production secrets are committed into a deployment manifest so every engineer cloning the repository receives them. The team must select a defensible control or assessment. Which security design action most directly addresses the documented problem?

  1. For the a regulated data-protection review at fictional Deepwood Tourism, separate untrusted build execution from privileged release jobs and grant ephemeral tokens only to reviewed protected workflows.
  2. For the a regulated data-protection review at fictional Deepwood Tourism, move secrets into managed runtime injection with access-scoped workload identity and rotate committed credentials.
  3. For the a regulated data-protection review at fictional Deepwood Tourism, create scoped, expiring exceptions with recorded risk ownership while keeping global admission controls enforced.
  4. For the a regulated data-protection review at fictional Deepwood Tourism, 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:

Secrets should be managed by an access-controlled lifecycle rather than source-control distribution. Repository scans are clean, service startup retrieves scoped secrets, and former committed keys are invalid.

Incorrect Answers

A:

This response concerns protected ci secrets. Here, production secrets are committed into a deployment manifest so every engineer cloning the repository receives them. The confirming evidence is: Repository scans are clean, service startup retrieves scoped secrets, and former committed keys are invalid.

C:

Focusing on automated security policy exception would leave this problem unresolved: Production secrets are committed into a deployment manifest so every engineer cloning the repository receives them.

D:

Release signing identity concerns another aspect of the problem. Secrets should be managed by an access-controlled lifecycle rather than source-control distribution.

Question 607

At fictional Deepwood Tourism, a software-security team is conducting a regulated data-protection review while protecting cross-tenant boundaries. The case observation is: Production secrets are committed into a deployment manifest so every engineer cloning the repository receives them. 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 regulated data-protection review at fictional Deepwood Tourism, rebuilt releases use approved package digests and cannot fetch unreviewed pipeline tooling.
  2. For the a regulated data-protection review at fictional Deepwood Tourism, deployment logs bind commit, builder identity, signed digest, and running workload artifact across environments.
  3. For the a regulated data-protection review at fictional Deepwood Tourism, repository scans are clean, service startup retrieves scoped secrets, and former committed keys are invalid.
  4. For the a regulated data-protection review at fictional Deepwood Tourism, untrusted contributions cannot access release secrets, while approved builds still publish traceable signed artifacts.

Explanation

Writer-proposed answer: C (UNVERIFIED)

Preliminary individual option explanations — NOT expert validated

Correct Answer

C:

Secrets should be managed by an access-controlled lifecycle rather than source-control distribution. Repository scans are clean, service startup retrieves scoped secrets, and former committed keys are invalid.

Incorrect Answers

A:

This response concerns pipeline dependency trust. Here, production secrets are committed into a deployment manifest so every engineer cloning the repository receives them. The confirming evidence is: Repository scans are clean, service startup retrieves scoped secrets, and former committed keys are invalid.

B:

Build artifact provenance concerns a different operational mechanism. Secrets should be managed by an access-controlled lifecycle rather than source-control distribution.

D:

Protected ci secrets concerns another aspect of the problem. Secrets should be managed by an access-controlled lifecycle rather than source-control distribution.

Question 608

At fictional Deepwood Tourism, a software-security team is conducting a regulated data-protection review while protecting cross-tenant boundaries. The case observation is: Production secrets are committed into a deployment manifest so every engineer cloning the repository receives them. The team must select a defensible control or assessment. Which secure-design principle best explains the appropriate approach?

  1. For the a regulated data-protection review at fictional Deepwood Tourism, artifact signatures only provide assurance when signer identity and key custody are trustworthy.
  2. For the a regulated data-protection review at fictional Deepwood Tourism, reproducible provenance limits substitution risks between build and deployment.
  3. For the a regulated data-protection review at fictional Deepwood Tourism, build tools are part of the trusted computing base and deserve supply-chain governance.
  4. For the a regulated data-protection review at fictional Deepwood Tourism, secrets should be managed by an access-controlled lifecycle rather than source-control distribution.

Explanation

Writer-proposed answer: D (UNVERIFIED)

Preliminary individual option explanations — NOT expert validated

Correct Answer

D:

Secrets should be managed by an access-controlled lifecycle rather than source-control distribution. Repository scans are clean, service startup retrieves scoped secrets, and former committed keys are invalid.

Incorrect Answers

A:

This response concerns release signing identity. Here, production secrets are committed into a deployment manifest so every engineer cloning the repository receives them. The confirming evidence is: Repository scans are clean, service startup retrieves scoped secrets, and former committed keys are invalid.

B:

Build artifact provenance concerns a different operational mechanism. Secrets should be managed by an access-controlled lifecycle rather than source-control distribution.

C:

Focusing on pipeline dependency trust would leave this problem unresolved: Production secrets are committed into a deployment manifest so every engineer cloning the repository receives them.

Question 609

At fictional Deepwood Tourism, a software-security team is conducting a regulated data-protection review while protecting cross-tenant boundaries. The case observation is: Production secrets are committed into a deployment manifest so every engineer cloning the repository receives them. 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 regulated data-protection review at fictional Deepwood Tourism, compromised repository history may continue exposing usable credentials.
  2. For the a regulated data-protection review at fictional Deepwood Tourism, sensitive objects can be exposed even when repository templates look secure.
  3. For the a regulated data-protection review at fictional Deepwood Tourism, a stolen signing key can make malicious artifacts appear authentic.
  4. For the a regulated data-protection review at fictional Deepwood Tourism, a broad override can permit unrelated vulnerable or untrusted software to launch.

Explanation

Writer-proposed answer: A (UNVERIFIED)

Preliminary individual option explanations — NOT expert validated

Correct Answer

A:

Secrets should be managed by an access-controlled lifecycle rather than source-control distribution. Repository scans are clean, service startup retrieves scoped secrets, and former committed keys are invalid.

Incorrect Answers

B:

Infrastructure as code drift concerns a different operational mechanism. Secrets should be managed by an access-controlled lifecycle rather than source-control distribution.

C:

Focusing on release signing identity would leave this problem unresolved: Production secrets are committed into a deployment manifest so every engineer cloning the repository receives them.

D:

Automated security policy exception concerns another aspect of the problem. Secrets should be managed by an access-controlled lifecycle rather than source-control distribution.

Question 610

At fictional Deepwood Tourism, a software-security team is conducting a regulated data-protection review while protecting cross-tenant boundaries. The case observation is: Production secrets are committed into a deployment manifest so every engineer cloning the repository receives them. The team must select a defensible control or assessment. Which repeatable engineering safeguard would most directly reduce recurrence?

  1. For the a regulated data-protection review at fictional Deepwood Tourism, measure exception age and enforce automatic revocation plus independent post-release review.
  2. For the a regulated data-protection review at fictional Deepwood Tourism, run secret detection before commits and rotate any leaked credentials using an incident procedure.
  3. For the a regulated data-protection review at fictional Deepwood Tourism, test isolation controls and review environment role trust policies after platform changes.
  4. For the a regulated data-protection review at fictional Deepwood Tourism, enforce protected branches, scoped runners, short-lived credentials and pipeline security tests.

Explanation

Writer-proposed answer: B (UNVERIFIED)

Preliminary individual option explanations — NOT expert validated

Correct Answer

B:

Secrets should be managed by an access-controlled lifecycle rather than source-control distribution. Repository scans are clean, service startup retrieves scoped secrets, and former committed keys are invalid.

Incorrect Answers

A:

This response concerns automated security policy exception. Here, production secrets are committed into a deployment manifest so every engineer cloning the repository receives them. The confirming evidence is: Repository scans are clean, service startup retrieves scoped secrets, and former committed keys are invalid.

C:

Focusing on environment segregation would leave this problem unresolved: Production secrets are committed into a deployment manifest so every engineer cloning the repository receives them.

D:

Protected ci secrets concerns another aspect of the problem. Secrets should be managed by an access-controlled lifecycle rather than source-control distribution.

Secure Software Design (KEO1) Practice Tests