mediummultiple choiceObjective-mapped

A legacy finance application cannot yet support multifactor authentication. The security team still wants administrators to use separate privileged accounts, receive elevated access only when a ticket is approved, and have those privileges removed automatically after the maintenance window ends. Which solution best fits?

Question 1mediummultiple choice
Full question →

A legacy finance application cannot yet support multifactor authentication. The security team still wants administrators to use separate privileged accounts, receive elevated access only when a ticket is approved, and have those privileges removed automatically after the maintenance window ends. Which solution best fits?

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

Create one shared administrator account and rotate its password every week.

This provides shared access, but it weakens accountability and does not support just-in-time elevation. It also increases the risk of credential misuse.

B

Distractor review

Assign permanent administrator rights through role-based access control and rely on audit logs afterward.

Permanent rights do not reduce standing privilege. Logging helps with accountability, but it does not prevent unnecessary access in advance.

C

Best answer

Use privileged access management with separate admin accounts and time-bound elevation approvals.

Privileged access management is designed for this situation. Separate admin accounts preserve accountability, while time-bound elevation reduces standing privilege and limits exposure when the elevated rights are not needed. Approval workflows also support operational control and can be tied to maintenance tickets for traceability.

D

Distractor review

Move the application behind a federation service so all users can sign in with a single password.

Federation and SSO help with authentication convenience, but they do not directly solve privileged elevation or lifecycle control of admin access. The requirement is about temporary privileged access.

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: Use privileged access management with separate admin accounts and time-bound elevation approvals. — Privileged access management is the best fit because it focuses on controlling high-risk administrative access. The organization wants separate admin identities, approval-based elevation, and automatic revocation after the maintenance window. Those are classic PAM capabilities. This approach improves accountability and reduces the attack window by ensuring elevated privileges exist only when needed, rather than remaining permanently assigned. Why others are wrong: Option A makes administration easier but sacrifices accountability and still leaves powerful credentials widely usable. Option B leaves privileged rights active all the time, which is exactly what the team is trying to avoid. Option D improves user convenience through federation, but it does not address temporary administrative elevation or automatic deprovisioning.

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.