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 65

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.

Question 641

At fictional Hillford Insurance, a software-security team is conducting an application release-readiness meeting within a practical least-privilege design. The case observation is: A gateway validates a user token, but a downstream microservice accepts unauthenticated direct traffic from other workloads. The team must select a defensible control or assessment. Which security design action most directly addresses the documented problem?

  1. For the an application release-readiness meeting at fictional Hillford Insurance, enforce service-to-service identity and authorization at the downstream service even when the gateway authenticates users.
  2. For the an application release-readiness meeting at fictional Hillford Insurance, use topic-scoped broker credentials and tenant-aware event authorization with isolated processing.
  3. For the an application release-readiness meeting at fictional Hillford Insurance, apply layered per-identity, per-IP and system-wide capacity limits with bounded computational cost and fair isolation.
  4. For the an application release-readiness meeting at fictional Hillford Insurance, configure a strict approved-origin list and validate browser credential behavior without reflecting untrusted origins.

Explanation

Writer-proposed answer: A (UNVERIFIED)

Preliminary individual option explanations — NOT expert validated

Correct Answer

A:

Every service boundary should enforce its own relevant trust decision rather than relying on a single perimeter. Direct service calls lacking valid identity are denied while authorized gateway traffic still succeeds.

Incorrect Answers

B:

Queue consumer permissions concerns a different operational mechanism. Every service boundary should enforce its own relevant trust decision rather than relying on a single perimeter.

C:

Focusing on rate limiting with identity awareness would leave this problem unresolved: A gateway validates a user token, but a downstream microservice accepts unauthenticated direct traffic from other workloads.

D:

Cross-origin policy misconfiguration concerns another aspect of the problem. Every service boundary should enforce its own relevant trust decision rather than relying on a single perimeter.

Question 642

At fictional Hillford Insurance, a software-security team is conducting an application release-readiness meeting within a practical least-privilege design. The case observation is: A gateway validates a user token, but a downstream microservice accepts unauthenticated direct traffic from other workloads. The team must select a defensible control or assessment. Which independent verification evidence would most directly show that the proposed action succeeded?

  1. For the an application release-readiness meeting at fictional Hillford Insurance, replay tests show duplicate requests return the same recorded outcome without an additional charge.
  2. For the an application release-readiness meeting at fictional Hillford Insurance, direct service calls lacking valid identity are denied while authorized gateway traffic still succeeds.
  3. For the an application release-readiness meeting at fictional Hillford Insurance, trace samples contain no reusable tokens and still correlate requests across services reliably.
  4. For the an application release-readiness meeting at fictional Hillford Insurance, cross-origin tests deny unauthorized websites while permitted application origins function normally.

Explanation

Writer-proposed answer: B (UNVERIFIED)

Preliminary individual option explanations — NOT expert validated

Correct Answer

B:

Every service boundary should enforce its own relevant trust decision rather than relying on a single perimeter. Direct service calls lacking valid identity are denied while authorized gateway traffic still succeeds.

Incorrect Answers

A:

This response concerns idempotent payment api design. Here, a gateway validates a user token, but a downstream microservice accepts unauthenticated direct traffic from other workloads. The confirming evidence is: Direct service calls lacking valid identity are denied while authorized gateway traffic still succeeds.

C:

Focusing on distributed trace secret exposure would leave this problem unresolved: A gateway validates a user token, but a downstream microservice accepts unauthenticated direct traffic from other workloads.

D:

Cross-origin policy misconfiguration concerns another aspect of the problem. Every service boundary should enforce its own relevant trust decision rather than relying on a single perimeter.

Question 643

At fictional Hillford Insurance, a software-security team is conducting an application release-readiness meeting within a practical least-privilege design. The case observation is: A gateway validates a user token, but a downstream microservice accepts unauthenticated direct traffic from other workloads. The team must select a defensible control or assessment. Which secure-design principle best explains the appropriate approach?

  1. For the an application release-readiness meeting at fictional Hillford Insurance, transport encryption and authenticated peer authorization are distinct security properties.
  2. For the an application release-readiness meeting at fictional Hillford Insurance, authenticated messages can still be replayed; state transitions need idempotency and time bounds.
  3. For the an application release-readiness meeting at fictional Hillford Insurance, every service boundary should enforce its own relevant trust decision rather than relying on a single perimeter.
  4. For the an application release-readiness meeting at fictional Hillford Insurance, cORS is a browser access policy and should be tightly scoped; it does not replace API authorization.

