CV0-004 — CompTIA Cloud+ (CV0-004) Exam Quick Reference

How to Use This Quick Reference

This Quick Reference supports independent preparation for the CompTIA Cloud+ (CV0-004) exam. Use it to review high-yield decision points, compare cloud technologies, and practice scenario reasoning.

CV0-004 questions often test best-fit choices, not definitions alone. When reading a scenario, identify:

1. Workload requirement: latency, availability, compliance, cost, performance, scale.
2. Operational model: self-managed, provider-managed, automated, outsourced.
3. Risk constraint: security, data loss, vendor lock-in, downtime, skills gap.
4. Most appropriate control: preventive, detective, corrective, compensating.
5. Troubleshooting signal: metric, log, trace, alert, dependency, recent change.

Cloud Models and Responsibility

Deployment Models

Service Models and Responsibility

Trap: “Cloud provider manages security” is incomplete. The provider secures the cloud infrastructure; the customer still secures identities, data, configurations, and workload access.

Workload Placement Decision Path

    flowchart TD
	    A[New or migrating workload] --> B{Strict data locality or legacy dependency?}
	    B -->|Yes| C[Hybrid or private placement]
	    B -->|No| D{Need OS/kernel customization?}
	    D -->|Yes| E[IaaS VM or bare metal]
	    D -->|No| F{Containerized microservice?}
	    F -->|Yes| G[Managed Kubernetes or container platform]
	    F -->|No| H{Event-driven short task?}
	    H -->|Yes| I[FaaS/serverless]
	    H -->|No| J{Standard business application?}
	    J -->|Yes| K[SaaS if fit exists]
	    J -->|No| L[PaaS or managed service]

Architecture and Design Reference

Cloud Design Qualities

Compute Selection Matrix

Common Architecture Traps

Availability, Capacity, and Performance Formulas

Use formulas for relative reasoning; provider-specific SLAs and limits vary.

Availability of Dependent Components

For components that must all work:

For redundant alternatives where either component can serve traffic:

IPv4 Subnet Size

Cloud providers may reserve addresses in a subnet, so do not assume every address is usable.

High-Yield Metrics

Networking Quick Reference

Core Network Components

Load Balancer Selection

Network Security Distinctions

CIDR Quick Table

Network Troubleshooting Cues

Storage and Data Services

Storage Selection Matrix

Data Protection Concepts

Storage Performance Cues

Identity, Security, and Governance

IAM Terms That Drive Scenario Answers

Access Control Models

Security Control Selection

Encryption and Key Management

Shared Responsibility Traps

Automation, DevOps, and Deployment

Automation Tool Selection

Deployment Strategies

Terraform-Style IaC Workflow

terraform init
terraform fmt -check
terraform validate
terraform plan -out=tfplan
terraform apply tfplan
terraform state list

High-yield points:

• Plan before apply to review intended changes.
• State files are sensitive because they can contain resource details and secrets.
• Use remote state locking in teams to prevent concurrent changes.
• Do not manually change cloud resources if IaC owns them; this creates drift.

Kubernetes Operations Snippets

kubectl get nodes
kubectl get pods -A
kubectl describe pod <pod-name>
kubectl logs <pod-name>
kubectl exec -it <pod-name> -- /bin/sh
kubectl rollout status deployment/<deployment-name>
kubectl rollout undo deployment/<deployment-name>

Common Kubernetes distinctions:

Minimal deployment concept:

apiVersion: apps/v1
kind: Deployment
metadata:
  name: web
spec:
  replicas: 3
  selector:
    matchLabels:
      app: web
  template:
    metadata:
      labels:
        app: web
    spec:
      containers:
        - name: web
          image: example/web:stable
          ports:
            - containerPort: 8080

Monitoring, Observability, and Troubleshooting

Observability Signals

SLI, SLO, and SLA

Troubleshooting Method

1. Identify symptoms and scope.
2. Determine what changed recently.
3. Check health dashboards, logs, metrics, and alerts.
4. Test dependencies: DNS, network path, IAM, storage, database, external services.
5. Form and test one hypothesis at a time.
6. Apply least-risk fix first when production is affected.
7. Validate service recovery.
8. Document root cause and preventive action.

Symptom-to-Cause Table

Resilience, Backup, and Disaster Recovery

RTO and RPO

Trap: Low RPO does not automatically mean low RTO. Replicated data can still take time to promote, reconnect, validate, and secure.

Backup Types

DR Strategy Selection

Resilience Design Checklist

Migration and Modernization

Migration Strategies

Migration Planning Reference

Data Migration Options

Cost Management and Optimization

Cost Drivers

Governance Controls

Cost Optimization Traps

Security Operations and Incident Response

Incident Response Phases

Cloud Forensics Considerations

High-Yield Exam Distinctions

Final Review Checklist

Before exam day, be able to:

• Match workloads to IaaS, PaaS, SaaS, containers, and serverless.
• Explain shared responsibility for compute, data, IAM, and SaaS usage.
• Choose storage by access pattern, latency, sharing, and durability needs.
• Troubleshoot routing, DNS, NAT, VPN, load balancers, and firewalls.
• Select IAM controls for least privilege, federation, MFA, and temporary access.
• Compare backup, snapshot, replication, HA, and DR strategies.
• Use RTO/RPO to select appropriate recovery designs.
• Recognize when automation, IaC, CI/CD, and policy-as-code reduce risk.
• Interpret metrics, logs, traces, alerts, and audit events during incidents.
• Identify cost, governance, and compliance tradeoffs in cloud scenarios.

Practical Next Step

Use this Quick Reference to mark weak areas, then move into scenario-based practice for CompTIA Cloud+ (CV0-004). For each missed question, write down the decision cue, the tempting wrong answer, and the control or service that best satisfies the requirement.