mediummultiple choiceObjective-mapped

A Linux operations team needs to run a nightly script that restarts one service and archives its logs on 60 servers. Security does not want an administrator to log in interactively, and the script should have only the permissions needed for that job. What is the best approach?

Question 1mediummultiple choice
Full question →

A Linux operations team needs to run a nightly script that restarts one service and archives its logs on 60 servers. Security does not want an administrator to log in interactively, and the script should have only the permissions needed for that job. What is the best approach?

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

Use the root account so the job never fails.

Root access is far broader than necessary and violates least privilege for a repeatable maintenance task.

B

Best answer

Create a dedicated service account with only the delegated rights needed, and run the script as a scheduled job.

A dedicated noninteractive account supports automation while keeping permissions tightly scoped to the task. The account can be granted only the ability to restart the specific service and write the required log archive location, rather than full administrator access. Scheduling the job also makes the activity repeatable and auditable. This approach supports least privilege, reduces human error, and avoids interactive logons on every server.

C

Distractor review

Store an administrator's SSH key inside the script.

Embedding privileged credentials in a script is unsafe, hard to audit, and creates a high-value secret exposure risk.

D

Distractor review

Have an operator log in and run the commands manually each night.

Manual execution is slower, less repeatable, harder to audit, and increases the chance of inconsistent results or missed runs.

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: Create a dedicated service account with only the delegated rights needed, and run the script as a scheduled job. — The best approach is a dedicated service account with only the rights needed for the specific maintenance job, executed through a scheduled automation mechanism. That design avoids interactive logins, makes the task repeatable, and limits the blast radius if credentials are ever exposed. Security+ expects least-privilege thinking here: the account should be able to restart that service and archive those logs, but nothing more. Automation should be controlled, not overprivileged. Why others are wrong: Using root grants excessive privilege. Storing an administrator SSH key in the script is insecure and difficult to manage. Manual logins are not scalable, are harder to audit, and introduce more operational error than a scheduled, delegated workflow.

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.