Explanation

Writer-proposed answer: C (UNVERIFIED)

Preliminary individual option explanations — NOT expert validated

Correct Answer

C:

Every service boundary should enforce its own relevant trust decision rather than relying on a single perimeter. Direct service calls lacking valid identity are denied while authorized gateway traffic still succeeds.

Incorrect Answers

A:

This response concerns mutual tls identity mapping. Here, a gateway validates a user token, but a downstream microservice accepts unauthenticated direct traffic from other workloads. The confirming evidence is: Direct service calls lacking valid identity are denied while authorized gateway traffic still succeeds.

B:

Webhooks replay protection concerns a different operational mechanism. Every service boundary should enforce its own relevant trust decision rather than relying on a single perimeter.

D:

Cross-origin policy misconfiguration concerns another aspect of the problem. Every service boundary should enforce its own relevant trust decision rather than relying on a single perimeter.

Question 644

At fictional Hillford Insurance, a software-security team is conducting an application release-readiness meeting within a practical least-privilege design. The case observation is: A gateway validates a user token, but a downstream microservice accepts unauthenticated direct traffic from other workloads. The team must select a defensible control or assessment. Which consequence is most directly associated with leaving this documented problem unresolved?

  1. For the an application release-readiness meeting at fictional Hillford Insurance, observers or third-party integrations may obtain active credentials from routine traces.
  2. For the an application release-readiness meeting at fictional Hillford Insurance, a compromised authorized certificate from another workload could impersonate a privileged peer.
  3. For the an application release-readiness meeting at fictional Hillford Insurance, untrusted sites could read privileged API responses through a permissive browser policy.
  4. For the an application release-readiness meeting at fictional Hillford Insurance, a compromised workload may bypass the gateway and invoke privileged internal APIs.

Explanation

Writer-proposed answer: D (UNVERIFIED)

Preliminary individual option explanations — NOT expert validated

Correct Answer

D:

Every service boundary should enforce its own relevant trust decision rather than relying on a single perimeter. Direct service calls lacking valid identity are denied while authorized gateway traffic still succeeds.

Incorrect Answers

A:

This response concerns distributed trace secret exposure. Here, a gateway validates a user token, but a downstream microservice accepts unauthenticated direct traffic from other workloads. The confirming evidence is: Direct service calls lacking valid identity are denied while authorized gateway traffic still succeeds.

B:

Mutual tls identity mapping concerns a different operational mechanism. Every service boundary should enforce its own relevant trust decision rather than relying on a single perimeter.

C:

Focusing on cross-origin policy misconfiguration would leave this problem unresolved: A gateway validates a user token, but a downstream microservice accepts unauthenticated direct traffic from other workloads.

Question 645

At fictional Hillford Insurance, a software-security team is conducting an application release-readiness meeting within a practical least-privilege design. The case observation is: A gateway validates a user token, but a downstream microservice accepts unauthenticated direct traffic from other workloads. 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 Hillford Insurance, include direct-to-service access probes and identity checks in service deployment tests.
  2. For the an application release-readiness meeting at fictional Hillford Insurance, track expensive endpoint usage and periodically test distributed abuse and fairness.
  3. For the an application release-readiness meeting at fictional Hillford Insurance, review CORS settings with authentication changes and probe unknown-origin behavior automatically.
  4. For the an application release-readiness meeting at fictional Hillford Insurance, reconcile webhook event ledgers and regression-test replay and reordering scenarios.

Explanation

Writer-proposed answer: A (UNVERIFIED)

Preliminary individual option explanations — NOT expert validated

Correct Answer

A:

Every service boundary should enforce its own relevant trust decision rather than relying on a single perimeter. Direct service calls lacking valid identity are denied while authorized gateway traffic still succeeds.

Incorrect Answers

B:

Rate limiting with identity awareness concerns a different operational mechanism. Every service boundary should enforce its own relevant trust decision rather than relying on a single perimeter.

C:

Focusing on cross-origin policy misconfiguration would leave this problem unresolved: A gateway validates a user token, but a downstream microservice accepts unauthenticated direct traffic from other workloads.

D:

