WGU D487 Secure Software Design Objective Assessment
(OA) Exam Prep Document | 2026/2027 Edition | 250 Verified
Questions
WGU D487 Secure Software Design OA Exam 2026-2027 QUESTIONS AND ANSWERS ALREADY GRADED A+.
100% Verified Solutions | Updated Per Latest Guidelines | Graded A+
This comprehensive exam preparation document contains 250 verified questions and expert rationales
for the WGU D487 Secure Software Design Objective Assessment. Each question is aligned with the
latest 2026 curriculum updates, ensuring you study the most current material. The bank covers all key
domains including secure design principles, threat modeling, secure coding practices, and security
testing. Expert rationales provide in-depth explanations for correct and incorrect answers, reinforcing
critical concepts. Ideal for students aiming to achieve a high pass rate on the OA.
Key Features:
Secure Design Principles and Best Practices
Threat Modeling and Risk Assessment
Secure Coding and Input Validation
Authentication, Authorization, and Access Control
Security Testing and Vulnerability Analysis
Cryptography and Data Protection
Updates for 2026:
- Updated to reflect 2026 WGU D487 curriculum changes
- Added new questions on DevSecOps and CI/CD security
- Enhanced rationales with step-by-step reasoning
- Revised distractor explanations to address common misconceptions
- Incorporated feedback from recent exam takers
Abstract:
The WGU D487 Secure Software Design Objective Assessment (OA) exam evaluates a student's mastery of secure
software development principles and practices. This exam bank comprises 250 verified questions meticulously
curated to mirror the format and difficulty of the actual OA. Each question is accompanied by an expert rationale
that not only explains the correct answer but also clarifies why the other options are incorrect, thereby deepening
conceptual understanding. The content is organized into key domains: secure design principles, threat modeling,
secure coding, authentication and access control, security testing, and cryptography. The 2026 update integrates
contemporary topics such as DevSecOps, API security, and cloud-native application security. By engaging with
this resource, students can systematically identify knowledge gaps, reinforce learning, and build confidence for
exam day. The rationales are written in a scholarly tone, consistent with professional exam prep standards, and
are designed to promote critical thinking rather than rote memorization. This document serves as both a study
guide and a self-assessment tool, enabling targeted review of high-weight areas. With a 100% verified accuracy
guarantee, students can trust that the content reflects the most current exam blueprint and industry best practices.
Keywords:
WGU D487, Secure Software Design, OA Exam Bank, Verified Questions, Expert Rationales, 2026 Update, Secure
Coding, Threat Modeling
Answer Format:
Each question is followed by the correct answer and a detailed rationale. The rationale explains the underlying
concept, why the correct answer is right, and why each distractor is wrong. Distractors are analyzed to address
Page 1
,common errors and misconceptions, ensuring comprehensive understanding.
Compliance Checklist:
All questions verified against 2026 WGU D487 OA blueprint
Expert rationales reviewed by subject matter experts
Updated to include latest secure design standards and frameworks
Distractor explanations provided for all incorrect options
Content organized by exam domains with weight percentages
Suitable for self-assessment and targeted study
Content Area Overview:
Content Area Questions Key Topics Weight
Secure Design Principles 1-50 Least privilege, defense in depth, secure 20%
defaults, fail secure, separation of duties
Threat Modeling and Risk 51-100 STRIDE, DREAD, attack trees, risk 20%
Assessment mitigation strategies, threat intelligence
Secure Coding and Input 101-150 Input validation, output encoding, buffer 20%
Validation overflow prevention, SQL injection, XSS
Authentication, Authorization, 151-190 Password policies, multi-factor 16%
and Access Control authentication, RBAC, ABAC, session
management
Security Testing and 191-220 Static analysis, dynamic analysis, 12%
Vulnerability Analysis penetration testing, fuzzing, vulnerability
scanning
Cryptography and Data 221-250 Symmetric vs asymmetric encryption, 12%
Protection hashing, digital signatures, TLS, key
management
Page 2
,Q1. A developer proposes using the same RSA key pair for both signing and encryption in a
microservice architecture. Which of the following is the most significant security concern with this
approach?
A. Increased computational overhead due to repeated key generation
B. Potential for key recovery through known-plaintext attacks on the encryption scheme
C. Loss of non-repudiation because the signing key is exposed to encryption operations
D. Violation of the principle of key separation, enabling chosen-ciphertext attacks to forge signatures
Correct Answer: D. Violation of the principle of key separation, enabling chosen-ciphertext attacks
to forge signatures
Rationale: Using the same key for both signing and encryption violates key separation. Chosen-ciphertext
attacks on the encryption oracle can be leveraged to produce valid signatures, breaking non-repudiation.
Known-plaintext attacks (B) are not a direct threat to RSA encryption, and key separation is a
fundamental cryptographic principle.
Why Wrong:
A - Computational overhead is not the primary security concern; key separation is.
B - Known-plaintext attacks on RSA are not feasible with proper padding; this misses the core issue.
C - Non-repudiation is already compromised by the shared key, but the mechanism is through
chosen-ciphertext attacks, not exposure during encryption operations.
Reference: Anderson, R. (2020). Security Engineering, 3rd Ed., Ch. 5; NIST SP 800-175B
Q2. In a threat modeling session using STRIDE, a software architect identifies a threat where an
attacker can modify the contents of a log file after it is written. Under which STRIDE category does
this threat fall?
A. Spoofing
B. Tampering
C. Repudiation
D. Elevation of Privilege
Correct Answer: B. Tampering
Rationale: Tampering involves unauthorized modification of data or code. Modifying a log file after it is
written is a clear example of tampering. Spoofing (A) relates to impersonation, repudiation (C) to denying
actions, and elevation of privilege (D) to gaining unauthorized access.
Why Wrong:
A - Spoofing is about impersonation, not data modification.
C - Repudiation concerns the ability to deny an action, not the act of modifying data.
D - Elevation of privilege involves gaining higher-level access, not modifying existing data.
Reference: Shostack, A. (2014). Threat Modeling: Designing for Security, Ch. 5
Page 3
, Q3. A web application allows users to upload profile pictures that are stored on the server and
served with the original filename. Which of the following attacks is most directly enabled by this
design?
A. Cross-Site Request Forgery (CSRF)
B. Server-Side Request Forgery (SSRF)
C. Path traversal via filename injection
D. SQL injection through metadata
Correct Answer: C. Path traversal via filename injection
Rationale: Using the original filename without sanitization allows an attacker to craft filenames like
'../../etc/passwd', leading to path traversal. CSRF (A) requires cross-origin requests, SSRF (B) involves
server making requests, and SQL injection (D) requires database interaction, not file storage.
Why Wrong:
A - CSRF is about unauthorized actions from authenticated users, not file uploads.
B - SSRF involves the server making unintended requests, not file path manipulation.
D - SQL injection is not directly enabled by filenames; it requires database queries.
Reference: OWASP Top 10 2021: A01-Broken Access Control; OWASP File Upload Cheat Sheet
Q4. A development team is implementing password storage for a new application. They decide to
use SHA-256 hashing without a salt. Which of the following best describes the primary vulnerability
of this approach?
A. SHA-256 is too slow for password hashing, causing denial of service
B. Without salt, identical passwords produce identical hashes, enabling rainbow table attacks
C. SHA-256 is a broken hash function and should not be used
D. The lack of a salt allows for easy key stretching
Correct Answer: B. Without salt, identical passwords produce identical hashes, enabling rainbow
table attacks
Rationale: Unsalted hashes allow attackers to precompute rainbow tables for common passwords,
making it trivial to reverse many hashes. SHA-256 is not broken (C), but it is not designed for password
hashing; however, the immediate vulnerability is the lack of salt. Key stretching (D) is unrelated to
salting.
Why Wrong:
A - SHA-256 is fast, but that is not the primary vulnerability; speed actually helps attackers.
C - SHA-256 is still considered secure for integrity checks; the issue is suitability for passwords.
D - Key stretching is a separate technique (e.g., bcrypt, PBKDF2); lack of salt does not enable it.
Reference: NIST SP 800-63B; OWASP Password Storage Cheat Sheet
Page 4
(OA) Exam Prep Document | 2026/2027 Edition | 250 Verified
Questions
WGU D487 Secure Software Design OA Exam 2026-2027 QUESTIONS AND ANSWERS ALREADY GRADED A+.
100% Verified Solutions | Updated Per Latest Guidelines | Graded A+
This comprehensive exam preparation document contains 250 verified questions and expert rationales
for the WGU D487 Secure Software Design Objective Assessment. Each question is aligned with the
latest 2026 curriculum updates, ensuring you study the most current material. The bank covers all key
domains including secure design principles, threat modeling, secure coding practices, and security
testing. Expert rationales provide in-depth explanations for correct and incorrect answers, reinforcing
critical concepts. Ideal for students aiming to achieve a high pass rate on the OA.
Key Features:
Secure Design Principles and Best Practices
Threat Modeling and Risk Assessment
Secure Coding and Input Validation
Authentication, Authorization, and Access Control
Security Testing and Vulnerability Analysis
Cryptography and Data Protection
Updates for 2026:
- Updated to reflect 2026 WGU D487 curriculum changes
- Added new questions on DevSecOps and CI/CD security
- Enhanced rationales with step-by-step reasoning
- Revised distractor explanations to address common misconceptions
- Incorporated feedback from recent exam takers
Abstract:
The WGU D487 Secure Software Design Objective Assessment (OA) exam evaluates a student's mastery of secure
software development principles and practices. This exam bank comprises 250 verified questions meticulously
curated to mirror the format and difficulty of the actual OA. Each question is accompanied by an expert rationale
that not only explains the correct answer but also clarifies why the other options are incorrect, thereby deepening
conceptual understanding. The content is organized into key domains: secure design principles, threat modeling,
secure coding, authentication and access control, security testing, and cryptography. The 2026 update integrates
contemporary topics such as DevSecOps, API security, and cloud-native application security. By engaging with
this resource, students can systematically identify knowledge gaps, reinforce learning, and build confidence for
exam day. The rationales are written in a scholarly tone, consistent with professional exam prep standards, and
are designed to promote critical thinking rather than rote memorization. This document serves as both a study
guide and a self-assessment tool, enabling targeted review of high-weight areas. With a 100% verified accuracy
guarantee, students can trust that the content reflects the most current exam blueprint and industry best practices.
Keywords:
WGU D487, Secure Software Design, OA Exam Bank, Verified Questions, Expert Rationales, 2026 Update, Secure
Coding, Threat Modeling
Answer Format:
Each question is followed by the correct answer and a detailed rationale. The rationale explains the underlying
concept, why the correct answer is right, and why each distractor is wrong. Distractors are analyzed to address
Page 1
,common errors and misconceptions, ensuring comprehensive understanding.
Compliance Checklist:
All questions verified against 2026 WGU D487 OA blueprint
Expert rationales reviewed by subject matter experts
Updated to include latest secure design standards and frameworks
Distractor explanations provided for all incorrect options
Content organized by exam domains with weight percentages
Suitable for self-assessment and targeted study
Content Area Overview:
Content Area Questions Key Topics Weight
Secure Design Principles 1-50 Least privilege, defense in depth, secure 20%
defaults, fail secure, separation of duties
Threat Modeling and Risk 51-100 STRIDE, DREAD, attack trees, risk 20%
Assessment mitigation strategies, threat intelligence
Secure Coding and Input 101-150 Input validation, output encoding, buffer 20%
Validation overflow prevention, SQL injection, XSS
Authentication, Authorization, 151-190 Password policies, multi-factor 16%
and Access Control authentication, RBAC, ABAC, session
management
Security Testing and 191-220 Static analysis, dynamic analysis, 12%
Vulnerability Analysis penetration testing, fuzzing, vulnerability
scanning
Cryptography and Data 221-250 Symmetric vs asymmetric encryption, 12%
Protection hashing, digital signatures, TLS, key
management
Page 2
,Q1. A developer proposes using the same RSA key pair for both signing and encryption in a
microservice architecture. Which of the following is the most significant security concern with this
approach?
A. Increased computational overhead due to repeated key generation
B. Potential for key recovery through known-plaintext attacks on the encryption scheme
C. Loss of non-repudiation because the signing key is exposed to encryption operations
D. Violation of the principle of key separation, enabling chosen-ciphertext attacks to forge signatures
Correct Answer: D. Violation of the principle of key separation, enabling chosen-ciphertext attacks
to forge signatures
Rationale: Using the same key for both signing and encryption violates key separation. Chosen-ciphertext
attacks on the encryption oracle can be leveraged to produce valid signatures, breaking non-repudiation.
Known-plaintext attacks (B) are not a direct threat to RSA encryption, and key separation is a
fundamental cryptographic principle.
Why Wrong:
A - Computational overhead is not the primary security concern; key separation is.
B - Known-plaintext attacks on RSA are not feasible with proper padding; this misses the core issue.
C - Non-repudiation is already compromised by the shared key, but the mechanism is through
chosen-ciphertext attacks, not exposure during encryption operations.
Reference: Anderson, R. (2020). Security Engineering, 3rd Ed., Ch. 5; NIST SP 800-175B
Q2. In a threat modeling session using STRIDE, a software architect identifies a threat where an
attacker can modify the contents of a log file after it is written. Under which STRIDE category does
this threat fall?
A. Spoofing
B. Tampering
C. Repudiation
D. Elevation of Privilege
Correct Answer: B. Tampering
Rationale: Tampering involves unauthorized modification of data or code. Modifying a log file after it is
written is a clear example of tampering. Spoofing (A) relates to impersonation, repudiation (C) to denying
actions, and elevation of privilege (D) to gaining unauthorized access.
Why Wrong:
A - Spoofing is about impersonation, not data modification.
C - Repudiation concerns the ability to deny an action, not the act of modifying data.
D - Elevation of privilege involves gaining higher-level access, not modifying existing data.
Reference: Shostack, A. (2014). Threat Modeling: Designing for Security, Ch. 5
Page 3
, Q3. A web application allows users to upload profile pictures that are stored on the server and
served with the original filename. Which of the following attacks is most directly enabled by this
design?
A. Cross-Site Request Forgery (CSRF)
B. Server-Side Request Forgery (SSRF)
C. Path traversal via filename injection
D. SQL injection through metadata
Correct Answer: C. Path traversal via filename injection
Rationale: Using the original filename without sanitization allows an attacker to craft filenames like
'../../etc/passwd', leading to path traversal. CSRF (A) requires cross-origin requests, SSRF (B) involves
server making requests, and SQL injection (D) requires database interaction, not file storage.
Why Wrong:
A - CSRF is about unauthorized actions from authenticated users, not file uploads.
B - SSRF involves the server making unintended requests, not file path manipulation.
D - SQL injection is not directly enabled by filenames; it requires database queries.
Reference: OWASP Top 10 2021: A01-Broken Access Control; OWASP File Upload Cheat Sheet
Q4. A development team is implementing password storage for a new application. They decide to
use SHA-256 hashing without a salt. Which of the following best describes the primary vulnerability
of this approach?
A. SHA-256 is too slow for password hashing, causing denial of service
B. Without salt, identical passwords produce identical hashes, enabling rainbow table attacks
C. SHA-256 is a broken hash function and should not be used
D. The lack of a salt allows for easy key stretching
Correct Answer: B. Without salt, identical passwords produce identical hashes, enabling rainbow
table attacks
Rationale: Unsalted hashes allow attackers to precompute rainbow tables for common passwords,
making it trivial to reverse many hashes. SHA-256 is not broken (C), but it is not designed for password
hashing; however, the immediate vulnerability is the lack of salt. Key stretching (D) is unrelated to
salting.
Why Wrong:
A - SHA-256 is fast, but that is not the primary vulnerability; speed actually helps attackers.
C - SHA-256 is still considered secure for integrity checks; the issue is suitability for passwords.
D - Key stretching is a separate technique (e.g., bcrypt, PBKDF2); lack of salt does not enable it.
Reference: NIST SP 800-63B; OWASP Password Storage Cheat Sheet
Page 4
