IT Cert Ready

AWS

AWS Certified Security – Specialty

Exam code: SCS-C03

Start practicing

About this certification

AWS Certified Security – Specialty is a AWS certification. Exam code SCS-C03. IT Cert Ready offers 1,200 practice questions with domain quizzes, full mock exams, and detailed explanations. Practice by official domain with 6 blueprint-aligned domains.

Official exam domain weights

Verified blueprint weights from the official exam outline.

  • Domain 1 · Detection · 16%
  • Domain 2 · Incident Response · 14%
  • Domain 3 · Infrastructure Security · 18%
  • Domain 4 · Identity and Access Management · 20%
  • Domain 5 · Data Protection · 18%
  • Domain 6 · Security Foundations and Governance · 14%

Sample AWS Certified Security – Specialty practice questions

Preview realistic multiple-choice items from the IT Cert Ready question bank. Expand each answer for the correct choice and explanation—the same format used in domain quizzes and mock exams.

  1. Sample question 1 · Security Foundations and Governance (14%)

    Velorix Systems, a mid-sized container platform company operating across North America and Europe, recently migrated to AWS. Their engineering teams provision AWS accounts ad hoc using root credentials shared via a wiki page. A governance audit reveals that 47 accounts exist with no consistent tagging, no baseline security controls, and no centralized visibility into spending or compliance posture. The CISO has mandated that all future account provisioning must enforce a security baseline automatically and that existing accounts must be brought under centralized governance. The security team must recommend a solution that enforces preventive controls at scale without requiring manual policy application to each account. Which combination of AWS services and features should Velorix Systems implement to enforce a consistent security baseline across all existing and future AWS accounts while enabling automated, governed account provisioning?

    • A. Enable AWS Config across all accounts with a delegated administrator account, and use AWS Systems Manager Automation runbooks to apply remediation to non-compliant resources in each account individually.
    • B. Deploy AWS Control Tower to establish a landing zone, enroll existing accounts into the landing zone using the Account Factory, and apply Service Control Policies through AWS Organizations to enforce preventive guardrails across all accounts.
    • C. Create a single consolidated billing account in AWS Organizations, attach resource-based policies to each account's IAM roles, and use AWS Trusted Advisor to identify and remediate compliance gaps.
    • D. Use AWS Security Hub with a designated aggregator account to collect findings from all member accounts, and configure automated response actions using Amazon EventBridge rules to enforce security controls.
    View answer & explanation

    Correct answer: B. Deploy AWS Control Tower to establish a landing zone, enroll existing accounts into the landing zone using the Account Factory, and apply Service Control Policies through AWS Organizations to enforce preventive guardrails across all accounts.

    [Domain 6 - Security Foundations and Governance, Subtopic 6 - Security Foundations and Governance - Area 2 - Control Tower] Core Concept: Develop a strategy to centrally deploy and manage AWS accounts. requires applying control tower in the context of the scenario, consistent with the official (ISC)² exam outline. Correct Answer (B): Deploy AWS Control Tower to establish a landing zone, enroll existing accounts into the landing zone using the Account Factory, and apply Service Control Policies through AWS Organizations to enforce preventive guardrails across all accounts. Why the other options are incorrect: Option A: AWS Config with Systems Manager Automation provides detective and reactive remediation but does not enforce preventive controls at the organizational level; it requires individual account configuration and does not address the account vending or landing zone requirements. Option C: Consolidated billing addresses cost visibility but not security governance; resource-based policies on IAM roles are not equivalent to SCPs and cannot enforce organization-wide preventive controls, and Trusted Advisor is advisory rather than enforcement-oriented. Option D: Security Hub aggregates and prioritizes findings for detective control but does not enforce preventive guardrails or provide a governed account provisioning mechanism; EventBridge automations are reactive and do not replace SCP-based prevention.

  2. Sample question 2 · Security Foundations and Governance (14%)

    Meridian Federal Systems, a large government contractor managing infrastructure for multiple civilian agency clients, operates 47 AWS accounts organized under a single AWS Organizations management account. Each client's workloads are isolated in dedicated organizational units (OUs). A recent internal audit found that several accounts in the 'Development' OU had enabled AWS services—specifically Amazon Rekognition and Amazon Comprehend—that are explicitly prohibited under the contractor's data handling agreements with two agencies. The audit committee is demanding that the security team present a governance mechanism that prevents prohibited service usage across specific OUs without affecting accounts in other OUs, and that the solution be documented as a policy artifact for stakeholder review. What is the most appropriate AWS governance mechanism Meridian Federal Systems should implement to prevent the use of prohibited AWS services in specific OUs while preserving service availability in other OUs, and that produces a policy artifact suitable for audit committee review?

    • A. Apply IAM permission boundaries to every IAM role in the Development OU accounts that explicitly deny actions for Amazon Rekognition and Amazon Comprehend, and document the boundary policies for the audit committee.
    • B. Enable AWS Config managed rules for restricted services in the Development OU accounts and configure automatic remediation to delete any resources created using prohibited services.
    • C. Attach a Service Control Policy (SCP) to the Development OU that contains explicit Deny statements for the prohibited services, and present the SCP JSON document as the policy artifact for audit committee review.
    • D. Create a resource-based policy on each prohibited service endpoint within the Development OU accounts that denies all principals, and archive the policies in an S3 bucket for audit committee access.
    View answer & explanation

    Correct answer: C. Attach a Service Control Policy (SCP) to the Development OU that contains explicit Deny statements for the prohibited services, and present the SCP JSON document as the policy artifact for audit committee review.

    [Domain 6 - Security Foundations and Governance, Subtopic 6 - Security Foundations and Governance - Area 6 - multi-account governance] Core Concept: Develop a strategy to centrally deploy and manage AWS accounts. requires applying multi-account governance in the context of the scenario, consistent with the official (ISC)² exam outline. Correct Answer (C): Attach a Service Control Policy (SCP) to the Development OU that contains explicit Deny statements for the prohibited services, and present the SCP JSON document as the policy artifact for audit committee review. Why the other options are incorrect: Option A: IAM permission boundaries constrain the maximum permissions of individual IAM entities but must be applied to each role or user separately; they do not provide a centralized, OU-wide control and can be bypassed by roles created without the boundary, making them insufficient as an organizational guardrail. Option B: AWS Config managed rules are detective controls that identify non-compliant resources after they are created; automatic remediation introduces a window of exposure and does not prevent prohibited service calls from occurring, which does not satisfy the audit committee's demand for a preventive control. Option D: Resource-based policies are not universally supported by all AWS services and cannot be applied at the OU level; this approach requires per-account, per-service configuration that is operationally fragile and does not constitute a centralized organizational governance mechanism aligned to Task 6.1.

  3. Sample question 3 · Security Foundations and Governance (14%)

    Harrowfield Medical Clinic, a 12-physician primary care practice in the northeastern United States, recently migrated to AWS. The clinic's IT administrator manually created three AWS accounts — one for production workloads, one for development, and one for billing — using the root email address of a shared mailbox. There are no guardrails preventing developers from launching resources in the production account, and the clinic has no centralized logging. A HIPAA audit finding notes that PHI workloads and non-PHI workloads share the same AWS account with no enforced boundary. The clinic's compliance officer wants to remediate these gaps before the next audit cycle. The administrator has been asked to propose a multi-account governance architecture that enforces workload isolation, prevents privilege escalation across accounts, and provides centralized visibility — all with minimal ongoing operational overhead. Which combination of AWS services and features BEST addresses the clinic's multi-account governance gaps while minimizing operational overhead?

    • A. Deploy AWS Control Tower to establish a landing zone with pre-built guardrails, enroll all three existing accounts into AWS Organizations, and apply Service Control Policies (SCPs) to restrict PHI workload accounts from launching resources outside approved Regions.
    • B. Create a new AWS Organizations structure manually, write custom IAM permission boundaries for each account, and configure AWS CloudTrail independently in each account to achieve centralized logging.
    • C. Enable AWS Security Hub in each account individually and configure cross-account IAM roles so the billing account can review findings, deferring SCP implementation until a future phase.
    • D. Migrate all workloads into a single AWS account, use resource tagging to separate PHI and non-PHI resources, and apply IAM policies at the resource level to enforce isolation.
    View answer & explanation

    Correct answer: A. Deploy AWS Control Tower to establish a landing zone with pre-built guardrails, enroll all three existing accounts into AWS Organizations, and apply Service Control Policies (SCPs) to restrict PHI workload accounts from launching resources outside approved Regions.

    [Domain 6 - Security Foundations and Governance, Subtopic 6 - Security Foundations and Governance - Area 6 - multi-account governance] Core Concept: Develop a strategy to centrally deploy and manage AWS accounts. requires applying multi-account governance in the context of the scenario, consistent with the official (ISC)² exam outline. Correct Answer (A): Deploy AWS Control Tower to establish a landing zone with pre-built guardrails, enroll all three existing accounts into AWS Organizations, and apply Service Control Policies (SCPs) to restrict PHI workload accounts from launching resources outside approved Regions. Why the other options are incorrect: Option B: Manually constructing an Organizations hierarchy and writing custom IAM permission boundaries is operationally intensive, error-prone, and does not provide the pre-built guardrails or automated account vending that Control Tower delivers, leaving governance gaps during the build phase. Option C: Enabling Security Hub without SCPs provides detective controls only and does not enforce the preventive workload isolation boundary required by the HIPAA finding; deferring SCP implementation leaves the privilege escalation risk unmitigated. Option D: Consolidating all workloads into a single account with tag-based separation violates the principle of account-level isolation recommended for PHI workloads and does not satisfy the HIPAA requirement for enforced boundaries, as IAM policies at the resource level can be misconfigured or bypassed by privileged users.

  4. Sample question 4 · Security Foundations and Governance (14%)

    Polaris HealthNet is a regional healthcare technology startup operating a single AWS account that hosts a cloud-native patient data platform subject to HIPAA requirements. The company has recently secured Series B funding and plans to expand its engineering organization from 15 to 80 developers over the next 18 months, adding dedicated teams for data engineering, security operations, and a new consumer mobile application. The VP of Engineering and the Head of Security are in disagreement: the VP wants to keep all teams in the existing single account to simplify billing and reduce operational overhead, while the Head of Security argues that a multi-account structure is essential for blast radius containment and regulatory compliance. The CTO has asked the Head of Security to present a concrete AWS-native governance strategy that addresses the VP's concerns about operational complexity while satisfying HIPAA isolation requirements. Which AWS-native strategy should the Head of Security recommend to satisfy HIPAA isolation requirements and limit blast radius while addressing the VP of Engineering's concern about operational complexity in managing multiple accounts?

    • A. Retain the single AWS account but implement strict VPC segmentation with separate VPCs for each team, use resource-based policies to isolate data access, and enable AWS Macie to monitor for PHI exposure across all teams.
    • B. Adopt AWS Control Tower with a landing zone that organizes accounts into Organizational Units by function (e.g., data engineering, security, mobile), use Account Factory to automate account provisioning for each new team, and consolidate billing through AWS Organizations with a management account, reducing manual overhead while enforcing per-OU guardrails.
    • C. Create separate AWS accounts manually for each team and use AWS Resource Access Manager to share common infrastructure resources such as VPCs and Transit Gateways across accounts to reduce duplication.
    • D. Deploy a centralized AWS Security Hub master account that aggregates findings from all team environments, and use AWS Config aggregators to enforce compliance rules across the single shared account through multi-region aggregation.
    View answer & explanation

    Correct answer: B. Adopt AWS Control Tower with a landing zone that organizes accounts into Organizational Units by function (e.g., data engineering, security, mobile), use Account Factory to automate account provisioning for each new team, and consolidate billing through AWS Organizations with a management account, reducing manual overhead while enforcing per-OU guardrails.

    [Domain 6 - Security Foundations and Governance, Subtopic 6 - Security Foundations and Governance - Area 2 - Control Tower] Core Concept: Develop a strategy to centrally deploy and manage AWS accounts. requires applying control tower in the context of the scenario, consistent with the official (ISC)² exam outline. Correct Answer (B): Adopt AWS Control Tower with a landing zone that organizes accounts into Organizational Units by function (e.g., data engineering, security, mobile), use Account Factory to automate account provisioning for each new team, and consolidate billing through AWS Organizations with a management account, reducing manual overhead while enforcing per-OU guardrails. Why the other options are incorrect: Option A: VPC segmentation within a single account does not provide true blast radius containment because a compromised IAM principal or misconfigured resource policy can potentially access resources across VPCs; HIPAA auditors and AWS Well-Architected guidance both recommend account-level isolation for sensitive workloads rather than relying solely on network controls. Option C: Manually creating accounts for each team reintroduces the operational complexity the VP is concerned about and does not establish a governed, repeatable provisioning process with enforced baseline security controls; AWS RAM sharing of infrastructure does not substitute for the governance layer that Control Tower and SCPs provide. Option D: Security Hub and Config aggregators are detective and compliance-monitoring tools that operate after resources are deployed; they do not address the fundamental architectural requirement for account-level isolation or automate governed account provisioning, and they cannot compensate for the blast radius risk inherent in a single-account model.

  5. Sample question 5 · Security Foundations and Governance (14%)

    Velorix Systems, a mid-sized financial services firm operating across North America and Europe, has recently migrated its core banking application to AWS. The platform team manages roughly 40 AWS accounts spread across development, staging, and production environments. A recent internal audit revealed that individual account owners are independently configuring IAM password policies, CloudTrail settings, and VPC configurations, resulting in significant drift from the corporate security baseline. The CISO wants a centralized mechanism to enforce non-negotiable guardrails—such as prohibiting the disabling of CloudTrail and restricting root account usage—across all accounts without requiring manual remediation per account. The security team must also produce a monthly compliance dashboard showing which accounts are adhering to the baseline and which are not. Which combination of AWS services and features should the Velorix Systems security team implement to enforce non-negotiable security guardrails across all 40 accounts AND generate the compliance metrics required for the monthly dashboard?

    • A. Deploy AWS Config rules in each individual account and use Amazon QuickSight to aggregate Config compliance data from each account's S3 export bucket into a central dashboard.
    • B. Enroll all accounts into AWS Organizations, apply Service Control Policies (SCPs) to deny prohibited actions such as disabling CloudTrail and using the root account, and use AWS Security Hub with a delegated administrator account to aggregate compliance findings and generate cross-account compliance reports.
    • C. Use AWS Control Tower to deploy a landing zone, apply managed guardrails, and rely solely on Control Tower's Account Factory to generate compliance metrics for the monthly dashboard without additional Security Hub integration.
    • D. Create a centralized IAM role in a master account with cross-account assume-role permissions, use AWS Lambda to periodically audit each account's configuration, and store results in Amazon DynamoDB for dashboard queries.
    View answer & explanation

    Correct answer: B. Enroll all accounts into AWS Organizations, apply Service Control Policies (SCPs) to deny prohibited actions such as disabling CloudTrail and using the root account, and use AWS Security Hub with a delegated administrator account to aggregate compliance findings and generate cross-account compliance reports.

    [Domain 6 - Security Foundations and Governance, Subtopic 6 - Security Foundations and Governance - Area 6 - multi-account governance] Core Concept: Develop a strategy to centrally deploy and manage AWS accounts. requires applying multi-account governance in the context of the scenario, consistent with the official (ISC)² exam outline. Correct Answer (B): Enroll all accounts into AWS Organizations, apply Service Control Policies (SCPs) to deny prohibited actions such as disabling CloudTrail and using the root account, and use AWS Security Hub with a delegated administrator account to aggregate compliance findings and generate cross-account compliance reports. Why the other options are incorrect: Option A: Deploying Config rules per account without SCPs addresses detective controls only and does not enforce preventive guardrails; account owners could still disable CloudTrail before Config detects the change, and the aggregation approach via S3 exports is operationally fragile compared to Security Hub's native cross-account aggregation. Option C: AWS Control Tower's Account Factory is an account provisioning mechanism, not a compliance reporting tool; while Control Tower's managed guardrails leverage SCPs and Config, relying solely on Control Tower without Security Hub integration does not produce the structured cross-account compliance metrics and dashboards required by the CISO. Option D: A Lambda-based audit approach is a custom detective control that introduces significant operational overhead, does not enforce preventive guardrails, and lacks the scalability and native compliance scoring that Security Hub provides; it also does not address the root cause of configuration drift, which requires preventive SCPs.

AWS Certified Security – Specialty exam prep FAQ

What is the passing score for the AWS Certified Security – Specialty exam?
Passing scores for AWS Certified Security – Specialty are set by AWS and can change between exam versions. Check the latest official exam outline on the AWS website for the current passing standard.
How many questions are on the AWS Certified Security – Specialty certification exam?
Official AWS Certified Security – Specialty exam length and item types are defined by AWS. Review the current exam blueprint for the latest question counts and timing.
How do domain quizzes help with AWS Certified Security – Specialty exam prep?
Domain quizzes on IT Cert Ready let you practice AWS Certified Security – Specialty one blueprint domain at a time across 6 official exam domains. You get immediate feedback, detailed explanations, and can revisit weak areas before taking a full timed mock exam.
How many AWS Certified Security – Specialty practice questions are on IT Cert Ready?
IT Cert Ready includes 1,200 published AWS Certified Security – Specialty practice questions with domain quizzes, full-length mock exams, and answer explanations mapped to the official outline.