SAP-C02 practice questions and answers
All 75 questions from Full Practice Test 1 for AWS Certified Solutions Architect - Professional, with the correct answer and a full explanation for each — including why the other options are wrong. Free to read, no signup.
What this set covers
Questions are weighted to match the official SAP-C02 exam guide. The real exam is 75 (65 scored) questions in 180 minutes with a pass mark of 750 / 1000.
- Design Solutions for Organizational Complexity19 q · 26%
- Design for New Solutions22 q · 29%
- Continuous Improvement for Existing Solutions19 q · 25%
- Accelerate Workload Migration and Modernization15 q · 20%
A new event-driven order pipeline must guarantee that each order is processed exactly once in the order it was received per customer. Which service and configuration fits?
- AAn Amazon SQS FIFO queue with the customer ID as the message group ID✓
- BAn Amazon SQS standard queue with long polling
- CAn Amazon SNS standard topic fanning out to Lambda
- DAmazon EventBridge with a scheduled rule
Correct answer: A — An Amazon SQS FIFO queue with the customer ID as the message group ID
FIFO queues provide exactly-once processing and strict ordering within a message group, so grouping by customer preserves per-customer order while allowing parallelism across customers. Standard queues are at-least-once and unordered, standard SNS gives no ordering guarantee, and a scheduled rule is a timer rather than an ordered pipeline.
AWS — Amazon SQS FIFO queuesA company wants to modernise a batch job that runs on a Windows file share into an event-driven design after migration. Which target architecture fits with least custom code?
- AStore files in S3, trigger processing with S3 event notifications into SQS and a container or Lambda consumer✓
- BKeep the file share on EC2 and poll it every minute from a cron job
- CMove the share to EFS and keep the same polling script
- DEmail each file to a processing mailbox
Correct answer: A — Store files in S3, trigger processing with S3 event notifications into SQS and a container or Lambda consumer
S3 with event notifications turns file arrival into an event, and a queue plus a serverless or container consumer gives durable, scalable processing without polling code. Both polling options carry the legacy pattern forward, and email is not a file processing pipeline.
AWS — Amazon S3 event notificationsA design requires that a Lambda function reaches a private RDS instance and also calls a public third-party API. What is required?
- AAttach the function to private subnets and route outbound traffic through a NAT gateway✓
- BAttach the function to public subnets with an internet gateway route
- CGive the function an Elastic IP address
- DDisable VPC configuration and open the database to the internet
Correct answer: A — Attach the function to private subnets and route outbound traffic through a NAT gateway
A VPC-attached Lambda has no public IP, so internet access must come from a NAT gateway reachable from the private subnets it uses. Placing the function in public subnets does not give it a public address, Lambda functions cannot be assigned Elastic IPs, and exposing the database publicly is unacceptable.
AWS — Lambda VPC networkingAn existing DynamoDB table suffers throttling on a small number of partition keys during flash sales. Which change addresses the root cause?
- AIntroduce write sharding by appending a suffix to the hot partition key, and cache hot reads with DAX✓
- BIncrease the table's provisioned write capacity tenfold
- CAdd a local secondary index
- DEnable point-in-time recovery
Correct answer: A — Introduce write sharding by appending a suffix to the hot partition key, and cache hot reads with DAX
Throttling on a few keys is a hot partition problem, so spreading writes across suffixed keys and absorbing hot reads in DAX fixes the distribution rather than the total. More capacity does not help a single partition's limits, an LSI shares the same partition key, and point-in-time recovery is a backup feature.
AWS — Designing partition keys to distribute loadA new solution must run a long multi-step business process with retries, branching, human approval, and full execution history. Which service is designed for this?
- AAWS Step Functions with a standard workflow✓
- BA single Lambda function with a long timeout
- CAn EC2 instance running a cron job
- DAmazon SQS with a visibility timeout
Correct answer: A — AWS Step Functions with a standard workflow
Standard workflows in Step Functions run up to a year, model branching and retries declaratively, support callback patterns for human approval, and record every state transition. A single Lambda is bounded by its 15 minute limit, a cron job carries no orchestration semantics, and a queue alone provides no workflow state.
AWS — Standard vs Express workflowsA company migrating a mainframe workload wants to keep the existing COBOL business logic while moving off the mainframe. Which AWS offering supports this path?
- AAWS Mainframe Modernization with the replatform runtime✓
- BAWS Application Migration Service
- CAWS Database Migration Service
- DAmazon EC2 Dedicated Hosts
Correct answer: A — AWS Mainframe Modernization with the replatform runtime
AWS Mainframe Modernization provides managed runtimes that let recompiled COBOL applications run on AWS, which is the replatform route off the mainframe. Application Migration Service targets x86 servers, DMS moves databases rather than application logic, and Dedicated Hosts are ordinary EC2 capacity with licensing controls.
AWS — AWS Mainframe ModernizationWhich two migration strategies from the 7 Rs involve changing the application itself? (Select TWO.)
- ARefactor✓
- BReplatform✓
- CRehost
- DRetain
- ERetire
Correct answer: A, B — Refactor · Replatform
Refactoring rearchitects the application and replatforming makes targeted changes such as swapping to a managed database, so both touch the workload. Rehosting moves it unchanged, retaining leaves it where it is, and retiring decommissions it.
AWS — Migration strategiesAn existing workload uses a NAT gateway heavily to reach S3 and DynamoDB, and data processing charges are significant. Which change reduces cost immediately?
- AAdd gateway VPC endpoints for S3 and DynamoDB and route that traffic through them✓
- BAdd a second NAT gateway for redundancy
- CMove the workload to public subnets
- DEnable VPC Flow Logs
Correct answer: A — Add gateway VPC endpoints for S3 and DynamoDB and route that traffic through them
Gateway endpoints for S3 and DynamoDB carry no hourly or per-gigabyte charge, so moving that traffic off the NAT gateway cuts both data processing and transfer cost. A second NAT gateway adds cost, public subnets weaken the security posture, and Flow Logs add expense without changing traffic paths.
AWS — Gateway endpointsAn existing CloudFront distribution has a low cache hit ratio because the origin sets no cache headers and the cache key includes all query strings. Which two changes improve the hit ratio? (Select TWO.)
- ARestrict the cache key to only the query strings that affect the response✓
- BSet appropriate Cache-Control max-age headers at the origin or via a cache policy✓
- CForward all cookies and headers to the origin
- DDisable compression
- EReduce the distribution's price class
Correct answer: A, B — Restrict the cache key to only the query strings that affect the response · Set appropriate Cache-Control max-age headers at the origin or via a cache policy
A narrower cache key means more requests collapse onto the same cached object, and explicit cache lifetimes let CloudFront keep objects instead of revalidating constantly. Forwarding everything fragments the cache further, compression settings do not change hit ratio, and price class only limits which edge locations are used.
AWS — Optimizing caching and availabilityTwo teams need to consume a private API hosted in another account's VPC without exposing it to the internet or peering the VPCs. Which service fits?
- AAWS PrivateLink with an endpoint service fronted by a Network Load Balancer✓
- BVPC peering with a route table entry
- CAn internet-facing Application Load Balancer with IP allowlisting
- DA NAT gateway in the consumer VPC
Correct answer: A — AWS PrivateLink with an endpoint service fronted by a Network Load Balancer
PrivateLink exposes exactly one service through an interface endpoint in the consumer VPC, with no route between the networks and no overlapping CIDR concerns. Peering joins whole networks, an internet-facing balancer contradicts the private requirement, and NAT provides outbound internet access.
AWS — What is AWS PrivateLinkA new solution must fan a single event out to six independent consumers, each with its own filtering logic and retry behaviour. Which service fits best?
- AAmazon EventBridge with one rule per consumer and content-based event patterns✓
- BA single SQS queue polled by all six consumers
- CA Lambda function that calls each consumer synchronously in sequence
- DAn Application Load Balancer with six target groups
Correct answer: A — Amazon EventBridge with one rule per consumer and content-based event patterns
EventBridge routes one event to many targets, and each rule carries its own pattern filter, retry policy, and dead-letter queue, so consumers stay independent. A single queue makes consumers compete for the same messages, sequential invocation couples their failure modes, and a load balancer distributes rather than duplicates requests.
AWS — Amazon EventBridge rulesA new global application must serve dynamic API traffic with the lowest possible latency and instant regional failover using static anycast IP addresses. Which service should front it?
- AAWS Global Accelerator✓
- BAmazon CloudFront with a caching policy
- CRoute 53 weighted routing
- DAn internet-facing Application Load Balancer in one Region
Correct answer: A — AWS Global Accelerator
Global Accelerator provides static anycast IPs, moves traffic onto the AWS backbone at the nearest edge, and shifts traffic between Regions within seconds on health check failure. CloudFront is optimised for cacheable content, DNS-based routing is bounded by TTL and resolver caching, and a single-Region balancer offers no global failover.
AWS — What is AWS Global AcceleratorA design must encrypt data in transit between microservices inside a VPC with mutual authentication and no application code changes. Which option is most suitable?
- AA service mesh such as AWS App Mesh or ECS Service Connect providing mTLS at the proxy layer✓
- BSecurity group rules restricting ports
- CA NAT gateway between services
- DS3 default encryption
Correct answer: A — A service mesh such as AWS App Mesh or ECS Service Connect providing mTLS at the proxy layer
A sidecar proxy terminates and originates mutual TLS on behalf of the application, so encryption and identity are added without touching service code. Security groups control reachability without encrypting, NAT gateways handle outbound internet traffic, and S3 encryption applies to object storage.
AWS — Transport Layer Security in App MeshAn existing three-tier application is hitting connection limits on its RDS instance because hundreds of Lambda functions each open their own connection. What is the best remedy?
- APut Amazon RDS Proxy between Lambda and the database to pool and reuse connections✓
- BIncrease the max_connections parameter to its maximum
- CMove the database to a larger instance class only
- DAdd a read replica and send writes to it
Correct answer: A — Put Amazon RDS Proxy between Lambda and the database to pool and reuse connections
RDS Proxy multiplexes many short-lived Lambda connections onto a small pool of database connections, which is the designed fix for serverless connection storms. Raising max_connections consumes memory and postpones the problem, a larger instance treats a design issue with hardware, and replicas cannot accept writes.
AWS — Using Amazon RDS ProxyA new workload must run a batch of 10,000 independent compute jobs as cheaply as possible and can tolerate interruption. Which choice is best?
- AAWS Batch on Spot Instances with a managed compute environment✓
- BOn-Demand Instances kept running between batches
- CDedicated Hosts reserved for a year
- DA single large On-Demand instance processing jobs serially
Correct answer: A — AWS Batch on Spot Instances with a managed compute environment
Interruption-tolerant, parallelisable batch work is the textbook Spot use case, and AWS Batch handles queueing, retry, and capacity for it. Idle On-Demand capacity and year-long Dedicated Hosts are far more expensive, and serial processing on one instance wastes wall-clock time and money.
AWS — AWS Batch and SpotA new file-processing service must accept uploads of up to 5 TB from browsers worldwide directly into S3 without proxying through the application. Which combination is correct?
- APresigned URLs with multipart upload, optionally with S3 Transfer Acceleration✓
- BA single PUT through an Application Load Balancer to an EC2 fleet
- CAPI Gateway proxy integration streaming to S3
- DA public bucket with anonymous write permission
Correct answer: A — Presigned URLs with multipart upload, optionally with S3 Transfer Acceleration
Presigned URLs let the browser upload directly with scoped, time-limited permission, multipart upload is required for very large objects, and Transfer Acceleration improves long-distance throughput. Proxying through instances or API Gateway adds cost and hits payload limits, and anonymous write on a public bucket is a serious security defect.
AWS — Uploading objects with presigned URLsAn existing Aurora cluster experiences connection storms when the application tier scales out rapidly. Which change is the most targeted improvement?
- AIntroduce RDS Proxy and have the application connect through the proxy endpoint✓
- BAdd more Aurora Replicas and send writes to them
- CIncrease the backup retention period
- DDisable Performance Insights to reduce overhead
Correct answer: A — Introduce RDS Proxy and have the application connect through the proxy endpoint
RDS Proxy pools and reuses database connections so a burst of application instances does not translate into a burst of database connections. Replicas cannot take writes, backup retention is unrelated to connections, and disabling Performance Insights removes visibility without changing connection behaviour.
AWS — Amazon RDS ProxyA stateful legacy application on EC2 cannot be modified but must survive instance hardware failure with minimal downtime. Which improvement fits best?
- AEnable EC2 Auto Recovery or use an Auto Scaling group of one across zones with EBS-backed data on a separate volume✓
- BTake a snapshot every 12 hours and restore manually
- CMove the data to instance store for speed
- DDisable detailed monitoring to reduce noise
Correct answer: A — Enable EC2 Auto Recovery or use an Auto Scaling group of one across zones with EBS-backed data on a separate volume
Auto Recovery replaces impaired hardware while preserving the instance identity and EBS data, and a single-instance Auto Scaling group provides replacement when the zone allows it. Twelve-hourly snapshots imply a long RPO and manual work, instance store loses data on failure, and disabling monitoring removes the signal that triggers recovery.
AWS — Recover your instanceAn on-premises application needs low-latency access to a subset of S3 data while the migration proceeds. Which service provides a local cache with an S3 backend?
- AAWS Storage Gateway in File Gateway mode✓
- BAmazon EFS mounted over the internet
- CS3 Transfer Acceleration
- DAmazon FSx for Windows File Server in AWS only
Correct answer: A — AWS Storage Gateway in File Gateway mode
File Gateway presents an NFS or SMB share on premises, caches hot data locally, and stores objects durably in S3. EFS is not intended to be mounted over the public internet for this pattern, Transfer Acceleration speeds transfers without caching, and an AWS-only FSx file system does not provide the local cache.
AWS — Amazon S3 File GatewayA new API must handle unpredictable spikes from zero to 20,000 requests per second with no idle cost. Which architecture fits best?
- AAmazon API Gateway with Lambda integration and appropriate concurrency settings✓
- BA fixed fleet of EC2 instances sized for peak
- CA single large EC2 instance with vertical scaling
- DAn ECS service on EC2 with a fixed desired count
Correct answer: A — Amazon API Gateway with Lambda integration and appropriate concurrency settings
API Gateway and Lambda scale on demand and bill per request and per millisecond, so idle periods cost nothing. Fleets sized for peak pay continuously, a single instance cannot absorb that spike, and a fixed task count does not scale with load.
AWS — Lambda scalingAn existing API sees latency spikes traced to a downstream service that occasionally takes 30 seconds. The API's own timeout is 60 seconds. Which change improves user experience most?
- ASet an aggressive downstream timeout with retries and jittered backoff, and return a degraded response when the dependency is unavailable✓
- BRaise the API timeout to 120 seconds
- CRemove all retries
- DAdd more instances to the API tier
Correct answer: A — Set an aggressive downstream timeout with retries and jittered backoff, and return a degraded response when the dependency is unavailable
Failing fast with bounded retries and jitter, plus a graceful degradation path, keeps user-visible latency predictable when a dependency misbehaves. Longer timeouts make the bad experience worse, removing retries discards recoverable transient failures, and more instances do not shorten a slow downstream call.
AWS — Timeouts, retries, and backoff with jitterWhich two designs reduce the blast radius of a failure in a new multi-tenant SaaS platform? (Select TWO.)
- ACell-based architecture that partitions tenants across independent stacks✓
- BBulkheads and per-tenant throttling so one tenant cannot exhaust shared capacity✓
- CA single shared database with no per-tenant limits
- DRouting all tenants through one Lambda function with unreserved concurrency
- EDisabling retries across all services
Correct answer: A, B — Cell-based architecture that partitions tenants across independent stacks · Bulkheads and per-tenant throttling so one tenant cannot exhaust shared capacity
Cells isolate failures to a subset of tenants, and per-tenant limits stop a noisy neighbour consuming shared capacity. A single unpartitioned database and one unreserved function are shared fate designs, and disabling retries harms recoverability without containing blast radius.
AWS — Reducing scope of impact with cell-based architectureA new microservice needs single-digit millisecond reads at any scale with a flexible schema and no capacity planning. Which database should be chosen?
- AAmazon DynamoDB with on-demand capacity✓
- BAmazon RDS for MySQL with read replicas
- CAmazon Redshift
- DAmazon Neptune
Correct answer: A — Amazon DynamoDB with on-demand capacity
DynamoDB delivers consistent single-digit millisecond latency at any scale and on-demand mode removes capacity planning entirely. RDS requires instance sizing, Redshift is a data warehouse for analytics, and Neptune is a graph database for relationship queries.
AWS — Amazon DynamoDB on-demandA new solution requires a relational database that scales reads globally with sub-second replication lag to five Regions. Which option fits?
- AAmazon Aurora Global Database✓
- BAmazon RDS for MySQL cross-Region read replicas
- CAmazon DynamoDB global tables
- DAmazon ElastiCache global datastore
Correct answer: A — Amazon Aurora Global Database
Aurora Global Database replicates at the storage layer with typical cross-Region lag under a second and supports secondary Regions serving reads. RDS cross-Region replicas use logical replication with higher and less predictable lag, DynamoDB global tables are not relational, and ElastiCache is a cache rather than a system of record.
AWS — Aurora global databasesA new design must ensure that a downstream service being slow does not exhaust all threads in the caller. Which pattern addresses this?
- ACircuit breaker with timeouts and bounded concurrency for downstream calls✓
- BUnbounded retries with no timeout
- CSynchronous chaining of all services
- DIncreasing the instance size of the caller
Correct answer: A — Circuit breaker with timeouts and bounded concurrency for downstream calls
Timeouts, bounded concurrency, and a circuit breaker stop a slow dependency consuming the caller's resources and let it fail fast or degrade gracefully. Unbounded retries amplify the incident, synchronous chaining propagates the delay, and a bigger instance only postpones exhaustion.
AWS — Timeouts, retries, and backoffWhich design ensures that an S3 event triggers processing exactly once even if the consumer occasionally fails?
- AS3 event notification to SQS, with idempotent processing keyed on the object version and a dead-letter queue✓
- BS3 event notification directly to Lambda with no error handling
- CPolling the bucket every minute with a list operation
- DEnabling S3 Transfer Acceleration
Correct answer: A — S3 event notification to SQS, with idempotent processing keyed on the object version and a dead-letter queue
Delivery is at-least-once, so the durable answer is a queue for buffering and retry plus idempotent handling so a duplicate delivery is harmless, with a dead-letter queue for poison messages. Direct invocation with no error handling loses events, list polling is expensive and slow, and Transfer Acceleration is unrelated.
AWS — Amazon S3 event notificationsDuring a phased migration, on-premises and AWS components must resolve each other's DNS names. Which service pair enables bidirectional resolution?
- ARoute 53 Resolver inbound and outbound endpoints with forwarding rules✓
- BPublic hosted zones in Route 53 only
- CA NAT gateway with DNS enabled
- DCloudFront with an alternate domain name
Correct answer: A — Route 53 Resolver inbound and outbound endpoints with forwarding rules
An inbound endpoint lets on-premises resolvers query AWS private zones and an outbound endpoint with rules forwards AWS queries to on-premises DNS, giving resolution in both directions. Public zones expose names to the internet, NAT gateways do not perform DNS forwarding, and CloudFront is a content delivery service.
AWS — Route 53 Resolver endpointsA central security account must be able to read findings from every member account but must never be able to modify workloads. Which pattern satisfies this with the least standing privilege?
- AA cross-account IAM role in each member account with a read-only policy, trusted by the security account and assumed on demand✓
- BIAM users created in every member account with access keys shared to the security team
- CThe organisation management account root credentials shared with the security team
- DA resource-based policy on every resource granting the security account full access
Correct answer: A — A cross-account IAM role in each member account with a read-only policy, trusted by the security account and assumed on demand
Role assumption gives short-lived credentials scoped to a read-only policy and leaves nothing standing in the member accounts. Long-lived user keys spread secrets, root credentials are the highest-risk credential in an account, and blanket full access on every resource contradicts the read-only requirement.
AWS — Cross-account access with IAM rolesA migrated workload must keep using an on-premises Active Directory for authentication with low latency in AWS. Which option is recommended?
- AAWS Directory Service AD Connector or a two-way trust with AWS Managed Microsoft AD✓
- BRecreate all users manually in IAM
- CAmazon Cognito user pools with imported passwords
- DA local password file on each instance
Correct answer: A — AWS Directory Service AD Connector or a two-way trust with AWS Managed Microsoft AD
AD Connector proxies authentication to the existing directory and a trust with AWS Managed Microsoft AD gives a local directory in-Region while preserving on-premises identity, both of which keep one source of truth. Recreating users in IAM or Cognito duplicates the directory, and local password files are unmanageable and insecure.
AWS — AWS Directory Service optionsAn existing EC2 fleet runs at 12% average CPU with steady traffic and has run unchanged for two years. Which two actions reduce cost while preserving capacity headroom? (Select TWO.)
- ARight-size to smaller instance types based on Compute Optimizer recommendations✓
- BPurchase Compute Savings Plans covering the steady baseline✓
- CSwitch the fleet entirely to Spot Instances
- DDelete the Auto Scaling group
- EEnable detailed monitoring on every instance
Correct answer: A, B — Right-size to smaller instance types based on Compute Optimizer recommendations · Purchase Compute Savings Plans covering the steady baseline
Right-sizing removes waste and a Savings Plan discounts the steady baseline that remains, and the two compose well. Moving a steady production fleet entirely to Spot risks interruption, deleting the Auto Scaling group removes resilience, and detailed monitoring adds cost rather than reducing it.
AWS — AWS Compute OptimizerA team wants to prove that an existing system tolerates the loss of an Availability Zone without waiting for a real outage. Which practice applies?
- ARun controlled fault injection experiments with AWS Fault Injection Service against a defined steady state✓
- BReview the architecture diagram in a meeting
- CIncrease the number of instances and assume it works
- DDisable health checks during business hours
Correct answer: A — Run controlled fault injection experiments with AWS Fault Injection Service against a defined steady state
Fault injection experiments deliberately create the failure under controlled conditions and measure whether the steady state holds, which is the only option that produces evidence. Diagram reviews and assumptions are not tests, and disabling health checks degrades the system rather than testing it.
AWS — AWS Fault Injection ServiceApplications in 30 VPCs across two Regions must reach shared services in a central VPC, and on-premises networks must reach all of them. Which design is the most operationally sustainable?
- AA Transit Gateway per Region with inter-Region peering and a Direct Connect gateway association✓
- BA full mesh of VPC peering connections between all VPCs
- CA NAT gateway in each VPC routing to a shared public endpoint
- DA VPN tunnel from every VPC to every other VPC
Correct answer: A — A Transit Gateway per Region with inter-Region peering and a Direct Connect gateway association
Transit Gateways give a hub-and-spoke routing domain per Region, peer to each other across Regions, and attach to a Direct Connect gateway for on-premises reachability, so each VPC is configured once. Full mesh peering and full mesh VPN both scale quadratically and peering is not transitive, while NAT gateways send traffic over the internet rather than providing private routing.
AWS — Transit gateway peering and Direct Connect gatewayA legacy application writes to a single EBS volume and cannot keep up during month-end. CloudWatch shows VolumeQueueLength consistently high and IOPS at the provisioned limit. What should be changed?
- AMove to io2 Block Express or raise provisioned IOPS to match the workload✓
- BIncrease the instance memory only
- CEnable EBS encryption
- DChange the file system block size to the smallest available
Correct answer: A — Move to io2 Block Express or raise provisioned IOPS to match the workload
A sustained queue with IOPS pinned at the ceiling is a storage throughput limit, so raising provisioned IOPS or moving to a higher-performance volume type is the direct fix. More memory does not raise the IOPS cap, encryption is orthogonal, and shrinking the block size typically increases the number of operations required.
AWS — Provisioned IOPS SSD volumesA company must centralise VPC Flow Logs, CloudTrail, and Config data from all accounts into one immutable archive that the source accounts cannot delete. Which design fits?
- ADeliver logs to an S3 bucket in a dedicated log archive account with Object Lock and a restrictive bucket policy✓
- BKeep logs in each source account with lifecycle rules
- CEmail daily log summaries to the security team
- DStore logs in a DynamoDB table in the management account
Correct answer: A — Deliver logs to an S3 bucket in a dedicated log archive account with Object Lock and a restrictive bucket policy
A separate log archive account removes the source account's ability to tamper, and Object Lock makes the objects immutable for the retention period. Logs kept locally can be deleted by the account, email summaries are not an archive, and DynamoDB is a poor fit for bulk log retention.
AWS — Centralized loggingWhich two factors most strongly justify choosing a rehost strategy over refactoring for a specific application? (Select TWO.)
- AA hard data centre exit deadline that leaves no time for rearchitecting✓
- BThe application is a vendor package that cannot be modified✓
- CThe application is already serverless
- DThe team wants maximum long-term cloud-native benefit above all else
- EThe application will be retired in three months
Correct answer: A, B — A hard data centre exit deadline that leaves no time for rearchitecting · The application is a vendor package that cannot be modified
Rehosting suits deadline pressure and unmodifiable third-party software, where changing the application is either impossible or too slow. An already serverless application needs no rehost, maximising cloud-native benefit argues for refactoring, and something being retired shortly argues for retiring rather than migrating it.
AWS — Migration strategiesA migration wave must be validated before cutover, including application behaviour under production-like load. Which practice is most appropriate?
- ARun a test cutover into an isolated environment and replay representative traffic before the production cutover✓
- BCut over directly and monitor closely
- CValidate only that the instances boot
- DRely on the migration tool's success message
Correct answer: A — Run a test cutover into an isolated environment and replay representative traffic before the production cutover
A rehearsal in an isolated environment with realistic traffic surfaces integration and performance problems while rollback is still trivial. Cutting over blind, checking only boot status, or trusting a tool's exit code all defer discovery to production.
AWS — Testing before cutoverA new workload requires a POSIX-compliant shared file system with sub-millisecond latency for high-performance computing. Which service fits?
- AAmazon FSx for Lustre✓
- BAmazon S3 with the Mountpoint client
- CAmazon EFS Standard
- DAmazon EBS gp2
Correct answer: A — Amazon FSx for Lustre
FSx for Lustre is purpose-built for HPC with sub-millisecond latency and very high throughput, and it can link to S3 for data staging. Mountpoint exposes S3 with object semantics rather than full POSIX, EFS latency is higher, and EBS is block storage attached to individual instances.
AWS — What is Amazon FSx for LustreA regulator requires that production data never leaves a specific AWS Region. Which control enforces this across all accounts?
- AA service control policy denying actions outside the approved Region using the aws:RequestedRegion condition✓
- BA CloudWatch alarm on cross-Region data transfer
- CAn IAM policy on one administrator
- DS3 Cross-Region Replication with a filter
Correct answer: A — A service control policy denying actions outside the approved Region using the aws:RequestedRegion condition
The aws:RequestedRegion condition in an SCP blocks API calls to unapproved Regions for every principal in the affected accounts. An alarm detects rather than prevents, a single IAM policy governs one identity, and cross-Region replication actively moves data out, which is the opposite of the requirement.
AWS — Region restriction with SCPsAn existing workload uses long-lived IAM access keys in a CI system running on GitHub. Which improvement removes the static credential?
- AConfigure an IAM OIDC identity provider for the CI system and assume a role with web identity✓
- BRotate the access keys every 30 days manually
- CStore the keys in an encrypted repository file
- DRestrict the keys to a single IP address
Correct answer: A — Configure an IAM OIDC identity provider for the CI system and assume a role with web identity
An OIDC trust lets the CI job exchange its workload identity token for short-lived AWS credentials, so no secret ever exists to leak. Rotation, encrypted storage in the repo, and IP restrictions all still depend on a long-lived key existing somewhere.
AWS — Create an OpenID Connect identity providerA monolith on EC2 must be modernised incrementally without a big-bang rewrite. Which approach is recommended?
- AThe strangler fig pattern, routing selected paths to new services behind the existing entry point✓
- BFreeze the monolith and rewrite everything before releasing
- CLift and shift to containers and stop there permanently
- DSplit the database first and keep the application unchanged
Correct answer: A — The strangler fig pattern, routing selected paths to new services behind the existing entry point
The strangler fig pattern peels functionality off behind a routing layer so each increment ships and can be reverted independently. A full rewrite carries enormous risk, containerising alone changes packaging rather than architecture, and splitting the data layer first usually breaks transactional assumptions the application still relies on.
AWS — Strangler fig patternWorkloads in AWS must authenticate users from an existing corporate identity provider without creating IAM users. Which design is correct?
- AFederate the identity provider into AWS IAM Identity Center and assign permission sets to accounts✓
- BCreate one IAM user per employee in the management account
- CShare a single IAM user's access keys with the whole team
- DUse the root user with MFA for daily access
Correct answer: A — Federate the identity provider into AWS IAM Identity Center and assign permission sets to accounts
IAM Identity Center federates the corporate directory once and grants access to accounts through permission sets that map to roles, avoiding per-employee IAM users entirely. Per-user IAM identities duplicate the directory, shared keys destroy attribution, and the root user must never be used for routine work.
AWS — IAM Identity CenterWhich two metrics best indicate that an existing Auto Scaling policy is tuned correctly for a web tier? (Select TWO.)
- ARequest latency stays within the target during scale-out events✓
- BAverage target utilisation tracks close to the configured target without oscillation✓
- CThe number of security groups attached to each instance
- DThe count of CloudFormation stacks in the account
- EThe size of the AMI in gigabytes
Correct answer: A, B — Request latency stays within the target during scale-out events · Average target utilisation tracks close to the configured target without oscillation
A well-tuned policy holds latency during scaling and keeps utilisation near target without flapping between scale-out and scale-in. Security group counts, stack counts, and AMI size say nothing about scaling behaviour.
AWS — Target tracking scaling policiesAn operations team wants to detect regressions in an existing web application before customers report them, from outside the VPC. Which service fits?
- AAmazon CloudWatch Synthetics canaries✓
- BAWS Config rules
- CAmazon Inspector
- DAWS Trusted Advisor
Correct answer: A — Amazon CloudWatch Synthetics canaries
Synthetics canaries run scripted browser or API checks on a schedule from outside the application and alarm on failure or latency regression. Config evaluates resource configuration, Inspector scans for vulnerabilities, and Trusted Advisor provides account-level best-practice checks.
AWS — CloudWatch SyntheticsA file migration must run continuously from on premises to Amazon S3 with verification, scheduling, and bandwidth throttling. Which service is purpose-built?
- AAWS DataSync✓
- BThe AWS CLI in a cron job
- CAWS Transfer Family
- DAWS Glue
Correct answer: A — AWS DataSync
DataSync provides scheduled, verified, throttled transfers between on-premises storage and AWS storage services with a managed agent. A CLI cron job lacks verification and scheduling features, Transfer Family exposes SFTP and FTPS endpoints for external partners, and Glue is an ETL service.
AWS — What is AWS DataSyncA company must transfer 300 TB from an on-premises NAS to S3 within two weeks over a 500 Mbps link that is also used by production. Which option is most practical?
- AAWS Snowball Edge devices shipped to AWS✓
- BAWS DataSync over the existing internet link
- CS3 Transfer Acceleration with the AWS CLI
- DA Site-to-Site VPN with multiple tunnels
Correct answer: A — AWS Snowball Edge devices shipped to AWS
At 500 Mbps shared with production, 300 TB would take months, so physical transfer with Snowball Edge is the only option that meets the deadline. DataSync, Transfer Acceleration, and VPN all remain bound by the same constrained link.
AWS — AWS Snowball EdgeA new analytics platform must run ad hoc SQL over petabytes of Parquet files in S3 without managing servers, paying only for data scanned. Which service fits?
- AAmazon Athena with a Glue Data Catalog table✓
- BAmazon RDS for PostgreSQL with a foreign data wrapper
- CAn EMR cluster running continuously
- DAmazon DynamoDB with a global secondary index
Correct answer: A — Amazon Athena with a Glue Data Catalog table
Athena is serverless, queries S3 data in place through the Glue Data Catalog, and charges by bytes scanned, which partitioned Parquet minimises. RDS is not designed for petabyte-scale object storage scans, a continuously running EMR cluster contradicts the pay-per-query requirement, and DynamoDB is a key-value store rather than an ad hoc SQL engine.
AWS — What is Amazon AthenaAn existing workload's S3 costs are dominated by objects that are rarely read after 30 days but must remain instantly retrievable. Which change reduces cost with minimal risk?
- AA lifecycle rule transitioning objects to S3 Standard-Infrequent Access after 30 days✓
- BA lifecycle rule transitioning objects to S3 Glacier Deep Archive after 30 days
- CDeleting objects after 30 days
- DEnabling S3 Transfer Acceleration
Correct answer: A — A lifecycle rule transitioning objects to S3 Standard-Infrequent Access after 30 days
Standard-IA lowers storage price while keeping millisecond retrieval, which matches rarely read but instantly retrievable. Deep Archive retrieval takes hours, deletion loses the data, and Transfer Acceleration increases cost rather than reducing it.
AWS — Using S3 storage classesA new containerised workload must run without managing EC2 capacity, scale to zero between jobs, and start quickly. Which compute option fits?
- AAmazon ECS with AWS Fargate✓
- BAmazon ECS on a fixed EC2 Auto Scaling group
- CAmazon EKS with self-managed node groups
- DEC2 Dedicated Hosts
Correct answer: A — Amazon ECS with AWS Fargate
Fargate runs containers without any instances to size, patch, or scale, and tasks can drop to zero when idle. Both fixed EC2 capacity and self-managed node groups require capacity management, and Dedicated Hosts are for licensing and isolation requirements.
AWS — AWS Fargate for Amazon ECSWhich two are valid reasons to place workloads in separate AWS accounts rather than separate VPCs in one account? (Select TWO.)
- AA hard security and blast radius boundary that IAM alone does not provide✓
- BIndependent service quotas and clearer cost attribution✓
- CLower per-request API latency
- DAutomatic data replication between accounts
- EElimination of the need for IAM policies
Correct answer: A, B — A hard security and blast radius boundary that IAM alone does not provide · Independent service quotas and clearer cost attribution
Account separation gives the strongest isolation boundary AWS offers and gives each workload its own quotas and billing view. It does not change API latency, it does not replicate data, and IAM policies remain necessary inside every account.
AWS — Organizing your AWS environment using multiple accountsWhich two techniques improve read performance for a new read-heavy relational workload without changing the database engine? (Select TWO.)
- AAdd read replicas and direct read-only traffic to them✓
- BIntroduce a caching layer such as ElastiCache in front of hot queries✓
- CIncrease the write concurrency limit on the primary
- DDisable automated backups
- EStore the connection string in Secrets Manager
Correct answer: A, B — Add read replicas and direct read-only traffic to them · Introduce a caching layer such as ElastiCache in front of hot queries
Replicas add read capacity and a cache removes repeated identical queries from the database entirely, which are the two standard levers for read-heavy load. Raising write concurrency addresses a different bottleneck, disabling backups risks data loss, and secret storage is a security practice with no performance effect.
AWS — Caching strategies with ElastiCacheA design requires API request authorisation based on a corporate OIDC identity provider, with fine-grained scopes per route. Which approach fits an HTTP API in API Gateway?
- AA JWT authorizer validating the OIDC token and checking scopes per route✓
- BAn API key per client
- CIAM authorisation with SigV4 from browsers
- DA security group on the API
Correct answer: A — A JWT authorizer validating the OIDC token and checking scopes per route
HTTP APIs support native JWT authorizers that validate the issuer and audience and enforce required scopes on each route. API keys identify callers for usage plans rather than authorising users, browser-side SigV4 requires distributing AWS credentials, and security groups do not apply to a regional API Gateway endpoint.
AWS — JWT authorizers for HTTP APIsDevelopers in 40 accounts need to resolve private DNS names hosted in a central Route 53 private hosted zone. Which approach scales best?
- AAssociate the private hosted zone with the VPCs across accounts, or use Route 53 Profiles to share DNS configuration centrally✓
- BDuplicate the hosted zone in every account and synchronise records with a nightly script
- CAdd entries to the hosts file on every instance
- DMake the zone public so all accounts can resolve it
Correct answer: A — Associate the private hosted zone with the VPCs across accounts, or use Route 53 Profiles to share DNS configuration centrally
A private hosted zone can be associated with VPCs in other accounts, and Route 53 Profiles distribute DNS configuration across many VPCs and accounts from one place. Duplicated zones drift, hosts files are unmanageable at fleet scale, and publishing internal names publicly leaks information.
AWS — Associating a private hosted zone with VPCs in other accountsA finance team needs cost broken down by application across 50 accounts, where each application spans multiple accounts. Which approach delivers this?
- AActivate cost allocation tags for an application tag and analyse in Cost Explorer or the Cost and Usage Report✓
- BRead each account's billing page manually every month
- CCreate a separate organisation per application
- DUse CloudWatch billing alarms only
Correct answer: A — Activate cost allocation tags for an application tag and analyse in Cost Explorer or the Cost and Usage Report
Activated cost allocation tags let Cost Explorer and the Cost and Usage Report group spend by application regardless of which account the resources live in. Manual review does not scale, splitting organisations is a drastic structural change, and billing alarms only threshold total spend.
AWS — Using cost allocation tagsAn existing multi-account estate has inconsistent security group rules allowing unrestricted SSH. Which approach both detects and corrects this continuously?
- AAWS Config rules with automatic remediation, deployed organisation-wide through a conformance pack✓
- BA quarterly manual audit
- CAn email reminder to each account owner
- DA CloudWatch dashboard of security group counts
Correct answer: A — AWS Config rules with automatic remediation, deployed organisation-wide through a conformance pack
Config conformance packs deploy the rules everywhere and remediation actions close the finding automatically, giving continuous enforcement. Quarterly audits, reminders, and dashboards observe the problem without fixing it.
AWS — Conformance packsAfter migration, a company wants to run part of its workload on premises with a consistent AWS API surface for latency-sensitive components. Which option fits?
- AAWS Outposts✓
- BAWS Local Zones
- CAmazon CloudFront
- DAWS Wavelength
Correct answer: A — AWS Outposts
Outposts places AWS-managed racks in the customer's own facility so the same APIs and services run on premises. Local Zones and Wavelength are AWS-operated locations near metros and mobile networks rather than in the customer data centre, and CloudFront caches content at edge locations.
AWS — What is AWS OutpostsAn existing data pipeline reprocesses the entire dataset nightly, and runtimes have grown past the maintenance window. Which change is most likely to fix this sustainably?
- AMove to incremental processing with partitioned data and job bookmarks so only new or changed partitions are processed✓
- BDouble the cluster size every quarter
- CStart the job earlier in the evening
- DCompress the output files more aggressively
Correct answer: A — Move to incremental processing with partitioned data and job bookmarks so only new or changed partitions are processed
Processing only what changed decouples runtime from total dataset size, which is the only change here that scales as data grows. Bigger clusters and earlier start times buy time without addressing growth, and output compression does not reduce input scanned.
AWS — AWS Glue job bookmarksA new system must retain immutable financial records with cryptographic verification of the complete change history. Which service is purpose-built for this?
- AAmazon Quantum Ledger Database✓
- BAmazon RDS with audit triggers
- CAmazon DynamoDB with streams
- DAmazon Redshift
Correct answer: A — Amazon Quantum Ledger Database
QLDB maintains an append-only journal with a cryptographic hash chain so any change to history is detectable. Audit triggers and streams record changes but can be altered or bypassed by a privileged user, and Redshift is an analytics warehouse.
An application in Account A must write to a KMS-encrypted S3 bucket in Account B. Which combination is required?
- AA bucket policy in B allowing the role in A, an IAM policy in A allowing the S3 and KMS actions, and a KMS key policy in B allowing the role in A✓
- BOnly an IAM policy in Account A
- COnly a bucket policy in Account B
- DMaking the bucket public and encrypting client-side
Correct answer: A — A bucket policy in B allowing the role in A, an IAM policy in A allowing the S3 and KMS actions, and a KMS key policy in B allowing the role in A
Cross-account access requires an allow on both sides, and because the objects are encrypted with a customer managed key the key policy must also permit the calling role to generate and use data keys. Either policy alone is insufficient, and making the bucket public is an unacceptable workaround.
AWS — Cross-account access to KMS-encrypted S3 objectsAn existing .NET Framework application on Windows must be modernised to reduce Windows licensing cost. Which AWS tooling directly supports this?
- AAWS Porting Assistant for .NET to assess and port to cross-platform .NET running on Linux✓
- BAWS License Manager to buy more licences
- CAWS Backup to snapshot the servers
- DAmazon WorkSpaces to virtualise desktops
Correct answer: A — AWS Porting Assistant for .NET to assess and port to cross-platform .NET running on Linux
Porting Assistant analyses .NET Framework code for incompatible API usage and helps move it to cross-platform .NET so it can run on Linux without Windows licences. License Manager tracks entitlements rather than removing the need for them, Backup protects data, and WorkSpaces delivers virtual desktops.
Before migrating, a company needs an inventory of on-premises servers with utilisation data and dependency mapping. Which service provides this?
- AAWS Application Discovery Service✓
- BAWS Config
- CAmazon Inspector
- DAWS Compute Optimizer
Correct answer: A — AWS Application Discovery Service
Application Discovery Service collects server inventory, performance data, and network dependencies from the on-premises estate to inform migration planning. Config tracks AWS resources, Inspector scans for vulnerabilities, and Compute Optimizer recommends sizing for resources already in AWS.
AWS — Application Discovery ServiceA 40 TB Oracle database must move to Amazon Aurora PostgreSQL with less than an hour of downtime. Which combination fits?
- AAWS Schema Conversion Tool for schema and code, then DMS with full load plus change data capture and a short cutover✓
- BA single mysqldump export and import
- CSnowball for the data with no schema conversion
- DManual CSV export and import over a weekend
Correct answer: A — AWS Schema Conversion Tool for schema and code, then DMS with full load plus change data capture and a short cutover
Heterogeneous migration needs schema and stored code conversion first, then DMS ongoing replication so the target stays current until a brief cutover. A MySQL dump tool does not apply to Oracle, Snowball alone does not convert or replicate, and manual CSV export cannot keep pace with change during the copy.
AWS — AWS DMS and Schema Conversion ToolA production incident review finds that a deployment broke the service and rollback took 40 minutes. Which change most directly reduces recovery time for the next incident?
- AAdopt automated canary deployments with CloudWatch alarms wired to automatic rollback✓
- BAdd a manual approval gate before every deployment
- CDeploy less frequently in larger batches
- DIncrease the instance size of the fleet
Correct answer: A — Adopt automated canary deployments with CloudWatch alarms wired to automatic rollback
Canary deployments limit exposure and alarm-triggered automatic rollback removes the human latency that made recovery slow. Manual gates add delay without improving rollback, larger batches increase blast radius, and instance sizing does not affect deployment safety.
AWS — CodeDeploy automatic rollbacksAn organisation must ensure that a specific approved baseline stack exists in every account, including accounts created next year. Which configuration achieves this automatically?
- AA CloudFormation StackSet with service-managed permissions and automatic deployment enabled for the target organisational units✓
- BA StackSet with self-managed permissions deployed once to the current account list
- CA shared template stored in S3 with instructions in the onboarding wiki
- DA Config rule that reports missing stacks
Correct answer: A — A CloudFormation StackSet with service-managed permissions and automatic deployment enabled for the target organisational units
Service-managed StackSets with automatic deployment target organisational units and roll the stack out to accounts as they join. Self-managed StackSets need explicit account lists, wiki instructions rely on humans, and a Config rule reports the gap without closing it.
AWS — StackSets automatic deploymentA hybrid workload requires 10 Gbps of consistent private bandwidth to AWS and must remain available if one circuit fails. Which design meets this?
- ATwo Direct Connect connections at different locations, with a Site-to-Site VPN as backup✓
- BA single Direct Connect connection with a higher port speed
- CTwo VPN tunnels over the same internet circuit
- DAWS Global Accelerator in front of the workload
Correct answer: A — Two Direct Connect connections at different locations, with a Site-to-Site VPN as backup
Resilience requires diverse paths, so two connections terminating at different Direct Connect locations remove the single point of failure, with VPN as a lower-bandwidth fallback. One connection is a single failure domain regardless of speed, two tunnels on one circuit share that circuit's fate, and Global Accelerator optimises internet routing rather than providing private capacity.
AWS — Direct Connect resiliencyA new workload processes 50,000 messages per second in bursts and must retain a replayable ordered stream for 24 hours for multiple independent consumers. Which service fits best?
- AAmazon Kinesis Data Streams✓
- BAmazon SQS standard queue
- CAmazon SNS standard topic
- DAmazon MQ
Correct answer: A — Amazon Kinesis Data Streams
Kinesis Data Streams keeps an ordered, replayable record per shard that many consumer applications can read independently at their own position. SQS deletes messages once consumed and gives no replay, SNS pushes without retention, and Amazon MQ targets existing JMS or AMQP applications rather than high-throughput streaming.
AWS — What is Amazon Kinesis Data StreamsAn existing application's error budget is being consumed by a dependency with no timeout. Which observability change best supports root cause analysis across services?
- AEnable distributed tracing with AWS X-Ray and propagate trace IDs across service boundaries✓
- BIncrease log verbosity on one service only
- CAdd a CloudWatch alarm on total invocations
- DEnable S3 server access logging
Correct answer: A — Enable distributed tracing with AWS X-Ray and propagate trace IDs across service boundaries
Distributed tracing stitches a single request across services so the slow hop is visible rather than inferred. Verbose logs on one service miss the cross-service picture, an invocation count alarm says nothing about where time goes, and S3 access logs cover a different subsystem.
AWS — AWS X-Ray conceptsAn organisation must let a partner company assume a role in one of its accounts, but only from the partner's own AWS account and only when a shared secret value is supplied. Which trust policy element enforces the second condition?
- AA condition on sts:ExternalId in the role's trust policy✓
- BA condition on aws:SourceIp in the permissions policy
- CAn SCP attached to the partner's account
- DA KMS grant issued to the partner
Correct answer: A — A condition on sts:ExternalId in the role's trust policy
The external ID is designed for exactly this third-party scenario: the partner must pass the agreed value when assuming the role, which defeats the confused deputy problem. Source IP conditions restrict networks rather than identity, you cannot attach an SCP to an account outside your own organisation, and KMS grants delegate key usage rather than role assumption.
AWS — How to use an external IDWhich two are appropriate when designing a new workload for cost efficiency from day one? (Select TWO.)
- AChoose managed serverless services where load is spiky or unpredictable✓
- BRight-size and use Graviton-based instances where the workload supports the architecture✓
- CProvision for the highest imaginable peak and leave it running
- DBuy three-year Reserved Instances before measuring any usage
- EStore all data in S3 Standard permanently regardless of access pattern
Correct answer: A, B — Choose managed serverless services where load is spiky or unpredictable · Right-size and use Graviton-based instances where the workload supports the architecture
Serverless matches spend to spiky demand, and Graviton typically delivers better price performance for compatible workloads. Provisioning for imagined peaks wastes money, long commitments before measurement lock in the wrong baseline, and ignoring storage class lifecycle leaves cold data on the most expensive tier.
AWS — Cost optimization pillarA shared subnet model is required so a networking account owns the VPC while application accounts launch instances into it. Which service enables this?
- AAWS Resource Access Manager sharing subnets with the organisation✓
- BVPC peering between the networking account and each application account
- CAWS Transit Gateway attachment per account
- DAWS PrivateLink endpoint services
Correct answer: A — AWS Resource Access Manager sharing subnets with the organisation
RAM shares VPC subnets across accounts so participants launch resources into a VPC owned and governed centrally. Peering and Transit Gateway connect separate VPCs rather than sharing one, and PrivateLink exposes a specific service endpoint rather than subnet capacity.
AWS — Share your VPC subnetsA company acquires a business with its own AWS accounts and wants those accounts under its existing organisation without recreating workloads. What should be done?
- AInvite the existing accounts to join the organisation and move them into the appropriate organisational unit✓
- BCreate new accounts and migrate every workload before decommissioning the old accounts
- CMerge the two organisations with a single API call
- DConvert the acquired management account into a member account of both organisations
Correct answer: A — Invite the existing accounts to join the organisation and move them into the appropriate organisational unit
Existing accounts can be invited into an organisation and then placed in an OU, which brings governance without touching the workloads. Rebuilding everything is unnecessary effort, there is no organisation merge operation, and an account can belong to only one organisation at a time.
AWS — Inviting an account to your organizationA company must migrate 500 VMware virtual machines to EC2 with minimal downtime and no application changes. Which service is designed for this?
- AAWS Application Migration Service✓
- BAWS Database Migration Service
- CAWS DataSync
- DAWS Snowball Edge
Correct answer: A — AWS Application Migration Service
Application Migration Service performs continuous block-level replication of source servers and cuts over with minimal downtime, which is the lift-and-shift path for large VM estates. DMS migrates databases, DataSync moves files, and Snowball Edge is for offline bulk data transfer.
AWS — AWS Application Migration ServiceWhich two statements about service control policies are correct? (Select TWO.)
- AAn SCP never grants permissions; it only sets the maximum available permissions✓
- BSCPs do not apply to the organisation management account✓
- CAn SCP can grant a principal access that its IAM policy denies
- DSCPs replace the need for IAM policies in member accounts
- ESCPs apply to resource-based policies on external principals
Correct answer: A, B — An SCP never grants permissions; it only sets the maximum available permissions · SCPs do not apply to the organisation management account
SCPs are a permissions ceiling and the management account is exempt from them, which is why workloads should not run there. An SCP can never grant access, IAM policies are still required to allow anything, and SCPs govern principals inside the organisation rather than external ones.
AWS — SCP effects on permissionsA company must apply a mandatory tagging standard so untagged resources cannot be created in production accounts. Which two mechanisms help enforce this? (Select TWO.)
- AA service control policy that denies resource creation when a required tag key is absent✓
- BA tag policy in AWS Organizations to standardise tag keys and values✓
- CA CloudWatch dashboard listing untagged resources
- DAn SNS topic that emails a weekly tag report
- EAn IAM group named tagged-resources
Correct answer: A, B — A service control policy that denies resource creation when a required tag key is absent · A tag policy in AWS Organizations to standardise tag keys and values
SCPs with a condition on aws:RequestTag can block creation outright, and tag policies define and enforce the allowed keys and casing across accounts. Dashboards and email reports only observe, and an IAM group name has no bearing on resource tagging.
AWS — Tag policiesA company runs 60 AWS accounts under AWS Organizations. Security requires that no account, including its administrators, can disable AWS CloudTrail or delete the organisation trail. Which control enforces this?
- AA service control policy denying the CloudTrail stop and delete actions, attached to the root or the relevant organisational units✓
- BAn IAM permissions boundary on every administrator user
- CAn AWS Config rule that flags disabled trails
- DA bucket policy on the CloudTrail S3 bucket
Correct answer: A — A service control policy denying the CloudTrail stop and delete actions, attached to the root or the relevant organisational units
An SCP defines the ceiling of permissions for every principal in an account, so a deny there cannot be overridden by any local administrator. Permissions boundaries must be attached to each identity and can be removed by an administrator, a Config rule only detects afterwards, and a bucket policy protects the log destination rather than the trail configuration.
AWS — Service control policiesA company wants a single sign-on experience where engineers pick an account and role from a portal and receive temporary credentials for the CLI. Which capability provides this?
- AIAM Identity Center permission sets with the AWS access portal and CLI integration✓
- BLong-lived access keys stored in a password manager
- CEC2 instance profiles
- DAmazon Cognito user pools
Correct answer: A — IAM Identity Center permission sets with the AWS access portal and CLI integration
IAM Identity Center provides the access portal, maps permission sets to accounts, and issues short-lived credentials that the AWS CLI can consume directly. Stored static keys are the practice being replaced, instance profiles authorise EC2 workloads rather than humans, and Cognito is for application end users.
AWS — Configure the AWS CLI with IAM Identity CenterReady to try it under exam conditions?
Reading answers is not the same as recalling them with a clock running. Take the same 75 questions as a timed mock exam — 180 minutes, no feedback until you submit, then a score broken down by exam domain so you know what to study.
Start the timed SAP-C02 test →