Home › AWS SysOps Associate › cloudcomputing › sysopsmonitoring › An EC2 instance's CPU steady-state is fine but b…
An EC2 instance's CPU steady-state is fine but bursts to 100% during scheduled jobs. The team wants to verify they aren't depleting CPU credits on a T-family burstable instance. Which CloudWatch metric helps?
A`CPUCreditBalance` and `CPUCreditUsage` on the instance
B`StatusCheckFailed` and `EBSReadOps`
C`NetworkOut` and `NetworkPacketsOut`
D`MemoryUtilization` and `SwapUsage`
Answer & Solution
Correct answer: A. `CPUCreditBalance` and `CPUCreditUsage` on the instance
T-family instances use a credit-based CPU model — `CPUCreditBalance` and `CPUCreditUsage` show whether the workload runs out of credits and gets throttled. The other metrics don't measure CPU credits.
Related questions
An EC2 Auto Scaling group is set to launch from an AMI baked weekly. After the latest AMI A team needs disaster recovery with an RTO ≤ 15 minutes and RPO ≤ 5 minutes across two AWSWhich service detects unexpected drift between an AWS resource's actual configuration and A multi-AZ RDS deployment for a write-heavy database experiences a primary AZ failure. WhaWhich automation pattern is BEST for self-healing a stuck EC2 instance — for example, restAn RDS database needs point-in-time-restore for 14 days plus a guaranteed daily backup. WhWhich Route 53 routing policy is used to fail traffic over from a primary endpoint to a stAn EC2 fleet behind an ALB needs to scale out when average CPU goes above 70% for 5 minute