WGU C706 Secure Software Design Pre-Assessment
2026/2027 Edition | 150 Verified Questions - 130 Questions
with Answers
WGU C706 Secure Software Design Pre-Assessment 2026-130 QUESTIONS AND ANSWERS ALREADY
GRADED A+. 100% Verified Solutions | Updated Per Latest Guidelines | Graded A+
This comprehensive exam preparation guide is meticulously crafted for the WGU C706 Secure
Software Design Pre-Assessment, reflecting the 2026/2027 academic year. It contains 150 verified
questions and expert solutions that cover the entire spectrum of secure software design principles, from
foundational security concepts to advanced threat modeling and secure coding practices. Each question
is accompanied by detailed rationales to reinforce understanding and ensure readiness for the actual
assessment. This document is an essential resource for students aiming to excel in the course and
achieve a top grade.
Key Features:
Introduction to Secure Software Design: Security fundamentals, CIA triad, security vs. functionality trade-offs
Security Requirements and Design Principles: Least privilege, defense in depth, fail-safe defaults, secure
defaults
Threat Modeling: STRIDE, DREAD, attack surfaces, threat identification and mitigation
Secure Architecture and Design: Security patterns, reference architectures, enterprise security frameworks
Secure Coding Practices: Input validation, output encoding, buffer overflows, injection flaws (SQL, XSS, etc.)
Authentication and Authorization: Identity management, access control models (RBAC, ABAC), session
management
Cryptography in Software: Symmetric/asymmetric encryption, hashing, digital signatures, key management
Security in the Software Development Lifecycle (SDLC): Integrating security in requirements, design, coding,
testing, and maintenance
Security Testing and Code Review: Static analysis, dynamic analysis, penetration testing, secure code review
techniques
Secure Deployment and Operations: Configuration management, secure release processes, incident response
Privacy and Data Protection: Data classification, anonymization, GDPR and other regulations
Emerging Trends and Future Directions: DevSecOps, cloud security, IoT security, AI/ML security
Updates for 2026:
- Updated to reflect the latest 2026/2027 WGU C706 curriculum and assessment guidelines
- Incorporated new questions on DevSecOps and cloud-native security practices
- Enhanced rationales to provide deeper explanations of correct and incorrect answer choices
- Revised content to align with current industry standards and best practices in secure software design
- Expanded coverage of privacy regulations and their impact on software design
Abstract:
This exam preparation document offers a rigorous and comprehensive review of secure software design principles
as required by the WGU C706 course. It systematically addresses the core domains of security requirements, threat
modeling, secure architecture, and secure coding, ensuring that students grasp both theoretical foundations and
practical applications. The 150 questions are designed to mirror the format and difficulty of the pre-assessment,
providing an authentic practice experience. Each solution is thoroughly explained, highlighting the reasoning
behind correct answers and common pitfalls of incorrect ones. By engaging with this material, students will
develop a robust understanding of how to design software that is resilient against contemporary cyber threats. This
Page 1
,guide is an indispensable tool for achieving a high score and mastering the essential skills of secure software
design.
Keywords:
Secure Software Design, Threat Modeling, Secure Coding, SDLC Security, Authentication, Cryptography, Security
Testing, WGU C706
Answer Format:
Each question is presented in a multiple-choice format, followed by the correct answer and a detailed rationale. The
rationale explains why the correct answer is right and why the other options are incorrect, providing comprehensive
insights into the underlying security concepts.
Compliance Checklist:
All questions are verified and aligned with the 2026/2027 WGU C706 syllabus
Each answer includes a thorough explanation to enhance learning
Content covers all major domains of secure software design
Updated to reflect the latest industry standards and best practices
Designed to simulate the actual pre-assessment experience
Suitable for self-study and exam preparation
Content Area Overview:
Content Area Questions Key Topics Weight
Foundations of Secure Software 1-20 Security basics, CIA triad, security 13%
Design principles, security vs. functionality
Security Requirements and 21-40 Least privilege, defense in depth, fail-safe 13%
Design Principles defaults, secure defaults
Threat Modeling 41-60 STRIDE, DREAD, attack surfaces, threat 13%
identification and mitigation
Secure Architecture and Design 61-80 Security patterns, reference architectures, 13%
enterprise security frameworks
Secure Coding Practices 81-100 Input validation, injection flaws, buffer 13%
overflows, output encoding
Authentication, Authorization, 101-120 Identity management, access control models, 13%
and Cryptography encryption, hashing, key management
Security in the SDLC and 121-135 Integrating security in SDLC, static/dynamic 10%
Testing analysis, penetration testing, code review
Secure Deployment, Operations, 136-150 Configuration management, DevSecOps, 10%
and Emerging Trends cloud security, privacy regulations
Page 2
,Q1. A development team uses STRIDE to analyze a new microservices-based payment
system. Which threat category is most directly addressed by implementing mutual
TLS between services?
A. Spoofing
B. Tampering
C. Repudiation
D. Information Disclosure
Correct Answer: A. Spoofing
Rationale: Mutual TLS authenticates both the client and server, preventing an attacker
from impersonating a legitimate service, which is a spoofing threat. Tampering (B) is
addressed by integrity controls, repudiation (C) by non-repudiation mechanisms, and
information disclosure (D) by encryption in transit.
Why Wrong:
B - Tampering involves altering data, which is mitigated by integrity checks, not
solely by mutual TLS.
C - Repudiation requires non-repudiation mechanisms like digital signatures, not just
mutual TLS.
D - Information disclosure is mitigated by encryption, but mutual TLS primarily
addresses authentication.
Reference: OWASP Threat Modeling, 2024
Q2. In a security code review, an auditor finds that a Java application uses
`ObjectInputStream` to deserialize data from untrusted sources. What is the most
effective mitigation to prevent deserialization attacks?
A. Use a custom `ObjectInputStream` that filters classes during deserialization.
B. Rely on Java's built-in serialization security features.
C. Encrypt the serialized data before transmission.
D. Use `Externalizable` interface for all serializable classes.
Correct Answer: A. Use a custom `ObjectInputStream` that filters classes during
deserialization.
Rationale: A custom `ObjectInputStream` with a filter that whitelists allowed classes is the
recommended defense against deserialization attacks (e.g., using `ObjectInputFilter`).
Java's built-in features (B) do not prevent gadget chains, encryption (C) does not stop
malicious payloads, and `Externalizable` (D) does not inherently secure the
deserialization process.
Why Wrong:
B - Java's default serialization does not validate the deserialized classes, leaving it
vulnerable to gadget chains.
C - Encryption only addresses confidentiality, not the execution of malicious objects
Page 3
, during deserialization.
D - Externalizable still allows arbitrary class instantiation if not properly secured.
Reference: OWASP Deserialization Cheat Sheet, 2024
Q3. An application stores encrypted user passwords. Which password storage method
is most resistant to offline brute-force attacks?
A. Salted SHA-256 hash
B. Peppered bcrypt hash
C. Unsalted MD5 hash
D. AES-256 encrypted password
Correct Answer: B. Peppered bcrypt hash
Rationale: bcrypt is a computationally expensive adaptive hash designed to resist
brute-force, and adding a pepper (secret key) further protects against database
compromise. Salted SHA-256 (A) is fast and susceptible to GPU attacks, unsalted MD5
(C) is outdated and vulnerable to rainbow tables, and AES-256 encryption (D) is
reversible if the key is compromised.
Why Wrong:
A - SHA-256 is fast, allowing attackers to attempt many guesses quickly.
C - MD5 is cryptographically broken and unsalted hashes are vulnerable to rainbow
tables.
D - Encryption is reversible, so a stolen key compromises all passwords.
Reference: OWASP Password Storage Cheat Sheet, 2024
Q4. In a multi-tenant cloud application, a developer implements an RBAC model.
Which design flaw could allow privilege escalation?
A. Roles are assigned only at the tenant level.
B. Users can create roles with permissions they do not have.
C. Permissions are scoped to resources within a tenant.
D. Role assignments are audited periodically.
Correct Answer: B. Users can create roles with permissions they do not have.
Rationale: If users can create roles with arbitrary permissions, they can grant themselves
elevated privileges, which is a classic privilege escalation flaw. Tenant-level roles (A) and
resource scoping (C) are good practices, and auditing (D) does not prevent escalation.
Why Wrong:
A - Tenant-level roles are not inherently a flaw; they can be appropriate for
multi-tenancy.
C - Resource scoping is a security best practice, not a flaw.
D - Auditing is a detective control, not a preventive one.
Page 4
2026/2027 Edition | 150 Verified Questions - 130 Questions
with Answers
WGU C706 Secure Software Design Pre-Assessment 2026-130 QUESTIONS AND ANSWERS ALREADY
GRADED A+. 100% Verified Solutions | Updated Per Latest Guidelines | Graded A+
This comprehensive exam preparation guide is meticulously crafted for the WGU C706 Secure
Software Design Pre-Assessment, reflecting the 2026/2027 academic year. It contains 150 verified
questions and expert solutions that cover the entire spectrum of secure software design principles, from
foundational security concepts to advanced threat modeling and secure coding practices. Each question
is accompanied by detailed rationales to reinforce understanding and ensure readiness for the actual
assessment. This document is an essential resource for students aiming to excel in the course and
achieve a top grade.
Key Features:
Introduction to Secure Software Design: Security fundamentals, CIA triad, security vs. functionality trade-offs
Security Requirements and Design Principles: Least privilege, defense in depth, fail-safe defaults, secure
defaults
Threat Modeling: STRIDE, DREAD, attack surfaces, threat identification and mitigation
Secure Architecture and Design: Security patterns, reference architectures, enterprise security frameworks
Secure Coding Practices: Input validation, output encoding, buffer overflows, injection flaws (SQL, XSS, etc.)
Authentication and Authorization: Identity management, access control models (RBAC, ABAC), session
management
Cryptography in Software: Symmetric/asymmetric encryption, hashing, digital signatures, key management
Security in the Software Development Lifecycle (SDLC): Integrating security in requirements, design, coding,
testing, and maintenance
Security Testing and Code Review: Static analysis, dynamic analysis, penetration testing, secure code review
techniques
Secure Deployment and Operations: Configuration management, secure release processes, incident response
Privacy and Data Protection: Data classification, anonymization, GDPR and other regulations
Emerging Trends and Future Directions: DevSecOps, cloud security, IoT security, AI/ML security
Updates for 2026:
- Updated to reflect the latest 2026/2027 WGU C706 curriculum and assessment guidelines
- Incorporated new questions on DevSecOps and cloud-native security practices
- Enhanced rationales to provide deeper explanations of correct and incorrect answer choices
- Revised content to align with current industry standards and best practices in secure software design
- Expanded coverage of privacy regulations and their impact on software design
Abstract:
This exam preparation document offers a rigorous and comprehensive review of secure software design principles
as required by the WGU C706 course. It systematically addresses the core domains of security requirements, threat
modeling, secure architecture, and secure coding, ensuring that students grasp both theoretical foundations and
practical applications. The 150 questions are designed to mirror the format and difficulty of the pre-assessment,
providing an authentic practice experience. Each solution is thoroughly explained, highlighting the reasoning
behind correct answers and common pitfalls of incorrect ones. By engaging with this material, students will
develop a robust understanding of how to design software that is resilient against contemporary cyber threats. This
Page 1
,guide is an indispensable tool for achieving a high score and mastering the essential skills of secure software
design.
Keywords:
Secure Software Design, Threat Modeling, Secure Coding, SDLC Security, Authentication, Cryptography, Security
Testing, WGU C706
Answer Format:
Each question is presented in a multiple-choice format, followed by the correct answer and a detailed rationale. The
rationale explains why the correct answer is right and why the other options are incorrect, providing comprehensive
insights into the underlying security concepts.
Compliance Checklist:
All questions are verified and aligned with the 2026/2027 WGU C706 syllabus
Each answer includes a thorough explanation to enhance learning
Content covers all major domains of secure software design
Updated to reflect the latest industry standards and best practices
Designed to simulate the actual pre-assessment experience
Suitable for self-study and exam preparation
Content Area Overview:
Content Area Questions Key Topics Weight
Foundations of Secure Software 1-20 Security basics, CIA triad, security 13%
Design principles, security vs. functionality
Security Requirements and 21-40 Least privilege, defense in depth, fail-safe 13%
Design Principles defaults, secure defaults
Threat Modeling 41-60 STRIDE, DREAD, attack surfaces, threat 13%
identification and mitigation
Secure Architecture and Design 61-80 Security patterns, reference architectures, 13%
enterprise security frameworks
Secure Coding Practices 81-100 Input validation, injection flaws, buffer 13%
overflows, output encoding
Authentication, Authorization, 101-120 Identity management, access control models, 13%
and Cryptography encryption, hashing, key management
Security in the SDLC and 121-135 Integrating security in SDLC, static/dynamic 10%
Testing analysis, penetration testing, code review
Secure Deployment, Operations, 136-150 Configuration management, DevSecOps, 10%
and Emerging Trends cloud security, privacy regulations
Page 2
,Q1. A development team uses STRIDE to analyze a new microservices-based payment
system. Which threat category is most directly addressed by implementing mutual
TLS between services?
A. Spoofing
B. Tampering
C. Repudiation
D. Information Disclosure
Correct Answer: A. Spoofing
Rationale: Mutual TLS authenticates both the client and server, preventing an attacker
from impersonating a legitimate service, which is a spoofing threat. Tampering (B) is
addressed by integrity controls, repudiation (C) by non-repudiation mechanisms, and
information disclosure (D) by encryption in transit.
Why Wrong:
B - Tampering involves altering data, which is mitigated by integrity checks, not
solely by mutual TLS.
C - Repudiation requires non-repudiation mechanisms like digital signatures, not just
mutual TLS.
D - Information disclosure is mitigated by encryption, but mutual TLS primarily
addresses authentication.
Reference: OWASP Threat Modeling, 2024
Q2. In a security code review, an auditor finds that a Java application uses
`ObjectInputStream` to deserialize data from untrusted sources. What is the most
effective mitigation to prevent deserialization attacks?
A. Use a custom `ObjectInputStream` that filters classes during deserialization.
B. Rely on Java's built-in serialization security features.
C. Encrypt the serialized data before transmission.
D. Use `Externalizable` interface for all serializable classes.
Correct Answer: A. Use a custom `ObjectInputStream` that filters classes during
deserialization.
Rationale: A custom `ObjectInputStream` with a filter that whitelists allowed classes is the
recommended defense against deserialization attacks (e.g., using `ObjectInputFilter`).
Java's built-in features (B) do not prevent gadget chains, encryption (C) does not stop
malicious payloads, and `Externalizable` (D) does not inherently secure the
deserialization process.
Why Wrong:
B - Java's default serialization does not validate the deserialized classes, leaving it
vulnerable to gadget chains.
C - Encryption only addresses confidentiality, not the execution of malicious objects
Page 3
, during deserialization.
D - Externalizable still allows arbitrary class instantiation if not properly secured.
Reference: OWASP Deserialization Cheat Sheet, 2024
Q3. An application stores encrypted user passwords. Which password storage method
is most resistant to offline brute-force attacks?
A. Salted SHA-256 hash
B. Peppered bcrypt hash
C. Unsalted MD5 hash
D. AES-256 encrypted password
Correct Answer: B. Peppered bcrypt hash
Rationale: bcrypt is a computationally expensive adaptive hash designed to resist
brute-force, and adding a pepper (secret key) further protects against database
compromise. Salted SHA-256 (A) is fast and susceptible to GPU attacks, unsalted MD5
(C) is outdated and vulnerable to rainbow tables, and AES-256 encryption (D) is
reversible if the key is compromised.
Why Wrong:
A - SHA-256 is fast, allowing attackers to attempt many guesses quickly.
C - MD5 is cryptographically broken and unsalted hashes are vulnerable to rainbow
tables.
D - Encryption is reversible, so a stolen key compromises all passwords.
Reference: OWASP Password Storage Cheat Sheet, 2024
Q4. In a multi-tenant cloud application, a developer implements an RBAC model.
Which design flaw could allow privilege escalation?
A. Roles are assigned only at the tenant level.
B. Users can create roles with permissions they do not have.
C. Permissions are scoped to resources within a tenant.
D. Role assignments are audited periodically.
Correct Answer: B. Users can create roles with permissions they do not have.
Rationale: If users can create roles with arbitrary permissions, they can grant themselves
elevated privileges, which is a classic privilege escalation flaw. Tenant-level roles (A) and
resource scoping (C) are good practices, and auditing (D) does not prevent escalation.
Why Wrong:
A - Tenant-level roles are not inherently a flaw; they can be appropriate for
multi-tenancy.
C - Resource scoping is a security best practice, not a flaw.
D - Auditing is a detective control, not a preventive one.
Page 4