Webhooks replay protection concerns another aspect of the problem. Every service boundary should enforce its own relevant trust decision rather than relying on a single perimeter.

Question 646

At fictional Oakhaven Public Services, a software-security team is conducting a new feature threat-model workshop with an auditable vulnerability remediation process. The case observation is: A gateway validates a user token, but a downstream microservice accepts unauthenticated direct traffic from other workloads. 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 Oakhaven Public Services, verify signatures and freshness, enforce idempotency with persistent event IDs, and define bounded replay windows.
  2. For the a new feature threat-model workshop at fictional Oakhaven Public Services, enforce service-to-service identity and authorization at the downstream service even when the gateway authenticates users.
  3. For the a new feature threat-model workshop at fictional Oakhaven Public Services, use topic-scoped broker credentials and tenant-aware event authorization with isolated processing.
  4. For the a new feature threat-model workshop at fictional Oakhaven Public Services, implement idempotency keys bound to principal and request intent, with transactional deduplication and clear retry semantics.

Explanation

Writer-proposed answer: B (UNVERIFIED)

Preliminary individual option explanations — NOT expert validated

Correct Answer

B:

Every service boundary should enforce its own relevant trust decision rather than relying on a single perimeter. Direct service calls lacking valid identity are denied while authorized gateway traffic still succeeds.

Incorrect Answers

A:

This response concerns webhooks replay protection. Here, a gateway validates a user token, but a downstream microservice accepts unauthenticated direct traffic from other workloads. The confirming evidence is: Direct service calls lacking valid identity are denied while authorized gateway traffic still succeeds.

C:

Focusing on queue consumer permissions would leave this problem unresolved: A gateway validates a user token, but a downstream microservice accepts unauthenticated direct traffic from other workloads.

D:

Idempotent payment api design concerns another aspect of the problem. Every service boundary should enforce its own relevant trust decision rather than relying on a single perimeter.

Question 647

At fictional Oakhaven Public Services, a software-security team is conducting a new feature threat-model workshop with an auditable vulnerability remediation process. The case observation is: A gateway validates a user token, but a downstream microservice accepts unauthenticated direct traffic from other workloads. 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 Oakhaven Public Services, cross-origin tests deny unauthorized websites while permitted application origins function normally.
  2. For the a new feature threat-model workshop at fictional Oakhaven Public Services, load tests show malicious bursts are throttled while legitimate users retain defined availability.
  3. For the a new feature threat-model workshop at fictional Oakhaven Public Services, direct service calls lacking valid identity are denied while authorized gateway traffic still succeeds.
  4. For the a new feature threat-model workshop at fictional Oakhaven Public Services, a certificate for an unrelated service fails authorization even though it chains to a trusted root.

Explanation

Writer-proposed answer: C (UNVERIFIED)

Preliminary individual option explanations — NOT expert validated

Correct Answer

C:

Every service boundary should enforce its own relevant trust decision rather than relying on a single perimeter. Direct service calls lacking valid identity are denied while authorized gateway traffic still succeeds.

Incorrect Answers

A:

This response concerns cross-origin policy misconfiguration. Here, a gateway validates a user token, but a downstream microservice accepts unauthenticated direct traffic from other workloads. The confirming evidence is: Direct service calls lacking valid identity are denied while authorized gateway traffic still succeeds.

B:

Rate limiting with identity awareness concerns a different operational mechanism. Every service boundary should enforce its own relevant trust decision rather than relying on a single perimeter.

D:

Mutual tls identity mapping concerns another aspect of the problem. Every service boundary should enforce its own relevant trust decision rather than relying on a single perimeter.

Question 648

At fictional Oakhaven Public Services, a software-security team is conducting a new feature threat-model workshop with an auditable vulnerability remediation process. The case observation is: A gateway validates a user token, but a downstream microservice accepts unauthenticated direct traffic from other workloads. 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 Oakhaven Public Services, messaging infrastructure must enforce least-privilege event distribution at the broker boundary.
  2. For the a new feature threat-model workshop at fictional Oakhaven Public Services, distributed systems must distinguish repeated delivery from unique business intent.
  3. For the a new feature threat-model workshop at fictional Oakhaven Public Services, cORS is a browser access policy and should be tightly scoped; it does not replace API authorization.
  4. For the a new feature threat-model workshop at fictional Oakhaven Public Services, every service boundary should enforce its own relevant trust decision rather than relying on a single perimeter.

