SY0-701 Security Architecture Practice Question
A Linux server is being prepared for production as a database host. The build team notices that a graphical desktop environment, an unused FTP service, and an open mail submission port are present on the image, even though none of them are required. The organization wants future builds to be consistent and easy to verify. What is the best approach?
⚠ Common exam trap
Many exam-takers think leaving the image unchanged aids troubleshooting (Option A), but in security architecture, consistency and minimal attack surface always take precedence over convenience, and a hardened standard is the only way to ensure repeatable, verifiable builds.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Create and enforce a hardened build standard that removes unnecessary services and ports, then validate future servers against it.
It establishes a hardened baseline configuration that removes unnecessary services (e.g., FTP on port 21) and closes unused ports (e.g., mail submission port 587), ensuring consistency and simplifying verification. This aligns with the principle of minimizing attack surface by disabling all non-essential components before production deployment. A hardened build standard also enables automated compliance checks (e.g., using CIS benchmarks or OpenSCAP) to validate future servers against the defined secure state.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Leave the image unchanged so troubleshooting remains easier for administrators.
Why it's wrong here
Prioritizing administrative convenience by preserving the stock image ignores that every preinstalled package, daemon, and listening socket expands the attack surface of a production database. The GUI, FTP service, and mail port are unnecessary for database operations and could harbor unpatched vulnerabilities. Troubleshooting can be performed through central logging, remote management over SSH, and monitoring tools, so the convenience gain does not justify the security risk. A hardened build standard would remove these components while still enabling effective operational diagnostics.
- ✗
Use the image only for development and skip security review for production.
Why it's wrong here
Using the base image only for development and bypassing a security review for production undermines the core principle of secure system design: development environments are not production-equivalent. Development images often include debug utilities, relaxed permissions, default credentials, and unneeded services that are unsuitable for a database host. Skipping security review means the host will lack baseline hardening, fail compliance audits, and expose the organization to avoidable risk. Production systems must be built from a validated, hardened standard and undergo security review before deployment.
- ✓
Create and enforce a hardened build standard that removes unnecessary services and ports, then validate future servers against it.
Why this is correct
A hardened build standard defines exactly which services, packages, and ports are allowed on the server. Removing the graphical environment, FTP service, and unnecessary mail port reduces the attack surface. Validating future systems against the standard also makes the build repeatable and helps identify drift quickly.
- ✗
Add another firewall rule set and keep every installed service in place.
Why it's wrong here
Adding another firewall rule set while retaining every installed service is a shallow defense-in-depth approach that only restricts external network access. The unnecessary services remain present on the host, so they can still be exploited via local privilege escalation, malformed local requests, or misconfigured firewall rules that inadvertently allow traffic. Additionally, the extra services consume memory, CPU, and disk space, and increase the system's patching burden. A hardened build standard that removes these services reduces the attack surface at the source, which is superior to merely adding more boundary controls.
Go deeper
Related to this question
Learn chapter
Firewall Types and Deployment
Key term
Compliance
Compliance is the process of ensuring that an organization follows laws, regulations, standards, and internal policies that apply to its operations and data handling.
Key term
FTP
FTP, or File Transfer Protocol, is a standard network protocol used to transfer files between a client and a server over a TCP/IP network.
About these practice questions
Courseiva writes every SY0-701 question from scratch — 1,013 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or dumps. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This SY0-701 practice question is part of Courseiva's free CompTIA certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the SY0-701 exam.