mediummultiple choiceObjective-mapped

Exhibit

Web Access Log
2026-04-17T10:22:11Z "GET /thumb?url=http://169.254.169.254/latest/meta-data/iam/security-credentials/ HTTP/1.1" 200 512
2026-04-17T10:22:14Z "GET /thumb?url=http://10.0.5.14:8080/admin HTTP/1.1" 200 133
Application server outbound connections observed to internal RFC1918 addresses after each request.

Based on the exhibit, which attack is most likely being attempted against the application?

Question 1mediummultiple choice
Full question →

Based on the exhibit, which attack is most likely being attempted against the application?

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

Distractor review

Cross-site scripting, because the attacker is trying to inject script into the victim's browser session.

XSS targets the browser by injecting malicious script into content that other users view. The exhibit instead shows the server fetching URLs supplied by the user, including internal addresses and cloud metadata. That behavior is not browser-based script execution.

B

Best answer

Server-side request forgery, because the application is being tricked into making internal requests on the attacker's behalf.

The application accepts a URL parameter and then makes outbound requests to internal resources, including the cloud metadata endpoint. That is the hallmark of SSRF. The attacker is causing the server to reach addresses that should not normally be accessible through a public request path.

C

Distractor review

Cross-site request forgery, because the attacker is forcing an authenticated user to submit an unwanted request.

CSRF exploits a victim's browser and authenticated session to trigger actions on a different site. Here, the evidence shows the server directly making internal outbound requests based on a supplied URL. The attack does not rely on a browser session or user interaction with a forged form.

D

Distractor review

SQL injection, because the attacker is manipulating a query parameter to expose backend data.

SQL injection manipulates database queries, usually by altering SQL syntax in input fields. The log output here shows URL fetching and requests to the metadata service, not database error messages or SQL syntax anomalies. This is a request-forgery issue, not a database query injection.

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: Server-side request forgery, because the application is being tricked into making internal requests on the attacker's behalf. — The correct answer is server-side request forgery. The application accepts a URL parameter and then fetches the target on the server's behalf. The presence of requests to 169.254.169.254 is especially important because that address is commonly used for cloud instance metadata, which can expose credentials or other sensitive information. SSRF can let an attacker reach internal-only services that should never be exposed directly. Why others are wrong: XSS affects the victim's browser, not the server's outbound requests. CSRF depends on an authenticated browser session being tricked into sending a request. SQL injection manipulates database queries, which is not what the log shows. The evidence consistently points to the server making unauthorized requests to internal resources.

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.