Explanation

Writer-proposed answer: D (UNVERIFIED)

Preliminary individual option explanations — NOT expert validated

Correct Answer

D:

Every service boundary should enforce its own relevant trust decision rather than relying on a single perimeter. Direct service calls lacking valid identity are denied while authorized gateway traffic still succeeds.

Incorrect Answers

A:

This response concerns queue consumer permissions. Here, a gateway validates a user token, but a downstream microservice accepts unauthenticated direct traffic from other workloads. The confirming evidence is: Direct service calls lacking valid identity are denied while authorized gateway traffic still succeeds.

B:

Idempotent payment api design concerns a different operational mechanism. Every service boundary should enforce its own relevant trust decision rather than relying on a single perimeter.

C:

Focusing on cross-origin policy misconfiguration would leave this problem unresolved: A gateway validates a user token, but a downstream microservice accepts unauthenticated direct traffic from other workloads.

Question 649

At fictional Oakhaven Public Services, a software-security team is conducting a new feature threat-model workshop with an auditable vulnerability remediation process. The case observation is: A gateway validates a user token, but a downstream microservice accepts unauthenticated direct traffic from other workloads. 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 Oakhaven Public Services, a compromised workload may bypass the gateway and invoke privileged internal APIs.
  2. For the a new feature threat-model workshop at fictional Oakhaven Public Services, network retries can create unauthorized duplicate financial transactions.
  3. For the a new feature threat-model workshop at fictional Oakhaven Public Services, repeated event delivery may duplicate credits, charges, or account status changes.
  4. For the a new feature threat-model workshop at fictional Oakhaven Public Services, observers or third-party integrations may obtain active credentials from routine traces.

Explanation

Writer-proposed answer: A (UNVERIFIED)

Preliminary individual option explanations — NOT expert validated

Correct Answer

A:

Every service boundary should enforce its own relevant trust decision rather than relying on a single perimeter. Direct service calls lacking valid identity are denied while authorized gateway traffic still succeeds.

Incorrect Answers

B:

Idempotent payment api design concerns a different operational mechanism. Every service boundary should enforce its own relevant trust decision rather than relying on a single perimeter.

C:

Focusing on webhooks replay protection would leave this problem unresolved: A gateway validates a user token, but a downstream microservice accepts unauthenticated direct traffic from other workloads.

D:

Distributed trace secret exposure concerns another aspect of the problem. Every service boundary should enforce its own relevant trust decision rather than relying on a single perimeter.

Question 650

At fictional Oakhaven Public Services, a software-security team is conducting a new feature threat-model workshop with an auditable vulnerability remediation process. The case observation is: A gateway validates a user token, but a downstream microservice accepts unauthenticated direct traffic from other workloads. 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 Oakhaven Public Services, audit service certificate identity rules and rehearse revocation and rotation.
  2. For the a new feature threat-model workshop at fictional Oakhaven Public Services, include direct-to-service access probes and identity checks in service deployment tests.
  3. For the a new feature threat-model workshop at fictional Oakhaven Public Services, review CORS settings with authentication changes and probe unknown-origin behavior automatically.
  4. For the a new feature threat-model workshop at fictional Oakhaven Public Services, track expensive endpoint usage and periodically test distributed abuse and fairness.

Explanation

Writer-proposed answer: B (UNVERIFIED)

Preliminary individual option explanations — NOT expert validated

Correct Answer

B:

Every service boundary should enforce its own relevant trust decision rather than relying on a single perimeter. Direct service calls lacking valid identity are denied while authorized gateway traffic still succeeds.

Incorrect Answers

A:

This response concerns mutual tls identity mapping. Here, a gateway validates a user token, but a downstream microservice accepts unauthenticated direct traffic from other workloads. The confirming evidence is: Direct service calls lacking valid identity are denied while authorized gateway traffic still succeeds.

C:

Focusing on cross-origin policy misconfiguration would leave this problem unresolved: A gateway validates a user token, but a downstream microservice accepts unauthenticated direct traffic from other workloads.

D:

Rate limiting with identity awareness concerns another aspect of the problem. Every service boundary should enforce its own relevant trust decision rather than relying on a single perimeter.

Secure Software Design (KEO1) Practice Tests