Free AWS Security Specialty practice exam 2026: 20 questions without signup
Start the free AWS Security Specialty practice exam
20 questions from the real bank, every option explained. No signup, no card.
Start free AWS Security Specialty practice exam →- Questions on the exam
- about 65 — vendor indicates, no fixed count published
- Time allowed
- 170 minutes format →
890 practice exam questions for AWS Certified Security – Specialty SCS-C03, grouped by exam domain. Every question below shows all four options, which one is correct, and why each of the other three is not — the wrong answers are where most candidates lose marks.
Not sure where you stand? Take the free 5-min AWS Security Specialty readiness check →
AWS Security Specialty certification: requirements, cost and exam format → · AWS Security Specialty exam format → ·
Questions by domain
- 4: Identity and Access Management — 178 questions →
- 3: Infrastructure Security — 160 questions →
- 5: Data Protection — 160 questions →
- 1: Detection — 142 questions →
- 2: Incident Response — 125 questions →
- 6: Security Foundations and Governance — 125 questions →
Sample questions
Use customer-specific OIDC roles with constrained aud/sub: Which mechanism should be configured?
- Issue every customer a presigned PUT URL for the same fixed artifact object.An object-specific URL neither provides customer-isolated prefixes nor temporary role credentials for each job’s required object operations.
- Create one IAM user per customer and distribute its access key through each job environment.This can separate customers but creates long-term credentials outside AWS, violating the requirement.
- Use customer-specific OIDC roles with constrained aud/sub trust and prefix-scoped S3 permissions. ✓OIDC federation issues temporary credentials without stored AWS keys. Trust conditions restrict which tokens can assume the role, and customer-scoped S3 permissions prevent cross-customer access.
- Use an S3 bucket policy allowing the provider's public IP range.A source IP restriction does not authenticate individual jobs or issue temporary AWS credentials with customer-specific authorization.
All 178 4: Identity and Access Management questions →
Use OAC with always-sign requests: Which configuration should the security engineer implement?
- Use an S3 website endpoint with OAC, always-sign requests, and a bucket policy restricted to the distribution.An S3 website endpoint is configured as a custom origin and does not support CloudFront OAC.
- Use an OAI and allow its canonical user to read the bucket.OAI is a supported legacy mechanism, but it does not provide the required SSE-KMS support without additional workarounds.
- Use OAC with always-sign requests and a distribution-scoped bucket policy. ✓OAC supports regular S3 origins with SSE-KMS. Always-sign requests ensure HTTPS to S3, and the bucket policy can authorize only the CloudFront service principal for this distribution.
- Make the bucket public and require HTTPS for CloudFront viewers.Viewer HTTPS does not prevent direct public S3 access or authorize the origin connection.
All 160 3: Infrastructure Security questions →
Use CloudFront OAC with always-sign requests and set: Which configuration satisfies all requirements?
- Retain OAI, set the viewer policy to HTTPS only, and leave the S3 origin protocol behavior unchanged.OAI is not the recommended design and does not satisfy the stated SSE-KMS and modern origin-control requirements reliably.
- Use CloudFront OAC with always-sign requests and set the viewer protocol policy to HTTPS only. ✓OAC always-sign requests ensures HTTPS to S3, while HTTPS-only viewer policy requires encrypted client-to-CloudFront connections.
- Use CloudFront OAC with do-not-sign requests and set the viewer policy to redirect HTTP to HTTPS.The viewer redirect protects eventual viewer traffic, but do-not-sign requests does not ensure HTTPS from CloudFront to S3.
- Use OAC with always-sign requests and allow HTTP viewers because CloudFront encrypts the origin connection.Origin encryption does not protect viewer-to-CloudFront traffic, so allowing HTTP violates the viewer requirement.
All 160 5: Data Protection questions →
Enable GuardDuty Runtime Monitoring for ECS on Fargate: Which design best satisfies these requirements?
- Enable GuardDuty Runtime Monitoring for ECS on Fargate, Macie automated discovery, and Security Hub aggregation. ✓GuardDuty Runtime Monitoring covers ECS on Fargate using its managed security-agent model, Macie classifies eligible S3 data, and Security Hub centralizes supported findings. Macie automated discovery samples rather than exhaustively scanning every object.
- Enable GuardDuty Runtime Monitoring for EKS, Macie automated discovery, and Security Hub aggregation across accounts and Regions.The workload is ECS on Fargate, not EKS. GuardDuty does not support EKS clusters running on Fargate, and this option selects the wrong runtime coverage.
- Enable Inspector for supported workloads, Macie automated discovery, and Security Hub aggregation across accounts.Inspector can assess supported software and workloads, but it does not provide Fargate runtime process and network visibility.
- Enable CloudTrail S3 data events, Inspector workload assessment, Macie automated discovery, and Security Hub aggregation across the organization.CloudTrail S3 data events record API activity, and Inspector assesses supported workloads; neither supplies process and network visibility inside Fargate tasks.
All 142 1: Detection questions →
Run AWSSupport-ContainEC2Instance and restore the saved: Which design best meets these constraints?
- Attach an additional restrictive security group while leaving the instance running.Adding a security group is additive and cannot reliably remove permissions granted by existing security groups.
- Terminate the EC2 instance immediately and restore it from the latest Amazon EBS snapshot.Termination destroys volatile evidence and does not preserve the original running system for investigators.
- Remove the instance from its target group and leave its existing security groups unchanged.Target-group removal limits application routing but does not prevent other network communications from the instance.
- Run AWSSupport-ContainEC2Instance and restore the saved security groups after investigation. ✓The supported containment automation keeps the instance running and intact, replaces its security groups to block new network activity, and permits reversal after the investigation.
All 125 2: Incident Response questions →
Create a production OU: Which design is best?
- Create a production OU, attach a tested SCP denying public S3 changes, and move accounts into that OU gradually. ✓An SCP centrally limits member-account principals, can deny public-access changes, and supports staged testing through OU placement.
- Attach an IAM policy denying public S3 changes to administrators in every production account.Separate identity policies require account-by-account administration and can be changed locally, lacking the requested organization-level guardrail.
- Attach the SCP directly to the management account to prevent production administrators from changing S3 settings.SCPs do not affect principals in the management account and therefore cannot provide the stated production-account guardrail there.
- Attach an RCP denying public S3 changes to the production OU and move accounts into it gradually.RCPs constrain supported resources and external principals, whereas this requirement limits IAM principals operating within member accounts.
All 125 6: Security Foundations and Governance questions →
Align the API audience validation or client flow: Which troubleshooting action should the team take?
- Align the API audience validation or client flow with the intended enabled app client. ✓The token audience identifies a different app client from the one accepted by the API, so the validation configuration or client flow must be aligned.
- Replace the user pool with an identity pool so the application receives temporary AWS credentials.Identity pools provide AWS credentials but do not correct the API's existing JWT audience mismatch.
- Enable unauthenticated identity-pool access for the requests.Guest identity-pool access does not make the API accept a JWT issued for the wrong app client.
- Rotate the external OIDC provider certificate and leave the API audience configuration unchanged.The issuer has already passed the stated check; certificate rotation does not resolve an audience mismatch.
All 178 4: Identity and Access Management questions →
Combine an IP set rule: Which rule design best meets these requirements?
- Combine an IP set rule, AWS WAF intelligent threat mitigation, and a rate-based rule using an appropriate client fingerprint. ✓The IP set blocks known ranges, intelligent mitigation identifies automation, and client-fingerprint aggregation limits abuse beyond simple IP identity.
- Combine an IP set rule, AWS WAF intelligent threat mitigation, and a rate-based rule using forwarded IP aggregation.Forwarded-IP aggregation remains vulnerable to shared or manipulated addresses and does not meet the stable-client-characteristic requirement.
- Combine an IP set rule, AWS WAF managed rules, and a rate-based rule aggregated by a chosen forwarded-IP address.Managed rules address common threats, but forwarded-IP aggregation cannot distinguish legitimate shared NAT users from abusive clients reliably.
- Combine an IP set rule, a request-labeling rule based on headers, and a rate-based rule with a suitable aggregation key.Header labels can classify requests, but this design does not provide the requested stable client characteristic for automated-abuse detection.
All 160 3: Infrastructure Security questions →
AWS Security Specialty exam: the facts
How many questions are on the AWS Security Specialty exam?
Around 65. The vendor does not publish a fixed count for AWS Security Specialty, so this is the figure it indicates rather than a guaranteed number.
How long is the AWS Security Specialty exam?
170 minutes. Across 65 questions that is about 157 seconds per question.
What topics does the AWS Security Specialty exam cover?
6 domains: 4: Identity and Access Management, 3: Infrastructure Security, 5: Data Protection, 1: Detection, 2: Incident Response, 6: Security Foundations and Governance. Weights: 4: Identity and Access Management 20%, 3: Infrastructure Security 18%, 5: Data Protection 18%, 1: Detection 16%, 2: Incident Response 14%, 6: Security Foundations and Governance 14%.
How many AWS Security Specialty practice exam questions does Certsqill have?
890, spread across 6 exam domains. Every one shows all options, which is correct, and why each of the others is not.
AWS security best practices are what the questions test
Most questions on the AWS cloud security certification are a scenario plus four or five plausible controls, and the right one is usually the option that follows AWS cloud security best practices most closely — least privilege, temporary credentials, encryption, logging — without breaking the requirement in the question. That is why practice for this exam looks like a tour of AWS’s own best-practice pages.
The SCS-C03 exam guide weights that material across six domains: Detection 16%, Incident Response 14%, Infrastructure Security 18%, Identity and Access Management 20%, Data Protection 18%, and Security Foundations and Governance 14%. The sections below follow the services those domains keep returning to.
AWS IAM security best practices
IAM is the largest domain, and AWS’s list of AWS IAM security best practices maps closely onto how the questions are built. Among the practices AWS lists:
- Require human users to use federation with an identity provider and temporary credentials.
- Require workloads to use temporary credentials through IAM roles.
- Require multi-factor authentication (MFA), and protect the root user credentials.
- Apply least-privilege permissions, using IAM Access Analyzer to generate and validate policies.
- Use conditions in policies, permissions guardrails across multiple accounts, and permissions boundaries to delegate safely.
- Regularly review and remove unused users, roles, permissions, policies and credentials.
AWS security credentials and AWS STS
AWS security credentials are what AWS uses to authenticate and authorise your requests. AWS points out that root user, IAM user and access-key credentials are long-term and do not expire, and it strongly recommends temporary credentials from IAM roles and federation instead. Expect questions where the wrong answers all work, but rely on a long-lived access key.
An AWS Security Token Service example shows the alternative. A call to AssumeRole returns an access key ID, a secret access key and a session token, plus an expiry time. The session lasts one hour by default and can be set from 15 minutes up to the role’s maximum, which can be at most 12 hours; role chaining limits a session to one hour. Typical uses are access within your own account and cross-account access, where the role’s trust policy has to trust the calling account.
For an IAM user, the AWS My Security Credentials page in the console — introduced by AWS in 2019 — is the one place to change the console password, manage access keys and set up MFA.
AWS foundational security best practices and the archived whitepaper
The AWS Foundational Security Best Practices (FSBP) standard is a set of controls in AWS Security Hub that AWS says was developed by AWS and industry professionals. Its controls continuously evaluate accounts and workloads and flag resources that deviate from security best practices across many services. In exam terms it belongs to compliance evaluation and governance: when a question asks how to detect drift from best practice at scale, FSBP is a candidate answer.
The AWS Security Best Practices whitepaper, by contrast, is marked as archived by AWS, which points readers to its current security, identity and compliance architecture pages instead. Do not build your preparation on it.
AWS S3 security best practices
Amazon S3 shows up in data protection, detection and IAM questions alike. AWS’s preventive AWS S3 security best practices include disabling access control lists, making sure buckets use the correct policies and are not publicly accessible (with organization-level Block Public Access for multi-account setups), least-privilege access, IAM roles for applications, encryption at rest, enforcing encryption in transit, S3 Object Lock, S3 Versioning and VPC endpoints.
On the detection side AWS lists auditing all your buckets, S3 server access logging, AWS CloudTrail, AWS Config and S3 Storage Lens. A good practice question makes you choose between a preventive control and a detective one — and the scenario decides which is right.
AWS security group best practices, including outbound rules
Security groups are stateful: if a request is allowed out, the response is allowed back in regardless of inbound rules, and vice versa. They only take allow rules, not deny rules — a frequent trap, because blocking a specific address needs a network ACL, not a security group.
AWS’s security group best practices include authorising only specific IAM principals to create and modify security groups, keeping the number of groups to the minimum you need, never opening SSH (22) or RDP (3389) to 0.0.0.0/0, avoiding large port ranges, and adding network ACLs as a second layer.
For AWS security group outbound best practices, start from the default: a new security group has an outbound rule that allows all outbound traffic. You can remove it and allow only the specific outbound traffic you need; a group with no outbound rules allows no outbound traffic at all.
AWS EC2 security best practices
For EC2, AWS draws the shared-responsibility line explicitly. Your part includes controlling network access to instances through the VPC and security groups, managing the credentials used to connect, managing the guest operating system and software — including updates and security patches — and configuring the IAM roles attached to the instance and their permissions.
Those four areas are a useful checklist for AWS EC2 security best practices questions: if an answer fixes one of them while weakening another — say, solving access by embedding credentials instead of using an instance role — it is usually a distractor.
AWS Lambda security best practices
AWS frames Lambda security with the same shared-responsibility model: AWS protects the infrastructure that runs the service, and your responsibility covers the sensitivity of your data, your company’s requirements and applicable laws and regulations. In practice that puts the function’s execution role, its secrets and its logging in your hands.
If you remember one AWS Lambda security best practice, make it the IAM one: workloads should use temporary credentials through IAM roles with least-privilege permissions. Combined with the Secrets Manager practices below, that covers most AWS Lambda security best practices questions you will meet.
AWS Secrets Manager security best practices
AWS’s list of AWS Secrets Manager security best practices reads like a set of exam answers: store credentials and other sensitive information in Secrets Manager, find unprotected secrets in your code, choose an encryption key for each secret, use caching to retrieve secrets, rotate them, limit access (block broad access, be careful with IP address conditions, use VPC endpoint conditions), replicate secrets, monitor them and run infrastructure on private networks.
SCS-C03 added task statements on creating and managing encryption keys and certificates across one or several Regions and on the difference between imported and AWS-generated key material, so questions combining Secrets Manager with AWS KMS are worth practising.
AWS EMR security best practices
For Amazon EMR, AWS lists EC2 security groups around cluster instances, EMR block public access, which stops a cluster launching in a public subnet when its security configuration allows inbound public traffic, and three distinct IAM roles: the EMR service role, the EC2 instance profile for cluster instances and the runtime role for jobs. Encryption at rest and in transit, Kerberos, AWS Lake Formation and Apache Ranger complete the picture.
AWS EMR security best practices became more relevant with SCS-C03, which added a task on inter-resource encryption in transit and names inter-node encryption for Amazon EMR as an example.
AWS Cognito security best practices
AWS places the security of an application built on Amazon Cognito on the customer side of the shared-responsibility model and recommends planning user pools with security features in mind, especially public ones. The features AWS lists are where AWS Cognito security best practices come from: MFA by email, SMS or authenticator app, threat protection that monitors sign-ins for risk and can require MFA or block sign-in, association of an AWS WAF web ACL, deletion protection and control over user-existence error responses.
Note the boundary AWS draws: MFA and threat protection apply to local users, while third-party identity providers are responsible for federated users.
AWS transit gateway security best practices
AWS publishes transit gateway design best practices rather than a separate security list, and several of them shape security answers. Use a separate subnet for each transit gateway VPC attachment, keep the network ACLs on those transit gateway subnets open in both directions, and apply restrictive network ACLs to your workload subnets according to your traffic flow. AWS also advises limiting the number of transit gateway route tables unless your design requires more.
For AWS transit gateway security best practices questions, that means filtering belongs on the workload side or in an inspection design — not on the attachment subnets.
AWS application security testing and AWS Security Agent
For AWS application security testing, AWS now has its own service. AWS Security Agent penetration testing became generally available on 31 March 2026: AWS describes autonomous, 24/7 penetration testing in which specialised AI agents discover, validate and report vulnerabilities, with CVSS risk scores, reproduction steps and remediation suggestions, across AWS, other clouds and on-premises environments.
It is a new service, so do not expect the exam guide to centre on it; the incident-response and vulnerability-management tasks in SCS-C03 are where such findings would fit.
AWS AI security certification and the security engineer path
AWS’s certification overview lists no separate AWS AI security certification. What exists instead is AI security inside this exam: SCS-C03 added protections and guardrails for generative AI applications as a task statement.
If you are looking for an AWS security engineer certification, Security – Specialty is the one AWS describes as intended for individuals who have a responsibility to secure cloud solutions.
AWS Certified Security Specialty jobs and salary
AWS publishes no data on AWS Certified Security Specialty jobs, and no AWS security engineer salary figures. Any number you find for an AWS cloud security engineer salary comes from job boards or surveys, not from AWS, and this page quotes none.
What the certification documents is the scope of work: detection, incident response, infrastructure security, IAM, data protection and governance on AWS. Matching that scope to the job descriptions you are aiming for is a better test of its value than a headline salary.
SCS-C02 dumps and why they do not help
SCS-C02 dumps are out of date by definition: AWS’s exam guide lists SCS-C02 as in use only until 1 December 2025. Beyond that, the AWS Certification Program Agreement treats exam materials as AWS confidential information and prohibits possessing, accessing or using unauthorized materials, including exam content posted on third-party websites without AWS’s permission. AWS can cancel results and bar a candidate from the programme, without refunding fees.
A course or question bank written against the published exam guide avoids both problems. The questions on this site are expert-developed against AWS’s published exam guide, each option comes with an explanation, and your readiness score is shown per domain, backed by a 7-day money-back guarantee.
AWS Security Specialty practice: questions people ask
What is the AWS cloud security certification?
AWS Certified Security – Specialty, currently exam SCS-C03. Source: AWS exam guide, checked 9 October 2026.
Is the AWS security best practices white paper still current?
No. AWS marks the AWS Security Best Practices whitepaper as archived and points to its current security, identity and compliance pages. Source: AWS, checked 9 October 2026.
Do security groups allow outbound traffic by default?
A new security group has an outbound rule that allows all outbound traffic; you can replace it with specific rules. Security groups take allow rules only. Source: AWS VPC documentation, checked 9 October 2026.
How long do AWS STS credentials from AssumeRole last?
One hour by default, configurable from 15 minutes up to the role’s maximum session duration of at most 12 hours. Source: AWS STS API Reference, checked 9 October 2026.
Are SCS-C02 dumps useful for SCS-C03?
No. SCS-C02 was used until 1 December 2025, and the AWS Certification Program Agreement prohibits using unauthorized exam content. Source: AWS, checked 9 October 2026.
Would you pass AWS Security Specialty today?
Five minutes, and you get a score per domain — not one number, but which section to open tonight.
Test your AWS Security Specialty readiness — free