CV0-004 Operations and Support Practice Test 10 — 15 Questions

Question 1

A cloud administrator needs to centralize logs from multiple cloud provider accounts and on-premises servers for security analysis. Which approach should be used?

Accepted Answer

Configure each account's API activity logging to deliver logs to a central storage bucket, and use a log collection agent on on-premises servers to send logs to a central log service. The correct approach is to configure each cloud account's API activity logging (e.g., AWS CloudTrail, Azure Activity Log, GCP Audit Logs) to deliver logs to a central storage bucket, and use a log collection agent on on-premises servers to forward logs to a central log service. This centralizes logs from both cloud and on-premises sources for unified security analysis.

Answer

Create a serverless function that copies logs from each account to a central storage bucket in a management account

Answer

Enable virtual network flow logs in each account and store them locally

Answer

Use configuration compliance rules to aggregate logs into a single account

Question 2

A cloud engineer is implementing a tagging strategy for cost allocation. Which tags should be applied to resources to track costs by business unit and environment?

Accepted Answer

BusinessUnit and Environment. BusinessUnit and Environment are the two dimensions explicitly required to track costs by business unit and environment, so tagging resources with these keys directly enables cost allocation reports filtered on those values. Cloud providers' cost explorers and billing dashboards group spend by tag key/value, making these the correct tag pair.

Answer

Owner and Department

Answer

Project and Application

Answer

Location and Region

Question 3

During a scheduled DR drill, the cloud team fails over a critical application to the secondary region. After the drill, the application is failed back. The application's RTO was 2 hours, but the actual failover took 2.5 hours. Which action should be taken to improve future failover times?

Accepted Answer

Automate the failover process using infrastructure as code and runbooks. The failover exceeded RTO because manual steps introduced delay; automating the failover with infrastructure as code (IaC) and pre-defined runbooks removes human latency, ensures consistent execution order, and reduces the time to bring up the secondary region. Automation directly attacks the root cause of the 30-minute overrun — manual coordination and decision-making — and is the standard DR improvement after a drill reveals timing gaps. This aligns with the DR principle of 'test, measure, improve' by codifying the recovery process.

Answer

Increase the frequency of DR drills

Answer

Increase the bandwidth between regions for data replication

Answer

Reduce the RTO to 1 hour to force faster execution

Question 4

A cloud administrator needs to apply security patches to a group of Windows servers during a maintenance window to minimize disruption. Which type of service should be used?

Accepted Answer

Patch automation service with maintenance window scheduling. The administrator needs to apply security patches to a group of Windows servers during a specific maintenance window to minimize disruption. A patch automation service with maintenance window scheduling is designed exactly for this purpose: it automates the deployment of patches and allows scheduling within defined windows, ensuring updates occur only during approved times. This directly addresses the requirement to apply patches while controlling when they happen to avoid service interruptions.

Answer

Vulnerability assessment service

Answer

Configuration compliance service

Answer

Configuration management and automation service

Question 5

A cloud architect is designing an auto-scaling policy for a web application. The application's traffic spikes predictably every weekday at 9 AM and decreases after 5 PM. Which scaling policy is most cost-effective?

Accepted Answer

Scheduled scaling policy that increases capacity at 8:45 AM and decreases at 5:15 PM. Scheduled scaling is designed for predictable, time-based traffic patterns. Scaling up at 8:45 AM and down at 5:15 PM pre-provisions capacity before the 9 AM spike and removes it after the 5 PM decline, avoiding the lag and over-provisioning inherent in reactive policies. This is the most cost-effective approach for a known weekly pattern.

Answer

Step scaling policy that adds instances when CPU > 70%

Answer

Simple scaling policy with a cooldown of 300 seconds

Answer

Target tracking policy with a target CPU of 50%

Question 6

A cloud administrator needs to ensure that log data is retained for one year to meet compliance requirements. Which action should be taken for the log group in CloudWatch Logs?

Accepted Answer

Set the log group's retention policy to 365 days. CloudWatch Logs log groups have a retention setting that controls how long log events are kept before automatic deletion. Setting the retention policy to 365 days ensures logs are retained for exactly one year, meeting the compliance requirement without manual intervention.

Answer

Create a CloudWatch Events rule to delete logs after one year

Answer

Increase the log group's data durability by enabling encryption

Answer

Export logs to Amazon S3 and delete the log group

Question 7

A company uses a hybrid cloud environment with workloads in AWS and on-premises. They want to use a single monitoring dashboard to view metrics from both environments. Which solution should they implement?

Accepted Answer

Install the CloudWatch agent on on-premises servers and send metrics to CloudWatch, then create a CloudWatch dashboard. The CloudWatch agent can be installed on on-premises servers to collect OS-level and application metrics and push them to CloudWatch over the public internet or a VPN/Direct Connect. Once the metrics are in CloudWatch, they appear alongside AWS-native metrics and can be visualized in a single CloudWatch dashboard, satisfying the hybrid monitoring requirement. This is the native, lowest-friction way to unify metrics from both environments.

Answer

Deploy a third-party monitoring tool in AWS and replicate all logs to it

Answer

Set up a VPN connection and use VPC Flow Logs for on-premises traffic

Answer

Use AWS CloudTrail to log on-premises activity

Question 8

