mediummultiple choiceObjective-mapped

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?

Question 1mediummultiple choice
Full question →

Based on the exhibit, what is the most likely issue with the software component being built?

Answer choices

Why each option matters

Good practice is not just finding the correct option. The wrong answers often show the exact trap the exam wants you to fall into.

A

Best answer

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

Distractor review

Cross-site scripting, because the package name suggests the application handles web content.

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

Distractor review

Credential stuffing, because automated systems frequently reuse credentials during updates.

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

Distractor review

Replay attack, because the nightly pipeline used an old copy of the package request.

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 trap

Common exam trap: answer the scenario, not the keyword

Many certification questions include familiar terms but test a specific constraint. Read the exact wording before choosing an answer that is generally true but wrong for this case.

Technical deep dive

How to think about this question

This question should be treated as a scenario, not a definition check. Identify the problem, the constraint and the best action. Then compare each option against those facts.

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.
  • Use explanations to understand the rule behind the answer.

TExam Day Tips

  • Underline the problem statement mentally.
  • 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.

Related practice questions

Related SY0-701 practice-question pages

Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.

More questions from this exam

Keep practising from the same exam bank, or move into a focused topic page if this question exposed a weak area.

FAQ

Questions learners often ask

What does this SY0-701 question test?

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 best answer is supply-chain compromise. The package hash does not match the expected integrity value, which means the dependency may have been altered, replaced, or otherwise corrupted before the build consumed it. In modern software environments, this is a serious third-party risk because malicious or tampered dependencies can introduce backdoors into production through an otherwise trusted pipeline. Why others are wrong: XSS is unrelated to package integrity checks and browser content. Credential stuffing concerns login attempts, not build artifacts. Replay attacks involve resending captured communications, which does not explain a checksum mismatch on a downloaded library. The scenario is about dependency trust and integrity in the software supply chain.

What should I do if I get this SY0-701 question wrong?

Then try more questions from the same exam bank and focus on understanding why the wrong options are tempting.

Discussion

Loading comments…

Sign in to join the discussion.