SAP-C02 · LESSON 3

Continuous Improvement for Existing Solutions25% · 5 topics

Learn strategies for continuously improving operational excellence, security, performance, reliability and cost of existing solutions.

3.1Develop a strategy to improve operational excellence

3.1 Determine a strategy to improve overall operational excellence.

Concept

The core of operational improvement is automation and observability. Automate routine tasks (restarts, patching, AMI creation) with Systems Manager Automation runbooks, and visualize state with CloudWatch (metrics, logs, alarms, Synthetics) and X-Ray (distributed tracing). Detect incidents with EventBridge and standardize response with Incident Manager or similar.

How it works / steps

  1. Identify manual operating procedures and automate them as runbooks
  2. Monitor key metrics with CloudWatch dashboards and alarms
  3. Identify slow services and dependencies with X-Ray
  4. Trigger automated responses from events with EventBridge rules
  5. Prevent recurrence through post-incident reviews

Workplace example

When disk utilization exceeds 90%, EventBridge triggers Systems Manager Automation to delete old logs and posts the result to Slack.

Common confusions and exam tips

Mini quiz

Q1. Which statement about AWS X-Ray is incorrect?

  1. Tracing can be enabled with integrations such as Lambda and API Gateway
  2. Sampling rules adjust the proportion of requests recorded
  3. A service map shows how requests flow across multiple services and the latency of each segment
  4. It automatically records the contents of all traffic without code changes or installing an SDK or agent
Show answer and explanation

Answer: D It automatically records the contents of all traffic without code changes or installing an SDK or agent

Using X-Ray requires SDK instrumentation, installing ADOT or the X-Ray daemon, or enabling tracing on the service side. It records trace information, not the full contents of all traffic.

Q2. An existing system with steadily increasing usage may hit service quota limits by next year. What is the most appropriate measure?

  1. Contact AWS Support to discuss after errors occur from hitting the limit
  2. Freeze the number of users at the current level and do not let new departments use the system
  3. Monitor Service Quotas utilization with CloudWatch and request increases before approaching limits
  4. Quotas increase automatically with usage, so no monitoring or preparation is needed
Show answer and explanation

Answer: C Monitor Service Quotas utilization with CloudWatch and request increases before approaching limits

Watch usage trends and raise quotas before reaching them. Some Service Quotas utilization metrics can have alarms set.

Reference links

3.2Determine a strategy to improve security

3.2 Determine a strategy to improve security.

Concept

Improve security of existing environments with Security Hub (standards checks and finding aggregation), IAM Access Analyzer (detecting external and unused access, generating policies), Config rules with automatic remediation, and Inspector vulnerability scanning. Rotating secrets and eliminating long-term access keys are also improvement targets.

How it works / steps

  1. Check scores against Security Hub standards (such as AWS Foundational Security Best Practices)
  2. Find externally exposed resources and unused permissions with Access Analyzer
  3. Automatically remediate resources that violate Config rules
  4. Replace long-term access keys with IAM roles or Identity Center
  5. Prioritize fixing critical vulnerabilities from Inspector findings

Workplace example

When Config detects “unencrypted EBS,” automatic remediation encrypts it via snapshots, and the Security Hub score is reviewed at a monthly meeting.

Common confusions and exam tips

Mini quiz

Q1. Production settings were changed manually in the console, diverged from the staging environment and caused an outage. What is the most appropriate improvement?

  1. Record config changes with AWS Config and notify staff on change
  2. Record change actions in CloudTrail to identify who made them
  3. Codify the configuration in CloudFormation, change via templates, and find manual changes with drift detection
  4. Require approval of change requests before console changes in production
Show answer and explanation

Answer: C Codify the configuration in CloudFormation, change via templates, and find manual changes with drift detection

Manage configuration as code and make changes through reviewed templates. CloudFormation drift detection finds differences between the template and the actual configuration. [Other options] Config or CloudTrail records find changes but don't keep environments matching. Approval alone still leaves manual-change mismatches.

