Free Secure-Software-Design Exam Braindumps
WGU Secure Software Design (D487, KEO1) Questions 41–45 (page: 10)

Updated On: 11-Feb-2026

Which type of security analysis is limited by the fact that a significant time investment of a highly skilled team member is required?

  1. Fuzz testing
  2. Dynamic code analysis
  3. Manual code review
  4. Static code analysis

Answer(s): C

Explanation:

Manual code review is a type of security analysis that requires a significant time investment from a highly skilled team member. This process involves a detailed and thorough examination of the source code to identify security vulnerabilities that automated tools might miss. It is labor-intensive because it relies on the expertise of the reviewer to understand the context, logic, and potential security implications of the code. Unlike automated methods like static or dynamic code analysis, manual code review demands a deep understanding of the codebase, which can be time-consuming and requires a high level of skill and experience.


Reference:

The information provided here is based on industry best practices and standards for secure software design and development, as well as my understanding of security analysis methodologies12.



Which design and development deliverable contains the results of each type of evaluation that was performed and the type and number of vulnerabilities discovered?

  1. Security test execution report
  2. Security testing reports
  3. Privacy compliance report
  4. Remediation report

Answer(s): B

Explanation:

Security testing reports are the deliverables that typically contain detailed results of the security evaluations performed. These reports include the types of tests conducted, such as static and dynamic analysis, penetration testing, and code reviews, as well as the number and types of vulnerabilities discovered. The purpose of these reports is to document the security posture of the software at the time of testing and to provide a basis for remediation efforts.


Reference:

The information aligns with best practices in secure software development, which emphasize the importance of documenting security requirements and conducting risk analysis during the design phase to identify and mitigate vulnerabilities early in the SDLC12.



Which type of security analysis is performed using automated software tools while an application is running and is most commonly executed during the testing phase of the SDLC?

  1. Dynamic analysis
  2. Manual code review
  3. Static analysis
  4. Fuzz testing

Answer(s): A

Explanation:

Dynamic analysis is a security testing method that involves analyzing the behavior of software while it is running or in execution. It is most commonly executed during the testing phase of the Software Development Life Cycle (SDLC). This type of analysis is used to detect issues that might not be visible in the code's static state, such as runtime errors and memory leaks. Automated tools are employed to perform dynamic analysis, which can simulate attacks on the application and identify vulnerabilities that could be exploited by malicious actors.


Reference:

The information provided here is verified by multiple sources that discuss security automation in the SDLC and the role of dynamic analysis during the testing phase123.



Which type of manual code review technique is being used when the reviewer starts at an input control and traces its value through the application to each of the value's outputs?

  1. Risk analysis
  2. Control flow analysis
  3. Data flow analysis
  4. Threat analysis

Answer(s): C

Explanation:

Data flow analysis is a manual code review technique where the reviewer traces the path of data from its entry point in the software (input control) through its processing and manipulation within the application, to its exit points (outputs). This technique is used to ensure that the data is handled securely throughout its lifecycle within the application and to identify any potential security vulnerabilities that may arise from improper data handling or processing12



What is the last slop of the SDLOSDL code review process?

  1. Review for security issues unique to the architecture
  2. Identify security code review objectives
  3. Perform preliminary scan
  4. Review code for security issues

Answer(s): D

Explanation:

The last step of the SDLC code review process is to review the code for security issues. This involves a detailed examination of the code to identify any potential security vulnerabilities that could be exploited. It's a critical phase where the focus is on ensuring that the code adheres to security best practices and does not contain any flaws that could compromise the security of the application or system. The process typically includes manual inspection as well as automated tools to scan for common security issues. The goal is to ensure that the software is as secure as possible before it is deployed.


Reference:

Mastering the Code Review Process, Understanding the SDLC, How Code Reviews Improve Software Quality in SDLC - LinkedIn.



Viewing page 10 of 25
Viewing questions 46 - 50 out of 118 questions


Post your Comments and Discuss WGU Secure-Software-Design exam prep with other Community members:

AI Tutor AI Tutor 👋 I’m here to help!