CompTIA Cloud + CV0-004 (V4) Exam Practice Test 1

Horizontal scaling adds more instances to handle increased load. Vertical scaling instead increases the resources of existing instances rather than adding more of them.

An attacker exploiting a misconfiguration to grant themselves higher permissions than originally held is privilege escalation. Unauthorized access generically describes gaining access without permission at all rather than elevating existing access, leaked credentials concerns exposed authentication secrets, software vulnerability issue generically concerns exploitable code flaws, and cipher suite deprecation concerns outdated encryption algorithms rather than an IAM permission escalation.

Scope exhaustion occurs when a DHCP server's configured address pool runs out of available addresses to assign to new clients, exactly matching this symptom of new devices failing to receive an address at all.

Oversubscription allocates more virtual resources than physical capacity actually supports, betting on statistical demand patterns, and causes degradation when that assumption fails under simultaneous load. Sizing issues concern choosing an inappropriately sized resource for a workload, permission issues concern access rights, resource allocation misconfiguration generically is broader, and API throttling concerns rate-limited API calls rather than this specific CPU overcommitment pattern.

An artifact is the packaged output of a build stage, such as a versioned container image or package, ready for deployment. Workflow describes the overall sequence of pipeline stages, testing validates the build before release, code integration merges changes from multiple contributors, and automation generically describes the broader hands-off execution of pipeline steps rather than the specific packaged build output.

A pull request submits proposed changes for review and discussion before merging, exactly matching this team review step. A code commit records a snapshot of changes locally, a code push uploads local commits to a remote repository, branch management alone describes organizing separate lines of development, and version management alone describes tracking change history rather than this specific review-and-approval workflow step.

A WAF specifically inspects and filters application-layer HTTP/HTTPS traffic for attacks like SQL injection and XSS. A network ACL filters traffic at the subnet level based on IP and port, a network security group filters traffic at the instance level, IPS/IDS generically covers broader intrusion detection and prevention, and DDoS protection specifically addresses volumetric availability attacks rather than application-layer attack filtering.

Secrets management centralizes storage and controlled retrieval of sensitive credentials like passwords, avoiding hardcoding them into application code. Zero Trust is a broader security philosophy of continuous verification, hardening reduces a system's attack surface generally, least privilege alone limits granted permissions, and benchmark compliance checks configuration against published standards rather than describing centralized credential storage specifically.

A bastion host is a hardened, publicly accessible instance used as a secure intermediary to reach private instances that have no direct public exposure. An API gateway manages API traffic, federation extends identity trust across organizations, directory-based authentication centralizes identity in a directory service, and OAuth 2.0 is an authorization framework rather than describing this specific network access intermediary.

Data sovereignty concerns legal requirements that data be stored and processed within specific geographic or jurisdictional boundaries. Data classification categorizes data by sensitivity, data retention concerns how long data is kept, data ownership concerns who holds rights to the data, and litigation hold suspends deletion schedules for anticipated legal proceedings rather than governing geographic data location.

Assessment evaluates identified findings to confirm which represent genuine, exploitable weaknesses rather than false positives, informing prioritization before action is taken. Scanning scope defines what will be scanned, identification discovers potential vulnerabilities in the first place, remediation applies the actual fix, and CVE cataloging references the standardized vulnerability database rather than describing this confirmation step.

End of life marks the point where a vendor stops all patches and updates entirely. End of support is typically a separate, sometimes earlier or later, milestone marking the end of vendor technical assistance, major and minor updates describe types of version changes rather than lifecycle endpoints, and decommissioning generically describes the broader retirement process rather than this specific patch-cutoff milestone.

Incremental backups capture only data changed since the most recent backup of any type, whether full or incremental, minimizing daily backup size and time. A full backup captures everything regardless of prior backups, a differential backup captures all changes since the last full backup specifically, growing larger each day, and replication continuously copies data to another location rather than describing a scheduled backup type.

The shared responsibility model defines which security and management responsibilities belong to the cloud provider versus the customer, varying by service model. Multicloud tenancy concerns using multiple providers simultaneously, cloud bursting concerns overflow capacity, availability monitoring tracks uptime, and resource metering tracks consumption for billing rather than describing this responsibility division.

Tracing follows a single request's path across multiple services, measuring the time spent in each, exactly matching this cross-service request-tracking need. Logging records discrete events, alerting notifies when a condition is met, metrics measure quantitative system behavior generally, and triage is the process of prioritizing alerts once they occur rather than following an individual request's path.

Each provisioning requirement category drives specific technical decisions: storage requirements determine storage type selection, performance requirements drive sizing and IOPS decisions, compliance requirements constrain where resources can be deployed, and network requirements define connectivity and bandwidth needs.

Drift detection identifies when a resource's actual live configuration has diverged from what is defined in code, exactly matching an undocumented manual console change. Repeatability describes IaC's ability to consistently reproduce the same environment, versioning tracks changes to the code itself over time, testing validates the code before applying it, and documentation records how the code works rather than detecting a live configuration mismatch.

Rehosting, often called lift-and-shift, moves an application to the cloud with no changes to its architecture or code. Refactoring modifies code to better leverage cloud-native features, re-architecting substantially redesigns the application, replatforming makes minor adjustments without a full redesign, and retaining means keeping the application where it currently is rather than migrating it.

A canary deployment releases a new version to a small subset of traffic first, monitoring closely before gradually increasing exposure. Blue-green maintains two complete parallel environments and switches all traffic at once, rolling deployment incrementally replaces instances across the fleet, in-place deployment updates instances directly, and a rollback reverts to a previous version rather than describing this gradual traffic-shifting release approach.

A community cloud is shared by several organizations with common interests or requirements, exactly matching this consortium-shared research environment restricted to members. Public cloud is available to the general public, private cloud serves a single organization, hybrid combines multiple deployment models, and on-premises alone describes a private cloud hosted within an organization's own facilities.

Data that must survive container deletion and recreation requires persistent volumes, while temporary scratch space that can be discarded is ephemeral storage. Port mapping connects container network ports to the host, image registries store container images, and workload orchestration manages container deployment and scheduling rather than describing these two storage durability concepts.

Loosely coupled architecture specifically describes services that interact through well-defined interfaces and can be changed independently without cascading impact on others. Fan-out describes distributing a single event to multiple consumers, service discovery describes how services locate each other dynamically, microservices alone describes the architectural style without necessarily emphasizing the loose-coupling property itself, and cloud-provided managed services describes provider-operated components rather than this independence characteristic.

Object storage suits large volumes of unstructured data accessed via API, block storage provides raw low-latency volumes for OS or database use, and file storage provides a shared hierarchical directory structure for simultaneous multi-client access, each fitting different workload patterns.

VPC peering creates a direct, private network connection between exactly two VPCs, allowing private IP communication without traversing the public internet. A transit gateway instead serves as a central hub connecting many VPCs and on-premises networks simultaneously, BGP is a routing protocol, static routes are manually defined paths, and SDN is a broader software-defined networking approach rather than this specific point-to-point peering connection.

The maximum tolerable downtime before operations are restored is the recovery time objective, while the maximum tolerable data loss measured in time since the last backup is the recovery point objective. A hot, warm, or cold site describes the readiness level of a standby recovery facility rather than these two specific time-based metrics.