WGU D487 Secure Software Design Final
Exam ACTUAL EXAM 2026/2027 |
Western Governors University | Verified
Q&A | Pass Guaranteed - A+ Graded
Answer Key Included
This final examination assesses mastery of secure software design principles as taught in WGU's D487
course. It covers threat modeling, secure coding standards, authentication and access control, security
testing methodologies, and compliance with regulatory frameworks. Questions reflect real-world
software development scenarios and require both foundational knowledge and applied critical thinking
to design and evaluate secure systems.
Content Area Overview
Secure Design Principles & Threat Modeling – Covers foundational security design principles, threat
modeling using STRIDE, DREAD, and attack trees, risk assessment methodologies, and the integration of
security into the software development lifecycle.
Secure Coding Practices & Vulnerability Mitigation – Addresses OWASP Top 10 and CWE/SANS Top 25
vulnerabilities, input validation and output encoding, secure memory handling, cryptographic
implementation, error handling, logging, and secure API design.
Authentication, Authorization & Access Control – Focuses on identity management, password policies,
multifactor authentication, session management, OAuth 2.0, SAML, role-based access control (RBAC),
attribute-based access control (ABAC), and the principle of least privilege.
Application Security Testing, Deployment & Compliance – Examines static and dynamic application
security testing (SAST/DAST), penetration testing, vulnerability scanning, software composition analysis,
DevSecOps pipeline integration, and compliance with standards such as PCI-DSS, HIPAA, and GDPR.
,Section 1: Secure Design Principles & Threat Modeling – Questions 1–15
Q1: The principle of "least privilege" in secure software design means that:
A. Users should be granted administrator access to simplify troubleshooting
B. Users and processes should be given only the minimum access rights necessary to perform their
specific functions [CORRECT]
C. All users should have equal access to all system resources to ensure fairness
D. Privileges should be assigned based on seniority within the organization
Correct Answer: B
Rationale: The best answer is B. Least privilege is about restricting access to the bare minimum needed
for a given role or process, which limits the damage if an account is compromised. Giving everyone
admin rights or equal access defeats the entire purpose, and seniority-based access has nothing to do
with security principles. When you minimize what any single user or process can touch, you naturally
shrink your attack surface.
Q2: In the STRIDE threat modeling framework, "Tampering" refers to:
A. Modifying data or code without authorization [CORRECT]
B. Impersonating another user to gain unauthorized access
C. Denying that a transaction or action took place
D. Gaining access to information without proper authorization
Correct Answer: A
Rationale: The best answer is A. STRIDE breaks threats into six categories, and Tampering specifically
covers unauthorized modification of data in transit, at rest, or in process. Impersonation is Spoofing,
denial of actions is Repudiation, and unauthorized information access is Information Disclosure. When
you're walking through STRIDE with your team, Tampering is where you ask: "What could an attacker
change if they got between our components?"
Q3: A development team is designing a new microservices architecture for a healthcare application.
During threat modeling, they identify that an attacker could intercept API traffic between services. Using
STRIDE, this threat would be categorized as:
, A. Spoofing
B. Tampering [CORRECT]
C. Repudiation
D. Information Disclosure
Correct Answer: B
Rationale: The best answer is B. Intercepting and potentially modifying traffic between services is a
classic Man-in-the-Middle scenario, which maps directly to Tampering in STRIDE. The attacker isn't just
listening—they're positioned to alter requests or responses. While this interception could also lead to
Information Disclosure, the primary threat category for unauthorized modification of data in transit is
Tampering. The team should prioritize TLS/mTLS and message integrity checks here.
Q4: The principle of "defense in depth" suggests that:
A. A single strong security control is sufficient if properly implemented
B. Multiple overlapping security controls should be implemented so that the failure of one does not
compromise the entire system [CORRECT]
C. Security should be concentrated at the network perimeter only
D. All security controls should be implemented at the application layer
Correct Answer: B
Rationale: The best answer is B. Defense in depth means layering security controls throughout your
architecture—network, host, application, and data layers—so that no single point of failure exposes
everything. Relying on one control, concentrating everything at the perimeter, or pushing everything to
the application layer all create brittle architectures. Real-world systems get breached; the question is
whether your remaining layers can contain the damage.
Q5: In the DREAD risk assessment model, the "D" that stands for "Damage" evaluates:
A. The financial cost of implementing a security control
B. The potential impact on the business if the threat is successfully exploited [CORRECT]
C. The difficulty an attacker would face in exploiting the vulnerability
D. The number of users affected by a security patch
Exam ACTUAL EXAM 2026/2027 |
Western Governors University | Verified
Q&A | Pass Guaranteed - A+ Graded
Answer Key Included
This final examination assesses mastery of secure software design principles as taught in WGU's D487
course. It covers threat modeling, secure coding standards, authentication and access control, security
testing methodologies, and compliance with regulatory frameworks. Questions reflect real-world
software development scenarios and require both foundational knowledge and applied critical thinking
to design and evaluate secure systems.
Content Area Overview
Secure Design Principles & Threat Modeling – Covers foundational security design principles, threat
modeling using STRIDE, DREAD, and attack trees, risk assessment methodologies, and the integration of
security into the software development lifecycle.
Secure Coding Practices & Vulnerability Mitigation – Addresses OWASP Top 10 and CWE/SANS Top 25
vulnerabilities, input validation and output encoding, secure memory handling, cryptographic
implementation, error handling, logging, and secure API design.
Authentication, Authorization & Access Control – Focuses on identity management, password policies,
multifactor authentication, session management, OAuth 2.0, SAML, role-based access control (RBAC),
attribute-based access control (ABAC), and the principle of least privilege.
Application Security Testing, Deployment & Compliance – Examines static and dynamic application
security testing (SAST/DAST), penetration testing, vulnerability scanning, software composition analysis,
DevSecOps pipeline integration, and compliance with standards such as PCI-DSS, HIPAA, and GDPR.
,Section 1: Secure Design Principles & Threat Modeling – Questions 1–15
Q1: The principle of "least privilege" in secure software design means that:
A. Users should be granted administrator access to simplify troubleshooting
B. Users and processes should be given only the minimum access rights necessary to perform their
specific functions [CORRECT]
C. All users should have equal access to all system resources to ensure fairness
D. Privileges should be assigned based on seniority within the organization
Correct Answer: B
Rationale: The best answer is B. Least privilege is about restricting access to the bare minimum needed
for a given role or process, which limits the damage if an account is compromised. Giving everyone
admin rights or equal access defeats the entire purpose, and seniority-based access has nothing to do
with security principles. When you minimize what any single user or process can touch, you naturally
shrink your attack surface.
Q2: In the STRIDE threat modeling framework, "Tampering" refers to:
A. Modifying data or code without authorization [CORRECT]
B. Impersonating another user to gain unauthorized access
C. Denying that a transaction or action took place
D. Gaining access to information without proper authorization
Correct Answer: A
Rationale: The best answer is A. STRIDE breaks threats into six categories, and Tampering specifically
covers unauthorized modification of data in transit, at rest, or in process. Impersonation is Spoofing,
denial of actions is Repudiation, and unauthorized information access is Information Disclosure. When
you're walking through STRIDE with your team, Tampering is where you ask: "What could an attacker
change if they got between our components?"
Q3: A development team is designing a new microservices architecture for a healthcare application.
During threat modeling, they identify that an attacker could intercept API traffic between services. Using
STRIDE, this threat would be categorized as:
, A. Spoofing
B. Tampering [CORRECT]
C. Repudiation
D. Information Disclosure
Correct Answer: B
Rationale: The best answer is B. Intercepting and potentially modifying traffic between services is a
classic Man-in-the-Middle scenario, which maps directly to Tampering in STRIDE. The attacker isn't just
listening—they're positioned to alter requests or responses. While this interception could also lead to
Information Disclosure, the primary threat category for unauthorized modification of data in transit is
Tampering. The team should prioritize TLS/mTLS and message integrity checks here.
Q4: The principle of "defense in depth" suggests that:
A. A single strong security control is sufficient if properly implemented
B. Multiple overlapping security controls should be implemented so that the failure of one does not
compromise the entire system [CORRECT]
C. Security should be concentrated at the network perimeter only
D. All security controls should be implemented at the application layer
Correct Answer: B
Rationale: The best answer is B. Defense in depth means layering security controls throughout your
architecture—network, host, application, and data layers—so that no single point of failure exposes
everything. Relying on one control, concentrating everything at the perimeter, or pushing everything to
the application layer all create brittle architectures. Real-world systems get breached; the question is
whether your remaining layers can contain the damage.
Q5: In the DREAD risk assessment model, the "D" that stands for "Damage" evaluates:
A. The financial cost of implementing a security control
B. The potential impact on the business if the threat is successfully exploited [CORRECT]
C. The difficulty an attacker would face in exploiting the vulnerability
D. The number of users affected by a security patch
