NAVER Cloud Platform Certified Associate key terms

A geographically separate location where NAVER Cloud Platform resources are deployed, containing multiple availability zones so workloads can be isolated and kept close to users.

An isolated data center group inside a region with independent power and network paths, used to spread resources so a single facility failure does not take down an entire service.

An architecture pattern that places instances or storage replicas across two or more zones in one region to improve availability and survive a zone-level outage.

A logically isolated network in NAVER Cloud Platform where you define IP ranges, subnets, routing, and gateways to control traffic between your resources and the internet.

A range of IP addresses carved out of a VPC and bound to one zone, used to separate public-facing resources from private resources and to control routing per tier.

A stateful virtual firewall attached to individual server instances that allows or denies inbound and outbound traffic by protocol, port, and source or destination address.

A stateless subnet-level traffic filter evaluated by ordered allow and deny rules, providing a coarser second layer of network control beyond instance-level security groups.

A set of rules inside a VPC that decides where traffic for a given destination prefix is sent, such as to a local subnet, internet gateway, NAT gateway, or VPN.

A managed service that lets instances in private subnets initiate outbound internet connections, such as software updates, without exposing them to inbound traffic from the internet.

A virtual machine created from a chosen image and server specification, offering configurable CPU, memory, and disk that you can start, stop, and resize.

A template containing an operating system and optional preinstalled software used to create servers consistently, and to recreate or scale out identical instances.

A predefined or custom combination of vCPU, memory, and disk performance that determines the capacity and price of a compute instance.

A user-supplied shell script executed automatically the first time a server boots, commonly used to install agents, join clusters, or configure application settings.

A managed collection of identical servers that automatically adds or removes instances according to policies, maintaining capacity during demand changes and replacing unhealthy members.

A rule that triggers scaling actions, such as a target metric threshold, a scheduled time, or a manual adjustment, defining how many instances to add or remove.

The saved template for an auto scaling group that specifies the server image, server spec, init script, and network settings used whenever a new instance is launched.

A managed container orchestration offering that provisions and operates Kubernetes clusters, handling control plane availability, upgrades, and node pool management for containerized workloads.

A group of worker nodes inside a managed Kubernetes cluster that share the same specification and can be scaled or upgraded as a unit.

A private repository for storing, versioning, and distributing container images that clusters and servers pull when deploying containerized applications.

A highly durable service for storing unstructured data as objects inside buckets, accessed over HTTP APIs and suited to backups, media files, logs, and static website content.

Network-attached disk volumes that behave like local drives and are attached to a single server, typically used for operating systems and databases needing low-latency random access.

A shared file storage service that multiple servers can mount simultaneously over a network protocol, useful for shared application content and clustered workloads.

A point-in-time copy of a block storage volume that can be used to restore data or create new volumes, forming a basic backup mechanism for server disks.

A rule set that automatically transitions stored objects to cheaper tiers or deletes them after a defined age, reducing storage cost without manual cleanup.

A service that distributes incoming traffic across multiple backend servers, performs health checks, and can terminate TLS, improving availability and horizontal scalability.

A periodic probe that tests whether a backend target responds correctly, so load balancers and auto scaling can stop sending traffic to or replace failing instances.

A managed domain name service that resolves hostnames to your resources and supports routing policies such as failover and weighted distribution across endpoints.

A content delivery network that caches static and media content at edge locations close to users, reducing origin load and improving download latency.

A managed relational database service where the provider handles provisioning, patching, backup, and failover for engines such as MySQL, PostgreSQL, and others.

An additional database instance that asynchronously copies the primary and serves read-only queries, scaling read throughput and offloading reporting workloads.

The automatic promotion of a standby database or server to primary when the active one becomes unavailable, minimizing downtime without manual intervention.

The configured period during which automatic database backups are kept and available for point-in-time restoration, balancing recovery options against storage cost.

A managed in-memory key-value store used for caching, session storage, and fast lookups, reducing load on backend databases and lowering response times.

A secondary identity created under the main account with its own credentials and assigned permissions, used to give people or systems limited access instead of sharing root credentials.

A document that lists allowed or denied actions on specified resources, attached to sub accounts, groups, or roles to define exactly what access they receive.

An identity that can be assumed temporarily by trusted users or services to obtain scoped permissions without storing long-term credentials, commonly used for cross-service access.

A credential pair used for programmatic API and CLI authentication, which must be stored securely, rotated regularly, and avoided in source code.

A security principle of granting only the permissions needed for a task and nothing more, limiting the blast radius if credentials are leaked or misused.

A monitoring service that collects metrics and logs from resources, supports dashboards and alarms, and can trigger notifications or auto scaling actions.

Tools that show current charges by service and resource, support budgets and alerts, and help teams attribute and control cloud spending.

A toolset for moving on-premises or other-cloud workloads into NAVER Cloud Platform, including server replication, database transfer, and data synchronization.

An architecture that connects on-premises data centers with cloud resources through private connectivity or VPN, letting workloads span both environments securely.

Managed offerings for building and running AI features, such as speech recognition, vision, translation, and language models, accessed through APIs instead of self-hosted infrastructure.