hardmulti selectObjective-mapped

Exhibit

Workstation baseline:
- Standard users are local admins
- Executables and scripts run from user-writable paths
- Unauthorized persistence reappears after reimaging
- Developers need to install approved tools, but not arbitrary software

A baseline review found that standard developer accounts are local administrators, unsigned tools can run from user profile folders, and reimaged systems still end up with unauthorized persistence. Which two changes best improve hardening while preserving developer work? Select two.

Question 1hardmulti select
Full question →

A baseline review found that standard developer accounts are local administrators, unsigned tools can run from user profile folders, and reimaged systems still end up with unauthorized persistence. Which two changes best improve hardening while preserving developer work? Select two.

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

Remove local administrator rights from standard user accounts.

Removing local admin rights blocks many common persistence and privilege escalation paths. It also reduces the damage a user mistake or malicious script can do on an otherwise managed workstation.

B

Best answer

Enforce application allowlisting for approved executables and scripts.

Application allowlisting prevents unauthorized binaries, scripts, and loaders from executing. That directly addresses the ability of unapproved tools to run from user-writable folders after reimaging or during normal use.

C

Distractor review

Turn off logging to preserve disk space.

Turning off logging would hide malicious activity and make investigation far harder. It may free space, but it directly weakens detection and response capabilities.

D

Distractor review

Allow unrestricted browser extension installs.

Unrestricted extensions widen the attack surface and create another path for malicious code. This makes the workstation less secure, not more hardened.

E

Distractor review

Merge all developer and production systems into one VLAN.

A flat network increases lateral movement opportunities and undermines containment. It is the opposite of a secure baseline and defense-in-depth design.

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: Remove local administrator rights from standard user accounts. — The best hardening controls here are to remove local administrator rights and to enforce application allowlisting. Admin removal reduces what a user or script can do if compromised. Allowlisting ensures only approved software and scripts can run, which directly cuts off the persistent unauthorized tooling described in the scenario. Together, they provide practical baseline protection without preventing legitimate development work. Why others are wrong: Logging should not be disabled because it is essential for detection and investigations. Allowing arbitrary browser extensions and flattening the VLAN both expand attack paths. The question asks for controls that preserve development while reducing abuse, so the correct answers focus on least privilege and execution control.

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.