Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

WGU Secure Software Design (D487) Exam - Topic 4 Question 9 Discussion

Posted by Tayna on Apr 11, 2026 at 02:29 AM

The product development team is preparing for the production deployment of recent feature enhancements. One morning, they noticed the amount of test data grew exponentially overnight. Most fields were filled with random characters, but some structured query language was discovered.

Which type of security development lifecycle (SDL) tool was likely being used?

Suggested Answer: B

Comprehensive and Detailed In-Depth Explanation:

The scenario described indicates that the system was subjected to inputs containing random data and some structured query language (SQL) statements, leading to an exponential increase in test data. This behavior is characteristic of fuzzing, a testing technique used to identify vulnerabilities by inputting a wide range of random or unexpected data into the system.

Fuzzing aims to discover coding errors and security loopholes by bombarding the application with malformed or unexpected inputs, observing how the system responds. The presence of random characters and SQL statements suggests that the fuzzing tool was testing for vulnerabilities such as SQL injection by injecting various payloads into the system.

This approach is part of the Verification business function in the OWASP SAMM, specifically within the Security Testing practice. Security testing involves evaluating the software to identify vulnerabilities that could be exploited, and fuzzing is a common technique employed in this practice to ensure the robustness and security of the application.


OWASP SAMM: Verification - Security Testing

Get Premium Secure Software Design (D487) Questions as Interactive Web-Based Practice Test or PDF Real Exam Format Detailed Explanations Instant Access Get Your Practice Test
21 comments · newest first
GU
Gussie 1 month ago
Overall, B) Fuzzing seems most relevant here.
MA
Magda 1 month ago
I feel like C) Threat model could apply too, but not as likely.
FE
Felix 1 month ago
True, but the random characters suggest B) Fuzzing was used.
DA
Daniel 2 months ago
But what about A) Dynamic analysis? It checks running apps.
AU
Audra 2 months ago
I agree! Fuzzing tests for unexpected input.
LA
Laura 2 months ago
This is tricky! I think B) Fuzzing fits best.
TE
Tegan 2 months ago
Overall, B) Fuzzing seems most likely. It’s all about unexpected input.
YA
Yaeko 2 months ago
I lean towards D) Static analysis. It checks code before execution.
HE
Hermila 2 months ago
I feel like C) Threat model could apply too. It identifies risks.
RO
Robt 3 months ago
But what about A) Dynamic analysis? It tests during runtime.
JU
Julianna 3 months ago
I agree, B) Fuzzing makes sense. Random data fits.
SA
Salena 3 months ago
This is tricky! I think it's B) Fuzzing.
TI
Tiera 3 months ago
Nah, I’m leaning towards D) Static analysis. Just a hunch!
TO
Tommy 3 months ago
I think it could also be A) Dynamic analysis, but fuzzing fits better.
LI
Lindsey 4 months ago
Wait, how did they get SQL in there? That's kinda weird.
EM
Emily 5 months ago
Definitely B) Fuzzing! Makes sense with the random data.
SH
Shelton 5 months ago
Sounds like they were using fuzzing to test inputs.
RO
Roselle 6 months ago
Static analysis sounds familiar, but I don't think it would generate random data like that. Fuzzing seems more likely based on what we practiced.
HE
Helaine 6 months ago
I feel like threat modeling is more about identifying risks beforehand, so it probably isn't the right answer here.
CH
Cheryll 6 months ago
I'm not entirely sure, but I think dynamic analysis could also be a possibility since it deals with how the application behaves with inputs.
SC
Scot 6 months ago
I remember we discussed fuzzing in class, and it seems like it fits since the data was random and might have been used to test for vulnerabilities.
0/2000 characters

Save Cancel