AWS SAA-C03 – 20 English Practice Questions

A · Weight 4/4: Cross-account role assumption with temporary credentials follows best practices.

C · Weight 3/4: Valid cross-account method but less granular than dedicated role.

B · Weight 2/4: Works but uses long-term keys, not best practice.

D · Weight 1/4: Highly insecure for sensitive data.

B · Weight 4/4: Serverless, pay-per-execution, minimal maintenance.

C · Weight 3/4: Serverless but more complex for simple periodic task.

A · Weight 2/4: Works but EC2 runs continuously, higher cost.

D · Weight 1/4: Error-prone, labor-intensive.

C · Weight 4/4: Best practice: reserve baseline, scale for spikes.

D · Weight 3/4: Guarantees capacity but wastes money during normal periods.

B · Weight 2/4: Cheap but risks availability during spikes.

A · Weight 1/4: Simple but not cost-optimized.

B · Weight 4/4: Versioning protects deletions, CRR protects regional outage.

A · Weight 3/4: Protects deletions but not regional failure.

C · Weight 2/4: Cost-effective archival but same region risk.

D · Weight 1/4: Error-prone, not real-time.

C · Weight 4/4: io2 designed for high IOPS mission-critical workloads.

A · Weight 3/4: gp3 solid performance but io2 better for 20k IOPS.

B · Weight 2/4: High IOPS but ephemeral, not persistent.

D · Weight 1/4: HDD unsuitable for high random IOPS.

A · Weight 4/4: Lowest cost for long-term archival.

C · Weight 3/4: Good archival but slightly more expensive.

B · Weight 2/4: Infrequent access but costlier than Glacier.

D · Weight 1/4: Very costly for 7-year archival.

D · Weight 4/4: Managed NAT Gateway is recommended solution.

B · Weight 3/4: Works but requires managing EC2 instance.

C · Weight 2/4: Only works for AWS services, not general internet.

A · Weight 1/4: Exposes instance to internet.

D · Weight 4/4: Dedicated connection with consistent bandwidth and low latency.

A · Weight 3/4: Secure but variable performance over internet.

C · Weight 2/4: More overhead, still over internet.

B · Weight 1/4: Least reliable for consistent performance.

B · Weight 4/4: ALB natively supports path-based routing at Layer 7.

D · Weight 3/4: Valid for API management but more complex.

C · Weight 2/4: Cannot differentiate by path.

A · Weight 1/4: Layer 4, cannot inspect URL path.

B · Weight 4/4: Automatic failover to standby in different AZ.

A · Weight 3/4: Manual promotion required, not automatic.

C · Weight 2/4: Complex, reinventing Multi-AZ.

D · Weight 1/4: Manual restore with significant downtime.

A · Weight 4/4: Purpose-built in-memory cache for DynamoDB.

B · Weight 3/4: Handles load but doesn't improve latency.

C · Weight 2/4: Works but adds complexity.

D · Weight 1/4: For multi-region, not hot key issue.

B · Weight 4/4: Customer-managed CMK provides key control and audit via CloudTrail.

A · Weight 3/4: Easy but no key control.

C · Weight 2/4: Full control but loses AWS KMS audit capabilities.

D · Weight 1/4: No encryption at rest.

C · Weight 4/4: CloudTrail logs all API calls and account activity.

A · Weight 3/4: Tracks configuration changes, not all API calls.

D · Weight 2/4: Monitors metrics, not API calls directly.

B · Weight 1/4: Threat detection, not comprehensive logging.

A · Weight 4/4: CloudWatch agent is recommended managed solution.

D · Weight 3/4: Works but requires maintaining custom script.

B · Weight 2/4: Doesn't include memory metrics.

C · Weight 1/4: No built-in memory event without metric.

D · Weight 4/4: Best practice: multi-AZ with load balancer.

C · Weight 3/4: Multi-AZ but DNS failover slower than ELB.

B · Weight 2/4: Auto-replace but still single AZ risk.

A · Weight 1/4: Vertical scaling, not HA.

C · Weight 4/4: Pre-deployed in second region with quick failover.

D · Weight 3/4: Faster than cold backup but may exceed RTO.

A · Weight 2/4: Protects AZ failure, not region.

B · Weight 1/4: Hours of downtime to restore.

A · Weight 4/4: Queue buffers surges, best practice for decoupling.

B · Weight 3/4: Helps capacity but doesn't decouple.

C · Weight 2/4: Pub/sub doesn't buffer for single consumer.

D · Weight 1/4: Not an architectural fix.

C · Weight 4/4: Scheduled scaling ideal for predictable patterns.

A · Weight 3/4: Reactive, may lag behind spike.

D · Weight 2/4: Error-prone, not automated.

B · Weight 1/4: Wasteful outside peak hours.

D · Weight 4/4: CDN caches at edge locations globally.

C · Weight 3/4: Optimizes path but doesn't cache.

B · Weight 2/4: Manual CDN-like solution, error-prone.

A · Weight 1/4: Doesn't address distance latency.

D · Weight 4/4: Managed service purpose-built for backup automation.

A · Weight 3/4: Valid but requires maintaining custom code.

C · Weight 2/4: Heavy for volume-only backups.

B · Weight 1/4: Not a backup mechanism.

AWS Certified Solutions Architect – Associate (SAA-C03)

Instructions

1) Cross-account S3 access without long-term credentials

2) Cost-effective periodic batch job

3) Optimize cost for baseline + spike traffic

4) Protect against deletion and regional outage

5) High IOPS database storage

6) Cost-effective 7-year archival

7) Private subnet internet access

8) Reliable on-premises to AWS connection

9) URL path-based routing

10) RDS high availability

11) DynamoDB hot key performance

12) S3 encryption with key control

13) Audit all API calls

14) Monitor EC2 memory usage

15) High availability architecture

16) Multi-region disaster recovery

17) Decouple order processing

18) Predictable daily traffic spike

19) Global static content delivery

20) Automated EBS backup