mediummultiple choiceObjective-mapped

A nightly patch script restarts services on 40 Linux servers. Security does not want an administrator to log in interactively, and the script should only have the permissions needed to install approved patches and restart those services. What is the best design?

Question 1mediummultiple choice
Full question →

A nightly patch script restarts services on 40 Linux servers. Security does not want an administrator to log in interactively, and the script should only have the permissions needed to install approved patches and restart those services. What is the best design?

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

Run the script with a dedicated automation account that has only the required sudo permissions

This satisfies least privilege while allowing unattended execution. A dedicated automation account can be limited to patching and service restart actions only.

B

Distractor review

Use the root account for every scheduled execution to avoid permission errors

Root access is broader than necessary and increases the impact of credential theft, script misuse, or configuration mistakes.

C

Distractor review

Hard-code the administrator password in the script so it never prompts

Embedding credentials in scripts creates a major secret-management risk and makes password rotation difficult and error-prone.

D

Distractor review

Ask each server owner to manually patch their system during the maintenance window

Manual patching is inconsistent, slow, and harder to audit than a controlled automated workflow with limited permissions.

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: Run the script with a dedicated automation account that has only the required sudo permissions — A dedicated automation account with only the needed sudo permissions is the best design because it supports unattended patching without granting unnecessary administrative power. This follows least privilege and reduces risk if the script or credentials are compromised. It also creates a clear audit trail for scheduled maintenance tasks. The goal is to make the workflow repeatable, controlled, and limited to exactly the actions required for the patch job. Why others are wrong: Using root for every job gives far more access than the script needs and increases the damage from a compromise. Hard-coding a password creates a secret-management problem and makes rotation difficult. Relying on manual patching is slower, less consistent, and harder to audit, which undermines the benefits of secure automation and scheduled maintenance.

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.