The answer is to shorten token and session lifetimes while using current IdP group claims for authorization instead of cached local roles. These two changes make access changes take effect faster because reducing the token session lifetime forces the app to re-verify the user’s identity and group membership more frequently, while relying on current IdP claims ensures that any role change—like moving out of finance—is reflected immediately rather than waiting for a locally cached role to expire. On the Security+ SY0-701 exam, this scenario tests your understanding of identity federation and session management, specifically how to balance security with usability; a common trap is assuming that simply clearing the cache or logging out once is enough, but the real issue is the stale token lifetime and cached roles. Remember the mnemonic “Shorten and Sync”—shorten the token lifetime and sync authorization with the IdP’s current claims to prevent stale permissions from persisting.
SY0-701 General Security Concepts Practice Question
This SY0-701 practice question tests your understanding of general security concepts. Examine the command output carefully: the correct answer depends on what the output actually shows, not on general recall alone. 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
Current behavior:
- Users sign in once through SSO
- App caches role assignments locally for the browser session
- Role changes are only noticed after logout
- No app-specific passwords are stored
A finance app uses the corporate IdP for authentication. A user who moved out of finance can still approve invoices until the browser session expires, and the app caches local roles. Which two changes best make access changes take effect faster without storing app passwords? Select two.
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.
Current behavior:
- Users sign in once through SSO
- App caches role assignments locally for the browser session
- Role changes are only noticed after logout
- No app-specific passwords are stored
A
Shorten token and session lifetimes, and require reauthentication for high-risk actions.
Shorter sessions reduce how long stale access remains usable after a role change. Step-up reauthentication for sensitive actions adds an extra check before invoice approval, which is appropriate for financial operations.
B
Increase password complexity but keep session duration unchanged.
Why wrong: Password complexity can help against guessing, but it does nothing to end a session that already has the wrong role. The stale authorization problem would still remain until the session expires.
C
Use current IdP group claims for authorization instead of cached local roles.
Using current group claims ties authorization to the latest identity data. That means role changes in the IdP are reflected faster, rather than waiting for a local cache to expire or a manual refresh to happen.
D
Disable SSO and email one-time passwords for every login.
Why wrong: Email-based one-time passwords are not a good substitute for centralized authorization, and disabling SSO increases user friction. Neither action directly solves stale role caching in the application.
E
Keep long-lived sessions to reduce help desk tickets.
Why wrong: Long-lived sessions make the stale-access window longer, which is the opposite of what the scenario needs. They improve convenience but weaken security when roles change quickly.
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Shorten token and session lifetimes, and require reauthentication for high-risk actions.
Option A is correct because shortening token and session lifetimes reduces the window during which stale permissions remain active, and requiring reauthentication for high-risk actions (like approving invoices) ensures that the user's current authorization status is verified before sensitive operations. This directly addresses the problem of cached roles persisting beyond the user's actual group membership changes.
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.
✓
Shorten token and session lifetimes, and require reauthentication for high-risk actions.
Why this is correct
Shorter sessions reduce how long stale access remains usable after a role change. Step-up reauthentication for sensitive actions adds an extra check before invoice approval, which is appropriate for financial operations.
Clue confirmation
The clue word "best" in the question point toward this answer.
Related concept
Read the scenario before looking for a memorised answer.
✗
Increase password complexity but keep session duration unchanged.
Why it's wrong here
Password complexity can help against guessing, but it does nothing to end a session that already has the wrong role. The stale authorization problem would still remain until the session expires.
✓
Use current IdP group claims for authorization instead of cached local roles.
Why this is correct
Using current group claims ties authorization to the latest identity data. That means role changes in the IdP are reflected faster, rather than waiting for a local cache to expire or a manual refresh to happen.
Clue confirmation
The clue word "best" in the question point toward this answer.
Related concept
Read the scenario before looking for a memorised answer.
✗
Disable SSO and email one-time passwords for every login.
Why it's wrong here
Email-based one-time passwords are not a good substitute for centralized authorization, and disabling SSO increases user friction. Neither action directly solves stale role caching in the application.
✗
Keep long-lived sessions to reduce help desk tickets.
Why it's wrong here
Long-lived sessions make the stale-access window longer, which is the opposite of what the scenario needs. They improve convenience but weaken security when roles change quickly.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates may think increasing password complexity or disabling SSO improves security, but the question specifically asks for changes that make access changes take effect faster without storing app passwords, so the focus must be on session/token lifetimes and authorization source, not authentication strength.
Trap categories for this question
Scenario analysis trap
Long-lived sessions make the stale-access window longer, which is the opposite of what the scenario needs. They improve convenience but weaken security when roles change quickly.
Detailed technical explanation
How to think about this question
Under the hood, OAuth2 access tokens and OpenID Connect ID tokens typically have configurable expiration times (e.g., 15 minutes for access tokens, 1 hour for ID tokens). When the app caches local roles, it effectively ignores the IdP's current group claims until the cached data expires or the session ends. By shortening token lifetimes and requiring reauthentication for high-risk actions, the app forces a fresh authorization check against the IdP, ensuring that group membership changes (e.g., removal from the finance group) are enforced promptly. In real-world scenarios, this is critical for compliance with the principle of least privilege and for meeting regulatory requirements like SOX or PCI-DSS.
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: Shorten token and session lifetimes, and require reauthentication for high-risk actions. — Option A is correct because shortening token and session lifetimes reduces the window during which stale permissions remain active, and requiring reauthentication for high-risk actions (like approving invoices) ensures that the user's current authorization status is verified before sensitive operations. This directly addresses the problem of cached roles persisting beyond the user's actual group membership changes.
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 →
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.