hardmultiple choiceObjective-mapped

A SaaS portal issues signed JWTs in a browser cookie. The help desk confirms a user logged out at 09:10, but SIEM logs show the same token was accepted from a different IP at 09:12 and continued working until the token expired. The application does not keep a server-side revocation list. What weakness is most likely being abused?

Question 1hardmultiple choice
Full question →

A SaaS portal issues signed JWTs in a browser cookie. The help desk confirms a user logged out at 09:10, but SIEM logs show the same token was accepted from a different IP at 09:12 and continued working until the token expired. The application does not keep a server-side revocation list. What weakness is most likely being abused?

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

SQL injection, because the attacker must be manipulating backend database logic to reuse the token.

SQL injection targets database queries. Reusing a valid token after logout is a session-handling problem, not evidence of SQL query manipulation.

B

Best answer

Session hijacking or session abuse, because the attacker can replay a valid token after logout without revocation.

This is session hijacking or session abuse because the attacker is using a valid session token outside the original user context. JWTs are often stateless, so if the application does not track revocation, logout may not immediately invalidate a copied token. The cross-IP reuse after logout strongly suggests the token was stolen or replayed and remained acceptable until its normal expiration.

C

Distractor review

Insecure deserialization, because the token is being decoded and reconstructed on the server.

Insecure deserialization involves unsafe object reconstruction from attacker-controlled data. A replayed JWT does not by itself indicate object deserialization abuse.

D

Distractor review

Cross-site request forgery, because the request is coming from a different IP address.

CSRF abuses a victim's browser to send unwanted requests with ambient authority. The scenario instead shows direct token replay from another source after logout, which is a session theft or abuse problem.

Common exam trap

Common exam trap: NAT rules depend on direction and matching traffic

NAT is not only about the public address. The inside/outside interface roles and the ACL or rule that matches traffic are just as important.

Technical deep dive

How to think about this question

NAT questions usually test address translation, overload/PAT behaviour, static mappings and whether the right traffic is being translated. Read the interface direction and address terms carefully.

KKey Concepts to Remember

  • Static NAT maps one inside address to one outside address.
  • PAT allows many inside hosts to share one public address using ports.
  • Inside local and inside global describe the private and translated addresses.
  • NAT ACLs identify traffic for translation, not always security filtering.

TExam Day Tips

  • Identify inside and outside interfaces first.
  • Check whether the scenario needs static NAT, dynamic NAT or PAT.
  • Do not confuse NAT matching ACLs with normal packet-filtering intent.

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?

Static NAT maps one inside address to one outside address.

What is the correct answer to this question?

The correct answer is: Session hijacking or session abuse, because the attacker can replay a valid token after logout without revocation. — Session hijacking or session abuse is the best answer. The key issue is that a copied JWT remained valid after logout and was accepted from another IP because the application did not revoke it server-side. That means possession of the token was enough to impersonate the user until expiration. In a stateless-token design, compensating controls like revocation lists, shorter lifetimes, and token binding become important. Why others are wrong: SQL injection would show database manipulation symptoms, not token replay across logins. Insecure deserialization requires unsafe object reconstruction and typically produces different exploitation clues. CSRF uses the victim's authenticated browser to send unauthorized requests; it does not explain a stolen token being reused from a different network location after logout.

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.