Governance, compliance and multi-account structure
Organisations use many accounts because an account is the strongest isolation boundary AWS offers. Guardrails then make that structure safe to work in quickly, rather than turning governance into a queue for approval.
Exam tip. SCPs do not restrict the management account, even when attached at the root. Keep workloads out of it and hold its access tightly.
Identity and access management
IAM answers who is asking and what they may do. Access is denied by default, an explicit allow permits, and an explicit deny anywhere wins. Everything else is a variation on those three rules.
Exam tip. Any option that stores a long-lived access key on a resource is the one to reject. Roles for workloads, roles for cross-account, roles for federation.
Encryption and key management
Encryption at rest and encryption in transit are separate settings and both are usually required. Most AWS services now encrypt at rest by default, so the real question is almost always which key is used and who can audit its use.
Exam tip. Cross-account or cross-Region access to encrypted data always needs two grants: the resource AND the key. Forgetting the key is the usual cause of a puzzling denial.
The shared responsibility model
AWS is responsible for security OF the cloud; the customer is responsible for security IN the cloud. The line moves with the service, but two things never move: AWS always owns the physical layer, and the customer always owns their data, their code and who may reach it.
Exam tip. Almost every publicised cloud data exposure is a customer configuration decision, not a provider breach. If a question describes a misconfiguration, the responsibility is the customer's.
Protecting the network and the application
Defence in depth means several controls at different layers. No single one is a substitute for another, and the exam consistently rejects answers claiming one removes the need for the rest.
Exam tip. A WAF is an outer layer that buys time. It cannot know your application's business rules, so it never replaces input validation in the code.
Detection, logging and investigation
Four questions, four services: what is happening, what could be exploited, what is in the data, and how was it configured. Knowing which service answers which is most of this domain.
Exam tip. A findings queue nobody can act on is the same as no detection. Triage by severity and suppress accepted findings deliberately, as a recorded decision.