CompTIA Cloud+ (CV0-004) — All Questions

A recovery plan states that after a disaster, the application must be restored within four hours. Which metric does the four-hour target represent?

• a.Recovery Point Objective (RPO)
• b.Mean Time Between Failures (MTBF)
• c.Recovery Time Objective (RTO)✓
• d.Service Level Indicator (SLI)

The Recovery Time Objective (RTO) is the maximum acceptable time to restore service after an incident. RPO measures acceptable data loss (time), MTBF measures reliability, and an SLI is a measured performance signal.

An operations team wants to be alerted only when CPU utilization stays above 85 percent for ten consecutive minutes, to avoid noise from brief spikes. Which monitoring concept should they configure?

• a.An alert threshold with a sustained duration condition✓
• b.A one-time snapshot of the current CPU value
• c.A static inventory report generated monthly
• d.A billing alarm on total account spend

Configuring an alert threshold combined with a duration (evaluation period) ensures notifications fire only when a condition persists, reducing false alarms from transient spikes. Snapshots, inventory reports, and billing alarms do not address sustained performance alerting.

Which practice best supports a reliable backup strategy in the cloud?

• a.Storing backups only on the same volume as the production data
• b.Never testing restores to save time
• c.Keeping a single backup copy indefinitely
• d.Periodically testing restores to verify backups are usable✓

A backup is only valuable if it can be restored, so periodic restore testing verifies integrity and process. Co-locating backups with production data, skipping tests, or relying on a single copy all undermine recoverability.

A workload experiences predictable traffic surges every weekday at 9 a.m. Which automation approach most efficiently prepares capacity ahead of the surge?

• a.Reactive scaling only after latency alarms trigger
• b.Scheduled (predictive) scaling that adds capacity before 9 a.m.✓
• c.Manually launching instances each morning
• d.Disabling autoscaling to keep the environment simple

Scheduled scaling adds capacity in advance of known, recurring demand so users do not experience the lag of purely reactive scaling. Reactive-only scaling responds after degradation begins, and manual launches are error-prone and slow.