Q2. Security Hub found that S3 Block Public Access is not configured on buckets in many accounts. No bucket needs to be public. What is the most appropriate next step?

  1. Enable account-level Block Public Access in all accounts and prevent changes with an SCP
  2. Send a ticket to the bucket owner for each Security Hub finding
  3. Deny requests where aws:SecureTransport is false in bucket policies
  4. Set Block Public Access per bucket and monitor with Config rules
Show answer and explanation

Answer: A Enable account-level Block Public Access in all accounts and prevent changes with an SCP

Account-level blocking prevents all buckets in the account from being made public. Prohibiting changes with an SCP also prevents it from being reverted. [Other options] Per-bucket settings miss new buckets. Tickets are slow and not enforced. SecureTransport enforces encrypted transport, not blocking public access.

Reference links

3.3Determine a strategy to improve performance

3.3 Determine a strategy to improve performance.

Concept

Improving performance of existing systems means identifying bottlenecks by measurement (CloudWatch, X-Ray, Performance Insights) and choosing the right measure (adding caching, read replicas, changing instances, asynchrony, CDN). Compute Optimizer also points out under-provisioned resources.

How it works / steps

  1. Collect user-experience metrics (latency) and resource metrics
  2. Identify slow queries in RDS with Performance Insights
  3. Choose measures that fit the bottleneck
  4. Run the same load test before and after changes and compare the effect
  5. Scale back excess resources once objectives are met

Workplace example

Investigating high DB CPU with Performance Insights shows a specific aggregation query is the cause, so add an index and cache the aggregation results in ElastiCache.

Common confusions and exam tips

Mini quiz

Q1. An internal quoting system's EC2 instance has had CPU utilization above 90% for months and responds slowly. Compute Optimizer shows it is “under-provisioned.” What is the most appropriate next step?

  1. Ignore the Compute Optimizer recommendation and raise the CPU alarm threshold to 99%
  2. Downsize the instance type to cut costs and use the freed budget for another monitoring tool
  3. Ask users to create fewer quotes to reduce CPU load itself
  4. Test the recommended larger or newer-generation instance type in staging, confirm the effect and change it
Show answer and explanation

Answer: D Test the recommended larger or newer-generation instance type in staging, confirm the effect and change it

Right-size based on Compute Optimizer recommendations and usage. Confirm the effect in testing before changing production.

Q2. Which statement about using ElastiCache as a cache is incorrect?

  1. Setting a TTL (expiration) on cached data prevents stale data from remaining indefinitely
  2. Putting frequently read data in memory reduces database read load
  3. When the database is updated, the app must be designed to update or invalidate the cache
  4. Once data is cached it is always synced with the database automatically, so cache handling on updates need not be designed
Show answer and explanation

Answer: D Once data is cached it is always synced with the database automatically, so cache handling on updates need not be designed

ElastiCache does not sync with the database automatically. Design the cache update approach on the app side, such as lazy loading, write-through and TTLs.

Reference links

3.4Determine a strategy to improve reliability

3.4 Determine a strategy to improve reliability.

Concept

Improving reliability of existing systems means finding single points of failure (single AZ, single instance, single connection), making them redundant, and deliberately injecting failures with AWS Fault Injection Service (FIS) to verify resilience (chaos engineering). AWS Resilience Hub can also assess against RTO and RPO targets.

How it works / steps

  1. Review the architecture and identify single points of failure
  2. Assess with Resilience Hub whether target RTO and RPO are met
  3. Add redundancy (Multi-AZ, Auto Scaling, dual Direct Connect)
  4. Test AZ failures and instance stops with FIS and confirm recovery
  5. Improve procedures and architecture based on the results

Workplace example

Run an FIS experiment stopping instances in one AZ and confirm Auto Scaling takes 5 minutes to make up capacity in another AZ, then revisit the minimum instance count.

Common confusions and exam tips

Mini quiz

