The answer is to perform authorization checks against current directory data on each privileged request. This is correct because JWT tokens carry static claims that remain valid until expiration, meaning any role changes made in the directory—such as demoting a user from admin to viewer—will not be reflected until the old token expires or the user reauthenticates. By checking current directory data, such as via LDAP or a policy decision point, on every privileged request, you decouple authentication from authorization, allowing dynamic role changes to take effect immediately without waiting for token expiration. On the Security+ SY0-701 exam, this tests your understanding of access control models and the common trap of assuming token validity equals current authorization. A helpful memory tip is "authN vs authZ"—the token proves who you are (authentication), but the directory proves what you can do (authorization) right now.
SY0-701 General Security Concepts Practice Question
This SY0-701 practice question tests your understanding of general security concepts. 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.
Exhibit
Application log excerpt:
10:20 HR updated jsmith from finance_approver to finance_viewer
10:35 invoice-approve allowed for jsmith by token claim role=finance_approver
11:05 jsmith still able to submit approval actions
JWT sample:
{
"sub": "jsmith",
"roles": ["finance_approver"],
"exp": "2026-05-01T18:00:00Z"
}
Identity team note: tokens remain valid for 8 hours after sign-in.
Based on the exhibit, what is the best fix so role changes take effect promptly without waiting for token expiration?
Clue words in this question
Noticing these words before you look at the options changes how you read each choice.
Clue: "best"
Why it matters: Signals that multiple options may be partially correct. Choose the option that most directly solves the exact problem described, not the one that sounds most complete.
Application log excerpt:
10:20 HR updated jsmith from finance_approver to finance_viewer
10:35 invoice-approve allowed for jsmith by token claim role=finance_approver
11:05 jsmith still able to submit approval actions
JWT sample:
{
"sub": "jsmith",
"roles": ["finance_approver"],
"exp": "2026-05-01T18:00:00Z"
}
Identity team note: tokens remain valid for 8 hours after sign-in.
A
Increase the token lifetime so users reauthenticate less often during the workday.
Why wrong: Longer-lived tokens would make stale access last even longer, which worsens the authorization delay shown in the exhibit rather than fixing it.
B
Perform authorization checks against current directory data on each privileged request.
This is the best fix because the problem is stale authorization, not failed authentication. The app is trusting a role claim that was correct at sign-in but became outdated after the HR change. Checking current directory data, or re-evaluating authorization on each sensitive action, ensures access follows the user's current status instead of an old token snapshot.
C
Store the JWT in a browser cookie so it refreshes automatically when roles change.
Why wrong: Moving the token into a cookie does not solve stale authorization. The application would still rely on the same outdated role information unless it revalidates the user's permissions against an authoritative source.
D
Disable MFA and rely only on the role claim inside the token.
Why wrong: Removing MFA weakens authentication and does nothing to correct the stale authorization decision. The issue is that the app trusts an old claim for too long, not that the user needs fewer login steps.
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Perform authorization checks against current directory data on each privileged request.
Option B is correct because performing authorization checks against current directory data (e.g., via LDAP or a policy decision point) on each privileged request ensures that role changes are enforced immediately, regardless of JWT token lifetime. This decouples authentication (token validity) from authorization (current role membership), allowing dynamic updates without waiting for token expiration or reauthentication.
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.
✗
Increase the token lifetime so users reauthenticate less often during the workday.
Why it's wrong here
Longer-lived tokens would make stale access last even longer, which worsens the authorization delay shown in the exhibit rather than fixing it.
✓
Perform authorization checks against current directory data on each privileged request.
Why this is correct
This is the best fix because the problem is stale authorization, not failed authentication. The app is trusting a role claim that was correct at sign-in but became outdated after the HR change. Checking current directory data, or re-evaluating authorization on each sensitive action, ensures access follows the user's current status instead of an old token snapshot.
Clue confirmation
The clue word "best" in the question point toward this answer.
Related concept
Read the scenario before looking for a memorised answer.
✗
Store the JWT in a browser cookie so it refreshes automatically when roles change.
Why it's wrong here
Moving the token into a cookie does not solve stale authorization. The application would still rely on the same outdated role information unless it revalidates the user's permissions against an authoritative source.
✗
Disable MFA and rely only on the role claim inside the token.
Why it's wrong here
Removing MFA weakens authentication and does nothing to correct the stale authorization decision. The issue is that the app trusts an old claim for too long, not that the user needs fewer login steps.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates assume storing a JWT in a cookie or increasing token lifetime will somehow make role changes take effect, when in fact neither alters the static nature of the token's claims without a reissue or runtime authorization check.
Trap categories for this question
Command / output trap
Longer-lived tokens would make stale access last even longer, which worsens the authorization delay shown in the exhibit rather than fixing it.
Detailed technical explanation
How to think about this question
In JWT-based systems, the token is a self-contained assertion; its claims (including roles) are signed and cannot be modified without reissuing. To enforce real-time authorization changes without waiting for token expiry, the relying party must query an authoritative source (e.g., Active Directory via LDAP, or a policy engine) on each request, often using a pattern like 'claims-based authentication with runtime authorization' or a token exchange mechanism (RFC 8693). This is critical in environments with dynamic role assignments, such as temporary privilege elevation or just-in-time access.
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.
General Security Concepts — This question tests General Security Concepts — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: Perform authorization checks against current directory data on each privileged request. — Option B is correct because performing authorization checks against current directory data (e.g., via LDAP or a policy decision point) on each privileged request ensures that role changes are enforced immediately, regardless of JWT token lifetime. This decouples authentication (token validity) from authorization (current role membership), allowing dynamic updates without waiting for token expiration or reauthentication.
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: "best". Signals that multiple options may be partially correct. Choose the option that most directly solves the exact problem described, not the one that sounds most complete.
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 →
These questions test the same concept from different angles. Work through them to make sure you can recognise it however the exam phrases it.
Variation 1. Based on the exhibit, what is the best fix so role changes are reflected promptly in the application?
Token and directory data:
09:10 Token issued for user jdoe
groups=[Finance_Approver, Expense_Reviewer]
auth_time=09:10
exp=17:10
09:15 HR updated directory: jdoe moved to Sales
11:00 The application still accepts the original token and allows expense approval
11:01 Identity provider logs show no token revocation event
hard
A.Increase the token lifetime so users reauthenticate less often.
✓ B.Shorten token and session lifetime and revoke active tokens when the directory role changes.
C.Move the application to a different subnet to isolate it from HR systems.
D.Disable group-based authorization and let any authenticated user approve expenses.
Why B: Option B is correct because the token's long lifetime (issued at 09:10, expires at 17:10) allows the application to continue accepting the original token even after the user's directory role changes at 09:15. Shortening the token lifetime forces more frequent reauthentication, and revoking active tokens when the directory role changes ensures that the application immediately reflects the updated authorization. This aligns with the principle of dynamic access control and token lifecycle management.
Last reviewed: Jun 11, 2026
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.
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.