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

Scaling based on a predefined time, regardless of real-time demand, is scheduled scaling. Triggered scaling based on load or trending reacts to actual real-time metrics rather than a fixed clock time, manual scaling requires human initiation, and vertical scaling specifically concerns resizing existing resources rather than the scheduling mechanism itself.

Instances still accepting an outdated, deprecated cipher suite is specifically a cipher suite deprecation issue. Authorization issues concern permission-related problems like privilege escalation, authentication issues concern credential-related problems, unauthorized software concerns unapproved applications, and software vulnerability issues generically concern exploitable code flaws rather than an outdated cryptographic algorithm configuration.

Two networks configured with the same address range, causing conflicts when connected, is network overlap. Scope exhaustion concerns a DHCP pool running out of addresses, missing routes concerns absent routing table entries, misconfigured tags concerns VLAN tagging errors, and access versus trunk ports concerns switch port configuration rather than overlapping address ranges between two VPCs.

A deployment referencing a component version that no longer exists in the registry is specifically an outdated component definition issue. Incompatibility concerns components that exist but don't work together correctly, sizing issues concern inappropriately sized resources, permission issues concern access rights, and regional service availability concerns whether a service exists in a given region rather than a stale version reference.

REST uses a lightweight, resource-oriented approach with standard HTTP methods, favoring simplicity over more rigid alternatives. SOAP relies on a more rigid, XML-based messaging structure, RPC invokes remote procedures directly rather than emphasizing resource orientation, web sockets provide persistent bidirectional connections, and GraphQL exclusively offers a flexible query language approach rather than this simpler HTTP-method-based style.

Code review is the process of examining specific line-by-line changes before approving a merge, exactly matching this pull request evaluation step. Code push uploads commits to a remote repository, branch management alone organizes separate lines of development, version management alone tracks change history broadly, and a code commit alone records a snapshot locally rather than describing the act of reviewing changes.

A zombie instance is a forgotten, still-running resource that was never properly decommissioned, continuing to consume resources and potentially expand attack surface unmonitored.

DDoS protection specifically detects and mitigates volumetric floods aimed at overwhelming availability. A WAF filters application-layer content like SQL injection, a network ACL filters traffic at the subnet level, IAM policies govern identity permissions, and a network security group filters traffic at the instance level rather than specifically defending against volumetric availability floods.

Role-based access control assigns permissions based on a defined role or job function, such as analyst or administrator, rather than individually per user. OAuth 2.0 is an authorization delegation framework, discretionary access control lets resource owners assign permissions directly, group-based access control assigns permissions by group membership rather than role definition specifically, and token-based describes an authentication model rather than a role-driven authorization model.

A litigation hold suspends normal data destruction schedules for records that may become relevant evidence in legal proceedings. Data sovereignty concerns geographic data residency requirements, data classification categorizes data by sensitivity, data locality concerns where data physically resides, and data ownership concerns who holds rights to data rather than this litigation-driven retention override.

Defining which systems, applications, and ranges will be included or excluded from an assessment is establishing the scanning scope. Identification discovers vulnerabilities within that defined scope, assessment evaluates findings, remediation applies fixes, and CVE cataloging references the standardized vulnerability database rather than defining what will be scanned.

End of support marks the point where vendor technical assistance stops, which can occur separately from and sometimes before complete end of life when all patches stop entirely. Major and minor updates describe version change types, and decommissioning generically describes the broader retirement process rather than this specific support-cutoff milestone.

Off-site backup storage keeps a copy at a geographically separate location, protecting against a disaster affecting the primary site entirely, unlike on-site backups stored at the same location as the primary data.

An availability zone is an isolated fault domain within a single region, more granular than the region-level failover described in the question. Cloud bursting overflows to additional capacity during demand spikes, edge computing brings processing closer to end users, multicloud tenancy describes using multiple providers, and availability monitoring tracks uptime rather than describing this specific intra-region isolation unit.

Retention defines how long logs are kept before deletion, balancing compliance requirements against storage costs. Collection concerns gathering logs from sources, aggregation concerns combining logs into a centralized location, tracing follows individual requests across services, and alerting notifies based on log-derived conditions rather than defining storage duration.

Ensuring infrastructure can handle traffic spikes without degradation while balancing cost is primarily an availability requirement, often addressed through elastic scaling. Cost requirements alone would focus purely on budget without the traffic-handling angle, compliance requirements concern regulatory constraints, storage requirements alone concern data storage needs, and security requirements concern protection controls rather than handling traffic spikes specifically.

YAML uses indentation to define structure and is widely favored for its human readability in configuration files. JSON uses brackets and braces rather than indentation for structure, XML uses verbose tag-based markup, CSV is a flat tabular format unsuited to nested configuration, and binary formats are not human-readable at all.

Replatforming makes minor adjustments to leverage cloud-native features without a full architectural redesign. Rehosting moves the application with no changes at all, re-architecting substantially redesigns the application, retaining keeps the application where it is, and retiring shuts the application down entirely rather than migrating it with minor adjustments.

Maintaining two complete environments and switching all traffic at once is blue-green deployment, while incrementally updating instances one at a time while keeping some capacity available is rolling deployment. Canary releases to a small percentage of traffic first, in-place deployment updates every instance simultaneously with no gradual replacement, and parallel recovery is a disaster recovery concept rather than either of these two deployment strategies.

A hybrid cloud combines private and public cloud environments, allowing workloads to move between them, exactly matching this on-premises-plus-public-cloud-bursting scenario. Public cloud alone is third-party-operated for general use, private cloud alone serves a single organization exclusively, community cloud is shared among multiple organizations with common needs, and on-premises alone describes hosting location rather than this specific combination of two deployment models.

A virtual network that abstracts multiple physical hosts into a single flat network through encapsulation is an overlay network, while a virtual network dedicated to VM-to-VM traffic on the same host is a VM network. SAN and NAS are storage technologies rather than networking concepts, and local storage refers to storage attached directly to a single host rather than either of these networking abstractions.

Port mapping connects a host port to a container's internal port, exactly matching external port 80 traffic being routed to internal port 8080. Persistent volumes and ephemeral storage concern data durability, image registries store container images, and workload orchestration manages container scheduling and deployment rather than network port translation.

Relying on vendor-operated components like managed databases and queues, rather than operating that software directly, is cloud-provided managed services. Microservices alone describes the architectural style, service discovery describes how services locate each other, fan-out describes distributing one event to many consumers, and loosely coupled architecture alone describes independence between components rather than describing reliance on vendor-managed infrastructure.

Hot tier suits frequent access at higher cost, warm tier balances moderate access and cost, cold tier further prioritizes cost over speed, and archive tier is the lowest-cost, slowest-retrieval option for rarely accessed long-term data, together forming a cost-versus-access-speed spectrum.

BGP dynamically exchanges routing information between networks, allowing routes to adapt automatically to path changes. VLAN segments a local network at layer 2, SDN generically describes software-controlled networking broadly, static routes are manually defined and don't adjust automatically, and route tables alone store routing entries without providing the dynamic exchange protocol itself.