The answer is a supply-chain compromise, because the dependency may have been altered before it reached the build pipeline. This is the most likely issue because the exhibit depicts a CI/CD pipeline fetching a dependency from a public repository, where attackers can inject malicious code into popular open-source packages. Once tampered, that compromised dependency is pulled into the build, infecting the final software component—a classic supply chain compromise scenario. On the Security+ SY0-701 exam, this concept tests your ability to identify risks in the software development lifecycle, often appearing in scenario-based questions where a trusted library behaves unexpectedly. A common trap is to blame a misconfigured pipeline or a code error, but the key is recognizing that the threat entered before the build started. Memory tip: “If the code came from outside, check the supply chain ride.”
SY0-701 Threats, Vulnerabilities, and Mitigations Practice Question
This SY0-701 practice question tests your understanding of threats, vulnerabilities, and mitigations. The scenario asks you to isolate a root cause — eliminate options that address a different problem before choosing. 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.
Exhibit
CI Build Output
Downloading package: report-utils@4.2.0
Expected integrity: sha512-F3d9e2f0e3a9c1...
Actual integrity: sha512-7ab4d1c19f0a22...
Source registry: registry.example.net
Build status: WARN - package checksum mismatch
Developer note: The update was pulled automatically during the nightly pipeline.
Based on the exhibit, what is the most likely issue with the software component being built?
Clue words in this question
Noticing these words before you look at the options changes how you read each choice.
Clue: "most likely"
Why it matters: Probability qualifier — the question wants the most probable cause or outcome, not a guaranteed one. Eliminate low-probability options.
CI Build Output
Downloading package: report-utils@4.2.0
Expected integrity: sha512-F3d9e2f0e3a9c1...
Actual integrity: sha512-7ab4d1c19f0a22...
Source registry: registry.example.net
Build status: WARN - package checksum mismatch
Developer note: The update was pulled automatically during the nightly pipeline.
A
Supply-chain compromise, because the dependency may have been altered before it reached the build pipeline.
A checksum or integrity mismatch during an automated dependency pull is a strong sign that the package may have been tampered with in transit or replaced in the software supply chain. Because the build pipeline trusted the registry source automatically, the control failure is around dependency integrity and third-party trust.
B
Cross-site scripting, because the package name suggests the application handles web content.
Why wrong: XSS is a web application attack involving malicious script in user-facing content. The exhibit is about a build pipeline downloading a package and comparing integrity values. There is no browser, user input field, or script execution evidence here.
C
Credential stuffing, because automated systems frequently reuse credentials during updates.
Why wrong: Credential stuffing relies on stolen username and password pairs being tried against logins. The log shows package download integrity validation, not authentication attempts. No user account access or password reuse is indicated in the build output.
D
Replay attack, because the nightly pipeline used an old copy of the package request.
Why wrong: Replay attacks involve capturing and resending valid communications to trick a system. Here, the issue is that the downloaded package's integrity does not match the expected value. That points to package tampering or dependency compromise, not a duplicated authentication message.
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Supply-chain compromise, because the dependency may have been altered before it reached the build pipeline.
The exhibit shows a build pipeline that fetches a dependency from a public repository. If the dependency has been tampered with before it reaches the pipeline, this is a classic supply-chain compromise. Attackers often inject malicious code into popular open-source packages, which then gets incorporated into the build, compromising the final software component.
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.
✓
Supply-chain compromise, because the dependency may have been altered before it reached the build pipeline.
Why this is correct
A checksum or integrity mismatch during an automated dependency pull is a strong sign that the package may have been tampered with in transit or replaced in the software supply chain. Because the build pipeline trusted the registry source automatically, the control failure is around dependency integrity and third-party trust.
Clue confirmation
The clue word "most likely" in the question point toward this answer.
Related concept
Read the scenario before looking for a memorised answer.
✗
Cross-site scripting, because the package name suggests the application handles web content.
Why it's wrong here
XSS is a web application attack involving malicious script in user-facing content. The exhibit is about a build pipeline downloading a package and comparing integrity values. There is no browser, user input field, or script execution evidence here.
✗
Credential stuffing, because automated systems frequently reuse credentials during updates.
Why it's wrong here
Credential stuffing relies on stolen username and password pairs being tried against logins. The log shows package download integrity validation, not authentication attempts. No user account access or password reuse is indicated in the build output.
✗
Replay attack, because the nightly pipeline used an old copy of the package request.
Why it's wrong here
Replay attacks involve capturing and resending valid communications to trick a system. Here, the issue is that the downloaded package's integrity does not match the expected value. That points to package tampering or dependency compromise, not a duplicated authentication message.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates may confuse a supply-chain compromise with a web-specific attack like XSS, but the question's context of a build pipeline and dependency fetching points directly to the integrity of the software supply chain.
Trap categories for this question
Command / output trap
Credential stuffing relies on stolen username and password pairs being tried against logins. The log shows package download integrity validation, not authentication attempts. No user account access or password reuse is indicated in the build output.
Detailed technical explanation
How to think about this question
Supply-chain attacks often exploit the trust in package managers like npm, PyPI, or Maven. Attackers may publish a malicious version of a legitimate package (typosquatting) or compromise the maintainer's account to push a backdoored update. The build pipeline's lack of integrity verification (e.g., checksum validation or signing) makes it vulnerable to such attacks, as the dependency is fetched without confirming its authenticity.
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 security analyst at a medium-sized enterprise encounters this scenario during an investigation or architecture review. The correct answer reflects best practice for the specific threat or control described. Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option. Security exam questions test whether you can match controls to threats in context — not just recall definitions.
Related glossary terms
Concepts from this question explained
These glossary pages explain the core terms tested in this SY0-701 question in full detail.
Threats, Vulnerabilities, and Mitigations — This question tests Threats, Vulnerabilities, and Mitigations — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: Supply-chain compromise, because the dependency may have been altered before it reached the build pipeline. — The exhibit shows a build pipeline that fetches a dependency from a public repository. If the dependency has been tampered with before it reaches the pipeline, this is a classic supply-chain compromise. Attackers often inject malicious code into popular open-source packages, which then gets incorporated into the build, compromising the final software component.
What should I do if I get this SY0-701 question wrong?
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
Are there clue words in this question I should notice?
Yes — watch for: "most likely". Probability qualifier — the question wants the most probable cause or outcome, not a guaranteed one. Eliminate low-probability options.
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 SY0-701 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 SY0-701 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.