The correct answers are Static Application Security Testing (SAST) and Software Composition Analysis (SCA). SAST works by scanning source code, bytecode, or binaries without execution to catch flaws like SQL injection and buffer overflows early in development, while SCA identifies known vulnerabilities in third-party libraries and open-source dependencies by cross-referencing them against databases like the NVD. On the CompTIA SecurityX CAS-004 exam, this tests your understanding of shift-left security and the distinction between analyzing custom code versus supply chain components—a common trap is confusing SAST with DAST, which requires a running application. Remember the mnemonic: SAST scans your own code, SCA scans what you borrowed.
CAS-004 Security Engineering Practice Question
This CAS-004 practice question tests your understanding of security engineering. Match the stated requirement to the specific cloud service, access model, or configuration option — many options are valid in isolation but not for this scenario. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.
A security architect is designing a secure software development pipeline. The organization wants to ensure that code is thoroughly analyzed before deployment. Which TWO of the following should be integrated into the pipeline to identify vulnerabilities early? (Select TWO.)
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Static application security testing (SAST)
SAST (Static Application Security Testing) analyzes source code, bytecode, or binary code without executing it, scanning for vulnerabilities like SQL injection, buffer overflows, and insecure cryptographic functions. Integrating SAST early in the pipeline (shift-left) allows developers to fix issues before compilation, reducing remediation cost and risk. SCA (Software Composition Analysis) identifies known vulnerabilities in third-party libraries and open-source components by comparing dependency versions against databases like the National Vulnerability Database (NVD). Both tools are non-intrusive and can be automated in CI/CD pipelines to catch flaws before deployment.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
✓
Static application security testing (SAST)
Why this is correct
SAST analyzes source code without executing it, identifying vulnerabilities early.
Related concept
Read the scenario before looking for a memorised answer.
✓
Software composition analysis (SCA)
Why this is correct
SCA scans dependencies for known vulnerabilities in open-source libraries.
Related concept
Read the scenario before looking for a memorised answer.
✗
Fuzz testing
Why it's wrong here
Fuzz testing is a dynamic technique that requires a running application.
✗
Dynamic application security testing (DAST)
Why it's wrong here
DAST is performed on a running application, which is later in the pipeline.
✗
Penetration testing
Why it's wrong here
Penetration testing is typically performed on deployed systems, not in the build pipeline.
Common exam traps
Common exam trap: answer the scenario, not the keyword
Cisco often tests the distinction between static and dynamic analysis by presenting SAST and DAST as equally valid early-stage options, but the trap is that DAST requires a running application and cannot be integrated before deployment, making SAST and SCA the only correct choices for early vulnerability identification.
Detailed technical explanation
How to think about this question
SAST tools parse the abstract syntax tree (AST) and control flow graphs to detect patterns matching known vulnerability signatures, such as taint propagation from user input to dangerous sinks (e.g., exec() or eval()). SCA tools generate a software bill of materials (SBOM) and cross-reference each dependency’s Common Platform Enumeration (CPE) against CVE entries; a subtle behavior is that transitive dependencies (dependencies of dependencies) are often overlooked, but SCA can recursively resolve them to uncover hidden risks like the Log4Shell vulnerability (CVE-2021-44228). In a real-world pipeline, SAST and SCA are typically run on every commit, while DAST and fuzzing are reserved for later stages or scheduled regression tests.
KKey Concepts to Remember
Read the scenario before looking for a memorised answer.
Find the constraint that changes the correct option.
Eliminate answers that are true in general but not in this case.
TExam Day Tips
→Watch for words such as best, first, most likely and least administrative effort.
→Review why wrong options are wrong, not only why the correct option is correct.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
How this comes up in practice
A small business has 20 workstations on the 192.168.1.0/24 network and one public IP from its ISP. The router uses PAT (NAT overload) so all 20 devices share one public address using different source ports. NAT questions test whether you understand the four address terms and which direction each translation applies.
What to study next
Got this wrong? Here's your next step.
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
Security Engineering — This question tests Security Engineering — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: Static application security testing (SAST) — SAST (Static Application Security Testing) analyzes source code, bytecode, or binary code without executing it, scanning for vulnerabilities like SQL injection, buffer overflows, and insecure cryptographic functions. Integrating SAST early in the pipeline (shift-left) allows developers to fix issues before compilation, reducing remediation cost and risk. SCA (Software Composition Analysis) identifies known vulnerabilities in third-party libraries and open-source components by comparing dependency versions against databases like the National Vulnerability Database (NVD). Both tools are non-intrusive and can be automated in CI/CD pipelines to catch flaws before deployment.
What should I do if I get this CAS-004 question wrong?
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
What is the key concept behind this question?
Read the scenario before looking for a memorised answer.
About these practice questions
Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
This CAS-004 practice question is part of Courseiva's free CompTIA certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the CAS-004 exam.
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
Sign in to join the discussion.