AWS Certified Security - Specialty Practice Test

AWS recommends a minimum of five years of IT security experience designing and implementing security solutions and at least two years of hands-on experience securing AWS workloads. While not a strict enforced prerequisite, holding an Associate-level AWS certification (such as Solutions Architect, Developer, or SysOps Administrator) or possessing equivalent knowledge is strongly advised to ensure foundational AWS competency before tackling this specialty-level content.

The Solutions Architect - Professional exam covers security as one component within a broad scope of architectural design, trade-offs, and best practices. In contrast, the Security - Specialty certification delves exclusively and exhaustively into security, requiring deeper, more granular knowledge of security-specific services (like AWS KMS, IAM, GuardDuty, Macie), data protection mechanisms, threat modeling, incident response procedures, and compliance frameworks. It is designed for security practitioners, whereas the Solutions Architect is for generalist architects.

The exam consists of 65 multiple-choice and multiple-response questions to be completed in 170 minutes. The current cost is USD 300. The exam is available in English, Japanese, Korean, and Simplified Chinese, and can be taken at a Pearson VUE testing center or as an online proctored exam. A scaled scoring model is used, with a passing score of 750 out of 1000.

Candidates must have expert-level knowledge of AWS Identity and Access Management (IAM), AWS Key Management Service (KMS), AWS CloudTrail, Amazon GuardDuty, AWS Security Hub, Amazon Inspector, AWS WAF & Shield, AWS Config, AWS Secrets Manager, and Amazon Macie. Deep understanding of how these services integrate to provide defense-in-depth is essential.

Success hinges on practical experience. Supplement official AWS training, whitepapers (especially the Security Pillar of the Well-Architected Framework), and exam guide with extensive hands-on labs. Practice analyzing scenarios by identifying the core security requirement (confidentiality, integrity, availability, compliance), evaluating trade-offs (cost vs. complexity), and selecting the most AWS-recommended, scalable, and secure solution. Focus on understanding the 'why' behind service selection.