CCP-C key terms

Delivery of computing resources such as servers, storage, and applications over a network on demand, where a provider owns the physical infrastructure and charges customers according to usage.

Software that divides physical hardware into isolated virtual machines or environments, allowing several workloads to run independently on one server and improving utilization.

An architecture where one shared pool of infrastructure serves many customers, with logical isolation ensuring each tenant's data and activity remain separate from others.

The ability to automatically add or remove capacity as demand rises and falls, keeping resources matched to workload needs and to cost.

The ability of a system to handle increased load by adding resources, either by making instances larger (vertical) or by adding more instances (horizontal).

A cloud service model that supplies virtual machines, storage, and networks which the customer configures and manages, while the provider operates the physical data center.

A cloud service model offering a managed runtime and middleware where customers deploy their own code without administering servers, operating systems, or scaling infrastructure.

A cloud service model delivering a complete, provider-managed application over a network, which customers use through a browser or API without managing infrastructure.

Two or more distinct cloud environments, typically private and public, kept separate but connected so applications and data can move between them.

A geographic area containing multiple isolated data centers, selected to place workloads near users and to meet latency, availability, and legal requirements.

The division of security duties in cloud computing: the provider secures the infrastructure, while the customer secures data, identities, configurations, and workloads placed in it.

Policies and technologies that verify who or what is making a request and decide which resources and actions that identity is allowed to use.

A security principle of granting each user, service, or process only the permissions required for its task, limiting damage from compromised credentials or mistakes.

An authentication control requiring two or more independent proofs of identity, such as a password plus a code from a device, before access is granted.

Converting stored data into ciphertext so that disks, backups, or snapshots cannot be read without the correct decryption key.

Protecting data while it moves between systems by encrypting the connection, so intercepted traffic cannot be read or altered.

The process of creating and configuring resources such as servers, networks, and storage so they become ready for use, whether done manually or automatically.

Automated coordination of many resources and tasks to complete a workflow, such as deploying a multi-tier application, scaling a cluster, or recovering a service.

Automatically adjusting the number or size of running resources in response to metrics such as CPU use or queue length, so capacity tracks demand.

A contract that states expected service levels, such as availability and response time, and defines remedies or credits when those targets are missed.

Collecting metrics, logs, and traces to understand system health, detect anomalies, and diagnose causes of failures across distributed applications.

A logically isolated network inside a provider's cloud where you define address ranges, subnets, routes, and gateways for your resources.

A portion of a network's IP address range assigned to one availability zone, used to separate application tiers and control routing.

A notation that expresses an IP address range as an address plus a prefix length, such as 10.0.0.0/16, used for planning cloud networks.

A stateful virtual firewall attached to cloud resources that allows or denies traffic based on protocol, port, and source or destination.

Distributing incoming requests across several servers to improve availability and responsiveness, and to let capacity grow or shrink without changing client configuration.

A storage model holding data as objects with keys and metadata in a flat namespace, accessed through APIs and suited to unstructured files, backups, and static content.

Storage presented as raw volumes attached to a server, which the operating system formats with a file system; suited to databases and low-latency random access.

A point-in-time copy of a volume or database used to restore data after loss or corruption, usually stored incrementally and billed as consumed capacity.

Copying data to another location, zone, or region, continuously or on a schedule, to improve durability and support recovery or local reads.

Rules that automatically move data between storage tiers or delete it after defined periods, controlling retention and cost without manual work.

Defining infrastructure in versioned, machine-readable files that tools apply automatically, replacing manual console or script configuration with repeatable, reviewable changes.

Automated pipelines that build, test, and release code changes frequently, giving fast feedback and reducing the risk of each deployment.

Tools and practices that bring servers and software to a defined state, installing packages and applying settings, and correcting configuration drift over time.

A lightweight, isolated package holding an application and its dependencies, sharing the host operating system kernel and starting far faster than a virtual machine.

Ongoing spending on services as they are consumed, which scales with usage and avoids large upfront purchases of hardware.

A complete estimate of the costs of an option over its life, including purchase, operations, staffing, migration, and exit, used to compare cloud and on-premises approaches.

A discount obtained by committing to a defined amount of usage for a fixed term, trading flexibility for a lower unit price.

Attaching key-value labels to resources so costs, owners, environments, and projects can be identified, reported, and governed at scale.