A company is performing a disaster recovery test for a critical application. The test reveals that the application's RTO of 1 hour is not being met due to slow database restoration. Which THREE actions could help improve the restoration time? (Select THREE.)

Accepted Answer

Implement continuous replication to a standby database. Option A (Implement continuous replication to a standby database) is correct because continuous replication keeps a standby copy nearly in sync with the primary, so failover requires little or no data restoration, drastically cutting the time to recover within the 1-hour RTO. Option B (Pre-warm standby database instances in the recovery region) is correct because pre-warming keeps compute, cache, and database processes already running and initialized, eliminating the startup and warm-up latency that would otherwise delay recovery. Option E (Use provisioned IOPS storage for the database volumes) is correct because restoring or replaying data is I/O-bound, and provisioned IOPS delivers guaranteed, higher disk throughput and lower latency, directly accelerating database restoration. Option C is not appropriate because disabling encryption weakens security and encryption overhead is not the primary bottleneck in slow restores. Option D is not appropriate because increasing backup retention only keeps backups longer; it does not make restoring any single backup faster.

Answer

Disable encryption on the database to reduce overhead

Answer

Increase the retention period of automated backups

Question 9

A cloud engineer wants to be notified when the average CPU utilization of an auto-scaling group exceeds 80% for 5 minutes. Which alerting mechanism should be used?

Accepted Answer

AWS CloudWatch Alarm. AWS CloudWatch Alarms are purpose-built to watch a metric (like the Average CPUUtilization of an Auto Scaling group) and trigger actions when a threshold is breached for a defined number of evaluation periods. Configuring an alarm with a threshold of 80%, a period of 300 seconds, and the appropriate statistic/datapoints-to-alarm directly satisfies the 'exceeds 80% for 5 minutes' requirement. Alarms can then notify via SNS, trigger Auto Scaling, or invoke actions.

Answer

AWS Systems Manager OpsCenter

Answer

AWS Config rule

Answer

AWS Trusted Advisor

Question 10

A company wants to implement a disaster recovery strategy with an RTO of 15 minutes and an RPO of 1 minute for a critical database. Which approach should be used?

Accepted Answer

Cross-region continuous replication with automatic failover. The requirement is an RTO of 15 minutes and an RPO of 1 minute. Cross-region continuous replication with automatic failover provides near-zero RPO (often seconds) and rapid RTO (minutes) by continuously replicating data and automatically promoting a standby in another region. This is the only option that can meet both the 1-minute RPO and 15-minute RTO.

Answer

Scheduled snapshots every hour

Answer

Daily snapshots copied to another region

Answer

Weekly full backups to tape stored offsite

Question 11

A cloud administrator wants to analyze network traffic to troubleshoot connectivity issues between VMs. Which feature should be enabled?

Accepted Answer

Network flow logs. Network flow logs capture metadata about IP traffic (source/destination IP, ports, protocol, bytes, packets, accept/reject) flowing through cloud network interfaces, subnets, or VPCs. This data is exactly what an administrator needs to troubleshoot connectivity issues between VMs, such as identifying blocked ports or asymmetric routing. Flow logs are available in AWS VPC Flow Logs, Azure NSG Flow Logs, and GCP VPC Flow Logs.

Answer

Audit logging service

Answer

Distributed tracing service

Answer

Configuration compliance service

Question 12

A cloud team wants to automatically scale an application based on the number of pending messages in a message queue. Which scaling policy type should be used?

Accepted Answer

Dynamic scaling (metric-based). Dynamic scaling (metric-based) adjusts the number of instances to keep a specific metric, such as queue depth, at a target value. This is the appropriate policy for scaling based on real-time queue depth.

Answer

Scheduled scaling

Answer

Manual scaling

Answer

Static scaling

Question 13

A company wants to ensure that logs from their application are easily searchable and structured for analysis. Which logging format should be recommended?

Accepted Answer

JSON format. JSON is a structured, self-describing format with key-value pairs that log aggregation tools (Splunk, ELK, CloudWatch Logs Insights) can parse natively without custom regex. This makes logs easily searchable by field name and enables structured queries, filtering, and aggregation across large volumes.

Answer

CSV format

Answer

Binary format

Answer

Plain text format

Question 14

A cloud administrator notices that an auto-scaling group is frequently adding and removing instances due to brief spikes in CPU usage. What should be adjusted to stabilize the scaling activity?

Accepted Answer

Increase the cooldown period. Increasing the cooldown period prevents the auto-scaling group from launching or terminating additional instances immediately after a scaling activity, which smooths out reactions to brief CPU spikes. A longer cooldown gives metrics time to stabilize before another scaling decision is made, reducing thrashing. This directly addresses the frequent add/remove behavior described.

Answer

Increase the maximum instance count

Answer

Decrease the minimum instance count

Answer

Decrease the cooldown period

Question 15

A cloud engineer wants to view a dashboard showing cost breakdown by department. Which tool provides pre-built billing dashboards?

Accepted Answer

AWS Cost Explorer. AWS Cost Explorer includes pre-built reports and dashboards that break down costs by dimensions such as service, linked account, and tag, which can represent departments. It is the native AWS tool for visualizing and analyzing billing data, including cost by department when tags are used.

Answer

AWS CloudWatch

Answer

AWS Trusted Advisor

Answer

AWS Config