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

Blue-green switches all traffic between two parallel environments at once, canary gradually increases exposure starting from a small percentage, rolling incrementally replaces instances while maintaining availability, and in-place updates every instance simultaneously, typically with some downtime.

An unapproved tool installed to bypass standard access controls is specifically unauthorized software. Authentication issues concern credential-related problems like leaked credentials, cipher suite deprecations concern outdated encryption algorithms, software vulnerability issues generically concern exploitable code flaws in otherwise approved software, and authorization issues concern permission-related problems like privilege escalation rather than an unapproved tool being installed.

A port configured for a single untagged VLAN when the server needs multi-VLAN tagged traffic is an access-versus-trunk-port misconfiguration; the port needs to be a trunk port rather than an access port. Scope exhaustion concerns a DHCP pool running out of addresses, network overlap concerns duplicate address ranges, missing routes concerns absent routing entries, and MTU mismatch concerns packet size handling rather than VLAN tagging capability.

A deployment halting because the service account lacks a required permission is specifically a permission issue. Incompatibility concerns components that don't work together correctly, sizing issues concern inappropriately sized resources, outdated component definitions concerns stale version references, and deprecation of functionality concerns a feature being phased out entirely rather than a missing access grant.

Categorizing data by sensitivity level is data classification, while requiring data to remain within a specific country's borders per legal requirement is data sovereignty. Data ownership concerns who holds rights to the data, litigation hold suspends deletion for legal proceedings, and data locality alone is a related but narrower physical-location concept rather than the broader legal residency requirement described here.

CVE provides standardized identifiers for publicly known vulnerabilities, enabling consistent tracking and reference across tools and reports. CVSS scores the severity of a given vulnerability rather than identifying it, and SOC2, PCI DSS, and ISO 27001 are compliance and industry standards rather than a vulnerability identifier system.

A major update typically introduces significant new capabilities and may include breaking changes requiring integration updates, unlike a minor update which typically adds smaller, backward-compatible improvements.

Integrity testing confirms restored data is complete and uncorrupted, such as through checksum comparison against the original. Recoverability testing confirms that a restore can actually be performed successfully at all, while bulk recovery, granular recovery, and in-place recovery describe recovery scope and method rather than data correctness verification.

Manual scaling requires explicit human action to add or remove capacity, with no automatic trigger of any kind. Triggered scaling based on load or trending reacts automatically to metrics, scheduled scaling activates at predefined times, and horizontal scaling specifically concerns adding instances rather than describing the human-initiated activation mechanism itself.

Retention defines how long logs are kept before deletion, balancing compliance requirements against storage costs.

Ensuring data is stored and processed only in regions meeting regulatory residency requirements is a compliance requirement. Performance requirements concern speed and responsiveness, cost requirements concern budget, network requirements concern connectivity and bandwidth, and compute requirements concern processing capacity rather than regulatory geographic constraints.

A conditional executes a block of logic only if a specified condition, such as a resource not already existing, evaluates as true. Variables store reusable values, data types generically describe the kind of value stored, functions encapsulate reusable logic blocks, and operators alone perform comparisons or calculations rather than making the branching decision itself.

Re-architecting substantially redesigns an application, such as converting a monolith to microservices, to fully leverage cloud-native capabilities. Rehosting moves the application with no changes, replatforming makes only minor adjustments, retaining keeps the application where it is, and retiring shuts the application down entirely rather than redesigning it.

Tagging applies key-value labels to resources, enabling cost attribution to specific departments or projects. Rightsizing adjusts resource sizing to match actual usage, resource metering tracks consumption for billing broadly, and reserved resources and spot instances are billing models rather than the labeling mechanism itself.

An on-premises deployment runs a private cloud within the organization's own data center, giving full hardware control while adopting cloud-like self-service capabilities. Public cloud is operated by a third-party provider for general use, hybrid combines multiple deployment models, community cloud is shared among multiple organizations, and multicloud describes using multiple different cloud providers rather than describing where a single private cloud is physically hosted.

Ansible automates configuration management using human-readable playbooks and is agentless, requiring no software installed on managed servers. Terraform focuses on infrastructure provisioning rather than configuration management specifically, Jenkins automates CI/CD pipeline execution, Grafana visualizes metrics and dashboards, and Kubernetes orchestrates containerized workloads rather than providing agentless configuration management.

A code commit records a snapshot of staged changes into the local repository history with a descriptive message. Code push uploads those local commits to a remote repository, a pull request submits changes for team review before merging, code review examines the changes themselves, and branch management alone organizes separate lines of development rather than recording a snapshot of changes.

Cryptojacking is the unauthorized use of compute resources to mine cryptocurrency, typically running silently in the background. Ransomware encrypts data for extortion, DDoS floods a target with traffic to disrupt availability, a zombie instance generically describes an abandoned but legitimate resource rather than active unauthorized mining, and social engineering manipulates people rather than describing this resource-hijacking attack.

CIS benchmarks are widely recognized, industry-consensus configuration hardening recommendations applicable across multiple providers. Vendor-specific benchmarks are published by a single cloud provider for their own platform, PCI DSS addresses payment card data protection specifically, SOC2 addresses broader trust service criteria, and GDPR governs personal data protection rather than providing general configuration hardening guidance.

A subnet-level control evaluating traffic statelessly by IP and port is a network ACL, while an instance-level, stateful control that tracks connections is a network security group. A WAF filters application-layer web traffic specifically, IPS/IDS provides broader intrusion detection and prevention, and VPC peering connects two virtual networks rather than filtering traffic at either the subnet or instance level.

A hot site is a fully staffed, continuously running standby facility with real-time replication, ready for near-immediate failover at significant cost. A cold site provides only basic infrastructure requiring substantial setup time, a warm site is partially configured with a moderate activation time, and an availability zone or region alone describe cloud infrastructure geography rather than a dedicated standby disaster recovery facility.

SaaS delivers a complete, ready-to-use application accessed over the internet, with the provider handling all underlying software and infrastructure. IaaS provides virtualized infrastructure the customer still manages, PaaS provides a platform for deploying custom applications, FaaS runs individual triggered functions, and the shared responsibility model describes the division of security duties rather than being a service model itself.

Low-power sensors transmitting data to a centralized platform for monitoring is a core IoT use case. Machine learning and AI describes a different category of evolving technology focused on data analysis and pattern recognition, and generative AI, visual recognition, and text-to-voice are all specific AI capabilities rather than the sensor-and-connectivity category these devices belong to.

IOPS measures the number of read and write operations a storage volume can handle per second, directly impacting database and transactional performance. Throughput alone measures data volume transferred over time rather than operation count, latency measures delay per operation, CPU utilization measures compute usage, and network bandwidth measures network capacity rather than storage operation rate.

Provider-managed database deployment has the cloud vendor handle patching, backups, and infrastructure maintenance, letting the team focus on schema and queries. Self-managed deployment requires the customer to handle that maintenance directly, relational and non-relational describe database data models rather than management responsibility, and on-premises hosted describes physical location rather than who manages the database.