hardmultiple choiceObjective-mapped

A Linux operations team has a standing need to restart services and edit protected configuration files on production servers, but administrators should not keep root privileges all day. Every elevation must be approved through a ticket and logged centrally. Which solution best meets this requirement?

Question 1hardmultiple choice
Full question →

A Linux operations team has a standing need to restart services and edit protected configuration files on production servers, but administrators should not keep root privileges all day. Every elevation must be approved through a ticket and logged centrally. Which solution best meets this requirement?

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 root password and rotate it weekly

A shared root password is difficult to audit and gives too much standing privilege. Even if rotated, it still allows broad access without individual accountability or approval workflow.

B

Best answer

Use privileged access management with just-in-time elevation and session logging

PAM with just-in-time elevation is the best match because it grants administrative rights only when needed and only after approval. Central session logging provides accountability, and the regular user account remains the default for normal work. This reduces standing privilege, limits misuse, and gives auditors a clear record of who elevated, when, and why.

C

Distractor review

Assign each administrator the server local administrator role permanently

Permanent admin rights violate least privilege and do not satisfy the need for approval before use. This would also increase the impact of compromised credentials or mistakes by administrators.

D

Distractor review

Use single sign-on so administrators only authenticate once each morning

SSO improves usability but does not control privilege elevation or require approval for sensitive actions. The problem is not repeated authentication; it is excessive standing admin 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 just-in-time elevation and session logging — PAM with just-in-time elevation solves both the security and operations requirements. Administrators work from standard accounts, then request temporary elevated rights only when a ticket is approved. The elevated session can be recorded for audit purposes, which supports accountability and incident review. This design sharply reduces standing privilege while still allowing fast maintenance on production systems. Why others are wrong: Option A is easy to misuse and hard to trace to a specific person. Option C permanently expands the attack surface by giving every administrator continuous privileged access. Option D changes the login experience but does nothing to control or log privilege escalation.

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.