hardmultiple choiceObjective-mapped

Exhibit

07:55:12  Account=FIN-ADMIN  Action=ApproveInvoice   Host=JUMP-02  IP=10.30.8.21
07:56:03  Account=FIN-ADMIN  Action=ChangeVendorBank Host=JUMP-02  IP=10.30.8.21
07:57:44  Account=FIN-ADMIN  Action=ExportReport     Host=JUMP-02  IP=10.30.8.21
Note: FIN-ADMIN is used by three finance managers during after-hours support.

Based on the exhibit, which change best improves accountability while still allowing emergency access?

A finance team uses the following shared account on a jump host:

07:55:12 Account=FIN-ADMIN Action=ApproveInvoice Host=JUMP-02 IP=10.30.8.21 07:56:03 Account=FIN-ADMIN Action=ChangeVendorBank Host=JUMP-02 IP=10.30.8.21 07:57:44 Account=FIN-ADMIN Action=ExportReport Host=JUMP-02 IP=10.30.8.21

Note: FIN-ADMIN is used by three finance managers during after-hours support.

Question 1hardmultiple choice
Full question →

Based on the exhibit, which change best improves accountability while still allowing emergency access?

A finance team uses the following shared account on a jump host:

07:55:12 Account=FIN-ADMIN Action=ApproveInvoice Host=JUMP-02 IP=10.30.8.21 07:56:03 Account=FIN-ADMIN Action=ChangeVendorBank Host=JUMP-02 IP=10.30.8.21 07:57:44 Account=FIN-ADMIN Action=ExportReport Host=JUMP-02 IP=10.30.8.21

Note: FIN-ADMIN is used by three finance managers during after-hours support.

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

Require the shared account password to be changed every 24 hours.

Frequent password changes may reduce reuse, but they do not show which person performed each action.

B

Best answer

Replace the shared account with named user accounts, role-based access, and a separate break-glass account for rare emergencies.

Named accounts preserve accountability, role-based access supports least privilege, and break-glass access preserves emergency availability.

C

Distractor review

Enable automatic account lockout after five failed logons.

Lockout helps against guessing attacks, but it does not solve shared-account traceability or accountability.

D

Distractor review

Restrict the jump host by MAC address and subnet only.

Network-based restrictions may reduce exposure, but they do not identify the individual using the account.

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: Replace the shared account with named user accounts, role-based access, and a separate break-glass account for rare emergencies. — The log entries show one shared account used for multiple high-risk finance actions, which removes individual accountability. The best fix is to use named user accounts with role-based access so each action can be traced to a person, while preserving emergency access through a separate break-glass account. That approach supports the AAA concept of accounting and also aligns with least privilege. It solves the real problem without sacrificing urgent support needs. Why others are wrong: Changing the password more often does not identify who approved or changed records. Account lockout helps against brute-force attempts, but the issue here is shared-use traceability, not failed logons. MAC or subnet restrictions may limit where access occurs, but they still do not tie actions to a specific user. The best answer must improve auditability and emergency access together, which only named accounts with a break-glass process accomplish.

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.