Q1. In a production-like environment, you want to verify that automatic recovery mechanisms and procedures really work when an AZ fails or instances stop. Which method is most appropriate?

  1. Plan experiments that deliberately inject faults with AWS FIS, define stop conditions and observe the impact
  2. Assume failures will not happen and consider reviewing design documents sufficient for automatic recovery
  3. In production, have staff manually stop instances one after another without notice to check
  4. Judge that the mechanisms work correctly because no failure has ever occurred
Show answer and explanation

Answer: A Plan experiments that deliberately inject faults with AWS FIS, define stop conditions and observe the impact

AWS FIS manages fault injection as experiments and can stop them safely with stop conditions (alarms). Use it to actually verify recovery mechanisms and procedures.

Q2. You want to eliminate single points of failure (SPOFs) in an existing architecture. Private subnets in three AZs all reach the internet through a single NAT gateway in AZ-a. Which measure is the most suitable?

  1. Make Direct Connect redundant at another location
  2. Move the files to Amazon EFS
  3. Place a NAT gateway in each AZ
  4. Make RDS a Multi-AZ deployment
Show answer and explanation

Answer: C Place a NAT gateway in each AZ

A NAT gateway is redundant within its AZ but cannot survive an AZ failure. Place a NAT in each AZ and route each AZ's subnets to it.

Reference links

3.5Identify opportunities for cost optimization

3.5 Identify opportunities for cost optimizations.

Concept

Find cost reduction opportunities in existing environments with Compute Optimizer (right-sizing EC2, EBS, Lambda), S3 Storage Lens (storage usage and lifecycle recommendations), Cost Explorer Savings Plans recommendations and Trusted Advisor (idle resources). Unused Elastic IPs, EBS volumes, snapshots and previous-generation instances are also targets.

How it works / steps

  1. Identify the highest-cost services and accounts with Cost Explorer
  2. Downsize based on Compute Optimizer recommendations
  3. Find buckets without lifecycle configuration with Storage Lens
  4. Review Savings Plans recommendations and utilization before purchasing
  5. Build a mechanism to regularly delete unused resources

Workplace example

Storage Lens finds a bucket with 50 TB of incomplete multipart uploads; delete them with a lifecycle rule to lower the monthly bill.

Common confusions and exam tips

Mini quiz

Q1. You do not know where personal data is stored in S3 across many accounts. Which method is most appropriate?

  1. Detect suspicious bucket access with GuardDuty S3 Protection
  2. View object counts and size per bucket in S3 Storage Lens
  3. Enable Amazon Macie organization-wide to discover sensitive S3 data automatically
  4. Find unencrypted buckets with AWS Config rules
Show answer and explanation

Answer: C Enable Amazon Macie organization-wide to discover sensitive S3 data automatically

Macie analyzes S3 data with machine learning and pattern matching to discover sensitive data such as personal information. A delegated administrator manages the whole organization centrally. [Other options] Config checks settings, not personal data in objects. Storage Lens analyzes usage. GuardDuty detects access threats and doesn't classify data.

Q2. You are starting a company-wide AWS cost reduction effort. What should you do first?

  1. Buy Compute Savings Plans to lower EC2 and Lambda prices
  2. Give every department a flat 20% reduction target and let them choose how
  3. Check the breakdown by usage type in Cost Explorer and prioritize the biggest items
  4. Resize every instance following Compute Optimizer recommendations
Show answer and explanation

Answer: C Check the breakdown by usage type in Cost Explorer and prioritize the biggest items

First understand the cost breakdown and causes, and start with the highest-impact items. Unfounded uniform cuts or wholesale changes risk affecting the business. [Other options] Buy Savings Plans after understanding usage. Applying all recommendations at once skips checking business impact. A flat target ignores the biggest items.

Reference links

Lessons are written by this site based on public information and do not guarantee exam content. Product specifications change, so check the latest information at the reference links.

Notes (unofficial, original questions, no pass guarantee)