hardmultiple choiceObjective-mapped

Exhibit

Jump host session log:
```
10:02  sharedadmin login successful from 10.20.1.45
10:03  sudo /opt/deploy/apply_patch.sh
10:11  sudo systemctl restart appsvc
10:12  logout
```
Audit note:
- Three administrators used the same shared account this week.
- Logs do not identify which person executed which command.
- Management still wants a break-glass option for after-hours maintenance.

Based on the exhibit, what is the best change to improve accountability without removing emergency access?

Question 1hardmultiple choice
Full question →

Based on the exhibit, what is the best change to improve accountability without removing emergency access?

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

Keep the shared account and add more logging of the shared password.

Logging the password increases exposure and still does not identify the individual performing actions. It makes the accounting problem worse rather than better.

B

Best answer

Require named accounts with role-based elevation through a privileged access workflow.

This is the best answer because the issue is accountability. Shared accounts prevent the organization from knowing which person performed the actions in the log. Named accounts plus privileged elevation preserve break-glass access while ensuring each command is tied to an individual identity. That improves accounting and auditability without removing the operational ability to maintain the system.

C

Distractor review

Remove all command logging to protect administrator privacy.

Removing logs destroys accountability and creates a major audit and incident-response gap. Privacy should be protected through least privilege and controlled log access, not by eliminating evidence.

D

Distractor review

Use a single shared account with a longer password and monthly rotation.

A stronger shared password does not solve attribution. The core problem is that multiple people can act under one identity, so the logs still cannot show who did what.

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: Require named accounts with role-based elevation through a privileged access workflow. — The exhibit shows a classic accounting failure: multiple administrators act through one shared identity, so the logs cannot attribute commands to a specific person. The best improvement is named accounts with privileged elevation through a controlled workflow. That preserves emergency access, but each action is still tied to an individual identity, which supports auditing, nonrepudiation, and incident investigations. Accounting is about traceability, not simply stronger passwords. Why others are wrong: More logging of a shared password expands risk without solving attribution. Removing logs eliminates evidence and weakens security operations. A longer shared password still leaves the organization unable to prove which administrator performed the actions, so accountability remains broken.

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.