Security Architecture: what Security+ tests and how to prepare
Where controls go and why. This domain moves from knowing that a control exists to placing it correctly in an architecture — on premises, in the cloud, or across both — and it leans heavily on networking knowledge the exam does not teach.
The list below follows the published exam objectives for SY0-701. Depth matters more than breadth here: the exam asks you to apply these ideas to a scenario, not to recite them.
Architecture models and their security implications: cloud, infrastructure as code, serverless, microservices, on-premises, centralised versus decentralised, virtualisation, IoT, ICS/SCADA and embedded systems.
Secure infrastructure design: device placement, security zones, attack surface, connectivity, failure modes, and whether a device is fail-open or fail-closed.
Data protection concepts — classification, data states, sovereignty, and methods including encryption, hashing, masking, tokenisation, obfuscation and segmentation.
Resilience and recovery: high availability, site considerations, testing, backups, power and continuity planning.
Common mistakes
Where candidates lose marks
Choosing a control that is correct in isolation but wrong for the stated placement. The question usually turns on where the device sits, not what it does.
Confusing tokenisation with masking, or hashing with encryption. Each has a different reversibility property, and that property is the answer.
Missing fail-open versus fail-closed. Availability and security pull in opposite directions here, and the scenario tells you which one the business prioritises.
For every architecture question, identify the asset being protected before evaluating options. The asset determines the control; working the other way round produces answers that are defensible in general and wrong for the scenario.
Try three questions. Understand every answer.
Original English practice examples, with answers and explanations available here. No account required. These are independent teaching examples, not official exam questions or exam dumps.
Question 1 of 3 · Threats, vulnerabilities, and mitigations
Answer and explanation
Best answer: Validate and apply the workaround, monitor it, and track the pending patch
A validated compensating control can reduce exposure while the permanent fix is pending. Retain the vulnerability record, residual risk, and a plan to apply and verify the patch.
Why the other choices fit less well
Waiting leaves exposure unchanged, and a hostname change does not block the flaw. A workaround reduces risk without necessarily removing the vulnerability, so closing it as permanently fixed overstates the evidence.
Best answer: Grant approved read-only access to that dataset with a reviewed expiry
Limit permissions to the approved task, resource and duration. Review the expiry and record the grant so access can be removed when the investigation ends.
Why the other choices fit less well
Permanent administrator rights exceed the task. Shared credentials weaken individual accountability. Disabling logs removes evidence without reducing the permissions required.
Best answer: Preserve both records and investigate or repeat the transfer before relying on the copy
The received bytes have not passed the expected integrity check. Preserve the acquisition record and investigate the discrepancy or acquire a verified copy.
Why the other choices fit less well
A filename does not establish byte-level integrity. Replacing the original hash hides the discrepancy. Do not describe the copy as verified until the mismatch is resolved.
Paid question-bank access is a one-time purchase, with no recurring subscription. Official exam registration, vouchers and provider labs are separate from CertSprint practice.
Find out if this domain is your weak one
20 free Security+ questions, no card required. Readiness is reported per domain, so you can see whether Security Architecture is where your revision should go.
