hardmulti selectObjective-mapped

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.

Question 1hardmulti select
Full question →

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.

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

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

Distractor review

Increase password complexity but keep session duration unchanged.

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

Best answer

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

Distractor review

Disable SSO and email one-time passwords for every login.

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

Distractor review

Keep long-lived sessions to reduce help desk tickets.

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 trap

Common exam trap: authentication is not authorization

Logging in proves the user can authenticate. It does not automatically mean the user is allowed to enter privileged or configuration mode. Watch for AAA authorization, privilege level and command authorization details.

Technical deep dive

How to think about this question

This kind of question is testing the difference between identity and permission. A user may successfully log in to a router because authentication is working, but still fail to enter configuration mode because authorization is missing, misconfigured or mapped to a lower privilege level.

KKey Concepts to Remember

  • Authentication checks who the user is.
  • Authorization controls what the user is allowed to do after login.
  • Privilege levels affect access to EXEC and configuration commands.
  • AAA, TACACS+ and RADIUS can separate login success from command access.

TExam Day Tips

  • Do not assume successful login means full administrative access.
  • Look for words such as cannot enter configuration mode, privilege level, authorization or command access.
  • Separate login problems from permission problems before choosing the answer.

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?

Authentication checks who the user is.

What is the correct answer to this question?

The correct answer is: Shorten token and session lifetimes, and require reauthentication for high-risk actions. — The right changes are to shorten session/token lifetime and to authorize users against current identity claims instead of cached local roles. Shorter sessions limit how long a revoked permission remains usable. Current IdP claims let the app react to role changes sooner, without storing separate application passwords or relying on outdated local authorization data. Why others are wrong: Password complexity and email one-time passwords do not solve stale authorization. Disabling SSO adds complexity and still does not guarantee fresh role checks. Long-lived sessions are convenient, but they prolong access after a transfer or termination, which is exactly the security weakness here.

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.