What Server Hardening Steps Should an Administrator Take Before Deployment?

An administrator needs to perform server hardening before deployment. Which of the following steps should the administrator take? (Choose two.)

  1. Disable default accounts. Source Reference Answer
  2. Add the server to the asset inventory.
  3. Remove unnecessary services. Source Reference Answer
  4. Document default passwords.
  5. Send server logs to the SIEM.

Community Votes

AC
100%

100% of anonymous learners picked answer AC. Votes are pick records left by other test-takers — they are not the verified answer.

Community Insight

This question tests knowledge of proactive system hardening techniques versus reactive or administrative tasks, with the trap being options like logging or inventory management which support operations but do not reduce initial vulnerabilities.

Server hardening focuses on proactively reducing the attack surface by disabling default accounts and removing unnecessary services. The community unanimously agrees that options A and C are the correct technical hardening measures for pre-deployment configuration.

Candidates often incorrectly select E because it relates to security monitoring, but log forwarding is a post-deployment operational control, not a hardening step that reduces the initial attack surface.

Community Discussion (3 comments)

tripletripe805692 👍 1 Selected: AC
AC is correct. both actions make the server less vulnerable.
jafyyy 👍 2
AC - these options ensure the server is secure before deployment.
a4e15bd 👍 3 Selected: AC
A&C are correct

Comments & Corrections

No comments yet — spotted an error or have a note? Share it below.

Log in to comment, report an error, or add a note about this question.

Submitted for moderation before publishing. Keep it helpful and respectful.

Expert Analysis

Why the Answer Is Correct

Disabling default accounts eliminates known credential vectors that attackers frequently exploit during initial compromise attempts. Removing unnecessary services directly shrinks the attack surface by closing unused ports and eliminating potential software vulnerabilities. Both actions are foundational hardening practices recommended by industry benchmarks before a system enters production.

Why the Other Options Are Wrong

Adding the server to the asset inventory is a crucial governance task but does not technically harden the operating system. Documenting default passwords is a dangerous practice; secure configurations require changing or disabling them immediately rather than recording them. Sending server logs to the SIEM supports detection and response but occurs after deployment and does not reduce pre-existing vulnerabilities.

Community Comment Notes

As highlighted in top-voted comments [1][2], both choices directly minimize system exposure prior to go-live. Multiple users note that hardening specifically targets vulnerability reduction rather than administrative tracking or monitoring setup. The unanimous vote distribution reflects strong alignment with official CompTIA objectives for secure configuration.

Official Reference

Exam Strategy

When evaluating hardening questions, focus exclusively on actions that reduce the attack surface or eliminate known vulnerabilities before the system goes live. Filter out monitoring, auditing, and inventory options, as these support operations but do not constitute technical hardening controls.

Related Analysis

Practice All SY0-701 Questions

Access 100 questions with complete answers and detailed explanations.

View Full SY0-701 Practice Test →

← Back to SY0-701 Study Guide