NAVER Cloud Platform Certified Professional study materials

NAVER Cloud Platform Certified Professional practice questions

One question at a time. Build your NAVER Cloud Platform Certified Professional understanding.

First 50 of 200 questions. Each one lists the choices, the correct answer, and an explanation. The checker at the top of this page saves progress in this browser when it is available.

Continue in the practice tool above to load more questions, 50 at a time.

Question 1NAVER Cloud Platform Fundamentals and Architecture

In NAVER Cloud Platform, which component is the top-level container that groups resources and provides a boundary for access control and billing separation?

Account Correct answer.
Zone
Project
Region

Explanation

The Account is the top-level logical container in NAVER Cloud Platform; resources such as compute instances and storage are created inside an account, and identity, permissions, and billing are managed at that level. Regions and Zones are physical placement concepts, not ownership containers.

Question 2NAVER Cloud Platform Fundamentals and Architecture

A team wants its workloads physically isolated from failures in a single data center while remaining in the same geographic area. Which NAVER Cloud Platform concept should they select?

A different Zone Correct answer.
A different Project
A separate Account
A different Region

Explanation

A Zone is an isolated data center inside a Region. Spreading resources across zones within one region protects against single-data-center failure while keeping latency low. Choosing another region changes geography, and accounts or projects are logical, not physical, boundaries.

Question 3NAVER Cloud Platform Fundamentals and Architecture

Which statement best describes the relationship between a Region and a Zone in NAVER Cloud Platform?

A Zone contains multiple Regions that share one network backbone.
A Region contains multiple Zones that are isolated from each other. Correct answer.
A Zone is a billing unit that spans every Region.
A Region and a Zone are synonyms used for the same data center.

Explanation

Regions are geographic groupings, and each Region contains multiple Zones that are physically separated to reduce correlated failures. Zones never contain Regions, and billing is handled at the account level, not by zones.

Question 4NAVER Cloud Platform Fundamentals and Architecture

An administrator needs to give a new engineer permission to manage only compute resources while blocking access to billing. Which NAVER Cloud Platform capability is designed for this?

Region selection at login
Zone placement policies
Auto-scaling policies
Sub-accounts with assigned permissions Correct answer.

Explanation

Sub-accounts let an organization create additional identities under the main account and grant each one a defined set of permissions, enabling least-privilege access. Region and zone choices affect placement, and auto-scaling affects capacity, not authorization.

Question 5NAVER Cloud Platform Fundamentals and Architecture

A workload must remain available if an entire Zone fails. Which architecture decision directly addresses this requirement?

Deploy all instances into the Region's default Zone only.
Deploy instances across at least two Zones in the same Region. Correct answer.
Deploy all instances into one Zone and enable auto-scaling.
Deploy instances into two different Accounts.

Explanation

Zone-level failure tolerance requires the workload to run in more than one Zone so that a surviving Zone can continue serving traffic. Auto-scaling inside a single failed zone cannot help, and accounts are logical boundaries with no physical isolation guarantee.

Question 6NAVER Cloud Platform Fundamentals and Architecture

Which NAVER Cloud Platform service category provides virtual servers on which a customer installs and operates their own operating system and middleware?

Server (compute) Correct answer.
Object Storage
CDN
DNS

Explanation

The Server category supplies virtual machine instances where the customer controls the OS and middleware layer. CDN, Object Storage, and DNS are separate service categories focused on delivery, data persistence, and name resolution respectively.

Question 7NAVER Cloud Platform Fundamentals and Architecture

A company wants to place its web tier in a private subnet that has no direct route to the internet, while still allowing outbound software updates through a controlled gateway. Which design fits NAVER Cloud Platform networking?

Attach the web tier directly to the internet gateway.
Place the web tier in a private subnet and route outbound traffic through a NAT gateway. Correct answer.
Disable the VPC and use only public endpoints.
Assign public IP addresses to every web server.

Explanation

Private subnets omit a direct internet route; a NAT gateway provides controlled outbound access so instances can fetch updates without being reachable inbound from the internet. Public IPs or direct internet gateway attachment would expose the tier.

Question 8NAVER Cloud Platform Fundamentals and Architecture

What is the primary purpose of a security group in NAVER Cloud Platform?

To replicate data between Regions.
To distribute incoming requests across multiple servers.
To encrypt data at rest in Object Storage.
To act as a virtual firewall controlling inbound and outbound traffic for resources. Correct answer.

Explanation

Security groups are stateful virtual firewalls attached to resources that permit or deny traffic by rule. Encryption, load distribution, and cross-region replication are handled by other services or features.

Question 9NAVER Cloud Platform Fundamentals and Architecture

An application running on a server must read credentials to call another NAVER Cloud Platform API without storing long-lived keys in a configuration file. Which approach aligns with platform identity practices?

Hard-code the main account access key in the source code.
Disable authentication for internal API calls.
Share the main account password with the development team.
Use a sub-account with scoped permissions and manage its credentials securely. Correct answer.

Explanation

Scoped sub-account credentials limit blast radius and can be rotated or stored in a secrets mechanism, which is the recommended identity practice. Hard-coding keys, sharing the root password, or disabling authentication all increase risk without solving the problem.

Question 10NAVER Cloud Platform Fundamentals and Architecture

Which statement about the main account versus sub-accounts in NAVER Cloud Platform is accurate?

The main account cannot be used to manage billing.
The main account holds ultimate control and sub-accounts operate within permissions granted to them. Correct answer.
Sub-accounts can create other sub-accounts regardless of assigned permissions.
Sub-accounts automatically inherit every permission of the main account.

Explanation

The main account is the root identity that owns the organization and its billing, while sub-accounts are constrained by the permissions explicitly assigned. Sub-accounts do not automatically gain full rights, and creating further identities depends on granted permissions.

Question 11NAVER Cloud Platform Fundamentals and Architecture

A team needs block storage that can be attached to a single server and formatted with a file system, similar to a local disk. Which NAVER Cloud Platform storage type matches?

Archive Storage
Block Storage Correct answer.
Object Storage
NAS

Explanation

Block Storage provides volumes attached to a server that the OS formats with a file system, behaving like a local disk. Object Storage is accessed via API for objects, NAS is shared file storage across servers, and Archive Storage targets long-term retention.

Question 12NAVER Cloud Platform Fundamentals and Architecture

Several servers must concurrently read and write the same files using standard file protocols. Which storage option is most appropriate?

Block Storage attached to one server
Object Storage bucket
NAS shared file storage Correct answer.
Local instance disk

Explanation

NAS offers shared file-level storage that multiple servers can mount simultaneously, which suits concurrent file access. Block Storage and local disks are typically attached to a single server, and Object Storage uses an object API rather than file protocols.

Question 13NAVER Cloud Platform Fundamentals and Architecture

Which characteristic distinguishes Object Storage from Block Storage in NAVER Cloud Platform?

Block Storage stores data as immutable objects with metadata.
Object Storage is accessed through APIs using keys and metadata, while Block Storage appears as an attached disk. Correct answer.
Block Storage is accessed only through HTTP GET requests.
Object Storage can only be attached to one server at a time.

Explanation

Object Storage manages data as objects addressed by keys with metadata and is reached over APIs, whereas Block Storage presents raw volumes to a server's operating system. The other options invert these characteristics.

Question 14NAVER Cloud Platform Fundamentals and Architecture

A stateless web application must scale out automatically when CPU utilization rises. Which NAVER Cloud Platform capability should be configured?

Auto Scaling Correct answer.
CDN purge
DNS failover
Snapshot schedule

Explanation

Auto Scaling adjusts the number of server instances based on metrics such as CPU utilization, which is exactly the scale-out requirement. DNS failover, CDN purge, and snapshot schedules address availability, caching, and backup rather than capacity.

Question 15NAVER Cloud Platform Fundamentals and Architecture

What is the main function of a load balancer in a NAVER Cloud Platform architecture?

To store session data persistently.
To distribute client requests across multiple backend servers and perform health checks. Correct answer.
To assign private IP addresses to subnets.
To encrypt traffic between zones.

Explanation

A load balancer spreads incoming requests over healthy backends and removes unhealthy targets from rotation, improving availability and utilization. Encryption, session persistence, and subnet addressing are handled by other mechanisms.

Question 16NAVER Cloud Platform Fundamentals and Architecture

A company needs to connect its on-premises data center to a NAVER Cloud Platform VPC with a dedicated private connection rather than the public internet. Which option should be used?

A CDN distribution
A public IP on each server
An Object Storage bucket policy
A dedicated connection service such as a leased line or VPN gateway Correct answer.

Explanation

Private hybrid connectivity is achieved with a dedicated connection or VPN gateway that links the on-premises network to the VPC without traversing the public internet. Public IPs, CDN, and bucket policies do not create a private network path.

Question 17NAVER Cloud Platform Fundamentals and Architecture

In a VPC design, what determines which IP address range a subnet can allocate to resources?

The load balancer listener port
The number of security groups attached
The Region's default gateway address
The CIDR block assigned to the subnet within the VPC range Correct answer.

Explanation

Each subnet receives a CIDR block carved from the VPC address range, and that block defines the addresses available to resources in the subnet. Gateways, security groups, and listener ports do not define address capacity.

Question 18NAVER Cloud Platform Fundamentals and Architecture

Which NAVER Cloud Platform service is designed to cache content at edge locations so users receive it with lower latency?

NAS
Cloud DB
CDN Correct answer.
VPC

Explanation

A CDN caches content at edge nodes close to users, reducing latency and origin load. VPC is a network boundary, NAS is shared file storage, and Cloud DB is a managed database service.

Question 19NAVER Cloud Platform Fundamentals and Architecture

A database must be highly available across Zones with automatic failover. Which architectural pattern best supports this on NAVER Cloud Platform?

A database running on a local disk of one web server.
A primary database in one Zone and a standby replica in another Zone with automatic failover. Correct answer.
A single database instance in one Zone with daily backups.
A read-only database in a single Zone with no replica.

Explanation

Cross-zone primary and standby replicas allow the service to promote the standby when the primary zone fails, preserving availability. A single instance or a lone read-only node leaves a zone-level single point of failure, and backups restore data but do not provide automatic failover.

Question 20NAVER Cloud Platform Fundamentals and Architecture

Which statement correctly describes how billing and cost attribution work in NAVER Cloud Platform?

Costs are attributed only to the Region's default project.
Costs are attributed to the Zone where the resource was created.
Costs are attributed to the security group attached to a resource.
Costs are attributed to the account, and services consumed by resources in that account are billed there. Correct answer.

Explanation

Billing is organized at the account level, so resource consumption within an account rolls up to that account's charges. Zones, projects, and security groups are placement or policy constructs and are not billing entities.

Question 21NAVER Cloud Platform Fundamentals and Architecture

A team wants to monitor CPU, disk, and network metrics for its servers and receive alerts when thresholds are exceeded. Which NAVER Cloud Platform capability applies?

DNS record sets
Cloud monitoring with metric-based alarms Correct answer.
Security group rules
Object Storage lifecycle rules

Explanation

Monitoring collects resource metrics and evaluates alarm rules to notify operators when thresholds are crossed. Lifecycle rules manage object retention, DNS records resolve names, and security group rules filter traffic, none of which provide metric alerting.

Question 22NAVER Cloud Platform Fundamentals and Architecture

An architect is told that a workload must survive the loss of an entire Region. Which approach is required?

Deploy across at least two Regions with data replication and traffic routing. Correct answer.
Deploy across multiple Zones within one Region.
Deploy all resources into one Zone with auto-scaling.
Rely on daily snapshots stored in the same Region.

Explanation

Region-level failure tolerance requires resources and replicated data in more than one Region, with routing that can shift traffic. Multi-zone deployment only survives a zone failure, and same-region snapshots are lost with the region.

Question 23NAVER Cloud Platform Fundamentals and Architecture

Which NAVER Cloud Platform concept allows logically separating environments such as development and production while sharing the same account-level billing?

Separate CDN distributions per environment
Separate load balancer listeners per environment
Separate Zones per environment
Separate VPCs per environment Correct answer.

Explanation

Creating a separate VPC for each environment provides network isolation while both remain under the same account and billing. Zones are physical locations, and listeners or CDN distributions do not isolate networks.

Question 24NAVER Cloud Platform Fundamentals and Architecture

A company wants to reduce storage cost for data that is rarely accessed but must be retained for years. Which NAVER Cloud Platform option is most suitable?

Archive Storage for long-term retention Correct answer.
Block Storage volumes kept attached
NAS mounted on production servers
A CDN cache layer

Explanation

Archive Storage is optimized for infrequently accessed data retained over long periods at lower cost. Attached block volumes, active NAS mounts, and CDN caches are priced and designed for active use rather than archival retention.

Question 25NAVER Cloud Platform Fundamentals and Architecture

Which practice best follows the principle of least privilege when configuring NAVER Cloud Platform access for an automated deployment pipeline?

Grant every permission to all sub-accounts to prevent failures.
Reuse a departed employee's credentials to avoid reconfiguration.
Create a dedicated sub-account limited to the deployment APIs it needs. Correct answer.
Grant the pipeline the main account credentials for simplicity.

Explanation

A dedicated sub-account scoped to only the required deployment APIs limits the impact of a compromised pipeline credential. Using main account credentials, stale identities, or blanket permissions violates least privilege.

Question 26NAVER Cloud Platform Fundamentals and Architecture

A team wants to deploy a relational database on NAVER Cloud Platform and needs the database to be resilient to the failure of a single physical data center. Which deployment approach should the team choose?

Deploy the database across multiple Zones within the same Region with synchronous replication and automatic failover. Correct answer.
Deploy the database across multiple Regions with asynchronous replication and manual failover.
Deploy the database in a single Zone and replicate backups to Object Storage in another Region.
Deploy the database in a single Zone and rely on automated snapshots for recovery.

Explanation

NAVER Cloud Platform Regions contain multiple isolated Zones, and placing resources in multiple Zones within a Region protects against the loss of one data center while keeping latency low. Synchronous replication with automatic failover ensures the database remains available without manual intervention. Cross-Region replication is for disaster recovery and does not provide automatic failover within the Region.

Question 27NAVER Cloud Platform Fundamentals and Architecture

Which NAVER Cloud Platform component is responsible for distributing incoming traffic across multiple server instances and performing health checks to remove unhealthy instances from rotation?

NAT Gateway
Security Group
Load Balancer Correct answer.
VPC Peering

Explanation

A Load Balancer accepts client traffic and distributes it across a pool of backend servers while monitoring their health, so failed instances are excluded. NAT Gateway provides outbound internet access for private subnets, VPC Peering connects VPCs, and Security Groups filter traffic at the instance level.

Question 28NAVER Cloud Platform Fundamentals and Architecture

A company is designing a new VPC on NAVER Cloud Platform and must decide how to allocate IP addresses to subnets. What is the primary factor that determines the range of IP addresses available to a subnet?

The number of servers that will be launched in the subnet.
The CIDR block assigned to the VPC and the subnet mask chosen for the subnet. Correct answer.
The Region in which the VPC is created.
The load balancer configuration attached to the subnet.

Explanation

In NAVER Cloud Platform, a VPC is defined by an IPv4 CIDR block, and each subnet is carved from that block with its own CIDR prefix. The subnet mask determines how many addresses the subnet can allocate, independent of how many servers are actually launched. Region and load balancer settings do not change the address range of a subnet.

Question 29NAVER Cloud Platform Fundamentals and Architecture

An application running on a NAVER Cloud Platform server must call another NAVER Cloud Platform API. The security team requires that no long-lived credentials be stored on the server. Which approach best meets this requirement?

Embed the credentials in the application source code and compile it before deployment.
Store the access key and secret key in a configuration file on the server with restricted file permissions.
Assign a service account role to the server so the application obtains temporary credentials from the instance metadata service. Correct answer.
Create a sub-account for each server and distribute its password to the application through an environment variable.

Explanation

NAVER Cloud Platform supports assigning service account roles to server instances, allowing applications to obtain temporary credentials from the metadata service. This avoids storing long-lived secrets on the server and supports automatic rotation. Configuration files, source code, and environment variables all persist credentials that could be leaked.

Question 30NAVER Cloud Platform Fundamentals and Architecture

A solutions architect is comparing NAVER Cloud Platform storage services for a workload that requires a POSIX-compliant shared file system mounted concurrently by many servers. Which statement correctly identifies the appropriate service and its characteristic?

Block Storage provides a shared file system that multiple servers can mount simultaneously.
NAS provides a shared file system that multiple servers can mount concurrently using standard file protocols. Correct answer.
Archive Storage provides a low-latency POSIX file system for active workloads.
Object Storage provides a POSIX-compliant file system that can be mounted by multiple servers.

Explanation

NAS (Network Attached Storage) in NAVER Cloud Platform offers a shared file system that can be mounted by multiple servers at the same time using standard file protocols such as NFS. Object Storage is accessed via HTTP APIs, Block Storage is attached to a single server, and Archive Storage is for long-term retention with slower access.

Question 31Compute (Server, Kubernetes Service, Container Registry)

Which NAVER Cloud Platform service is used to store, version, and pull container images that are then deployed to Kubernetes Service clusters?

File Storage
Container Registry Correct answer.
Object Storage
Load Balancer

Explanation

Container Registry is the dedicated image repository service on NAVER Cloud Platform, providing image push and pull with version tags and vulnerability scanning integration. Object Storage and File Storage hold general data, not container image manifests. Load Balancer distributes traffic and does not store images.

Question 32Compute (Server, Kubernetes Service, Container Registry)

In NAVER Cloud Platform, what is the fundamental unit that a Kubernetes Service cluster schedules and runs workloads on?

A worker node Correct answer.
A registry namespace
A load balancer rule
A container image tag

Explanation

A Kubernetes Service cluster consists of a control plane and worker nodes, and pods are scheduled onto worker nodes that provide the compute and memory. Image tags and registry namespaces only identify stored images, and load balancer rules route traffic rather than run workloads.

Question 33Compute (Server, Kubernetes Service, Container Registry)

You must run a stateless web front end that can be scaled out and rolled back quickly, and you want the platform to manage the container orchestration control plane. Which NAVER Cloud Platform offering fits best?

Kubernetes Service Correct answer.
Cloud DB for MySQL
Global CDN
Bare Metal Server with manual container scripts

Explanation

Kubernetes Service provides a managed control plane and node pools, so you can scale replicas and roll back deployments declaratively. Bare Metal Server would require you to operate the orchestration layer yourself. Cloud DB and CDN are data and delivery services, not container orchestration.

Question 34Compute (Server, Kubernetes Service, Container Registry)

Which statement correctly describes the relationship between a container image and a running container?

A container is the immutable template and an image is its runtime copy.
A container must be converted into an image before it can start.
An image and a container are the same object viewed through different CLIs.
An image is a read-only template, and a container is a runnable instance created from it. Correct answer.

Explanation

An image is an immutable, layered template containing the application and its dependencies. A container is a running (or stopped) instance created from that image, with its own writable layer. Images are never runtime copies of containers, and containers do not need conversion to start.

Question 35Compute (Server, Kubernetes Service, Container Registry)

What does a Server (VM) instance in NAVER Cloud Platform require before it can be reached over the internet on a web port?

A Kubernetes namespace
An assigned public IP or load balancer plus an ACG rule allowing the port Correct answer.
A container registry repository
A CDN distribution

Explanation

Reachability requires both an address path (public IP or load balancer) and a security rule. Access Control Groups (ACGs) act as virtual firewalls and must permit the inbound port. Registry repositories, Kubernetes namespaces, and CDN distributions do not open ports on a VM.

Question 36Compute (Server, Kubernetes Service, Container Registry)

Which NAVER Cloud Platform capability lets you increase the CPU and memory of an existing Server instance without rebuilding the application stack?

Deleting and recreating the ACG
Re-tagging the container image
Enabling autoscaling in Kubernetes
Changing the server specification (scale-up) Correct answer.

Explanation

Changing a server's specification performs a scale-up or scale-down of vCPU and memory while preserving the installed software and data. ACG changes only affect firewall behavior, image tags do not alter compute, and Kubernetes autoscaling applies to pods rather than standalone Server instances.

Question 37Compute (Server, Kubernetes Service, Container Registry)

A team wants a private registry so that only their Kubernetes Service cluster can pull images. Which combination is the most appropriate?

A private Container Registry repository plus an image pull secret configured in the cluster Correct answer.
Storing images in Object Storage and referencing the bucket URL in the pod spec
A public registry with anonymous pull and no authentication
Publishing images to a public Git repository and cloning them at pod start

Explanation

A private registry restricts access, and the cluster authenticates with credentials supplied through an image pull secret. Anonymous public pulls defeat the privacy goal, and object storage or Git repositories are not OCI registries that the kubelet can pull from.

Question 38Compute (Server, Kubernetes Service, Container Registry)

In Kubernetes Service, what is the purpose of a node pool?

To store persistent volume claims for stateful workloads
To group worker nodes of the same specification so they can be scaled and upgraded together Correct answer.
To assign external IP addresses to individual pods
To define the DNS name of the cluster API endpoint

Explanation

A node pool is a set of worker nodes sharing a specification and configuration, managed as a unit for scaling and upgrades. It does not define the API endpoint, hold persistent volumes, or assign pod IPs. Those concerns belong to cluster endpoints, storage classes, and the CNI respectively.

Question 39Compute (Server, Kubernetes Service, Container Registry)

A Deployment in Kubernetes Service is configured with three replicas, and one pod crashes. What does the controller do?

It deletes the Deployment and requires manual recreation.
It promotes the failed pod to a DaemonSet.
It stops the remaining pods to keep the state consistent.
It creates a replacement pod to restore the desired replica count. Correct answer.

Explanation

A Deployment maintains the declared desired state, so the ReplicaSet controller observes that only two of three pods are running and creates a new pod. It does not scale down the healthy pods, convert workloads, or require manual intervention for a single pod failure.

Question 40Compute (Server, Kubernetes Service, Container Registry)

Which workload controller is the correct choice for running exactly one logging agent pod on every worker node of a Kubernetes Service cluster?

CronJob
Job
DaemonSet Correct answer.
Deployment with one replica

Explanation

A DaemonSet ensures that a copy of a pod runs on every eligible node, which is the standard pattern for node-level agents such as log or metric collectors. A single-replica Deployment runs on one node only, while CronJob and Job are for scheduled or one-off batch tasks.

Question 41Compute (Server, Kubernetes Service, Container Registry)

Why should a Kubernetes Service pod read configuration from a ConfigMap or Secret rather than from values baked into the image?

Because the same image can then be reused across environments while configuration changes independently Correct answer.
Because ConfigMaps and Secrets increase the CPU limit of the pod
Because the registry rejects images that contain environment variables
Because images cannot store text files at all

Explanation

Separating configuration from the image keeps the image immutable and portable, so the same artifact can run in development and production with different settings injected at runtime. Images can contain files, ConfigMaps do not raise CPU limits, and registries accept images containing environment variables.

Question 42Compute (Server, Kubernetes Service, Container Registry)

Which NAVER Cloud Platform Server feature helps distribute traffic across multiple backend instances and perform health checks?

Load Balancer Correct answer.
Init Script
Container Registry
ACG

Explanation

Load Balancer forwards client traffic to registered backend servers and removes unhealthy targets based on health checks. ACGs filter traffic, Container Registry stores images, and Init Script automates first-boot configuration.

Question 43Compute (Server, Kubernetes Service, Container Registry)

What is the primary purpose of a persistent volume claim in Kubernetes Service?

To cache container images on the control plane
To request storage with specific size and access characteristics that pods can mount Correct answer.
To reserve a static public IP for the cluster
To define the maximum number of pods per node

Explanation

A persistent volume claim expresses a storage request, and the cluster binds it to a volume that satisfies the requested capacity and access mode. Pods mount the claim to retain data beyond pod lifetime. Public IPs, pod density limits, and image caching are unrelated concerns.

Question 44Compute (Server, Kubernetes Service, Container Registry)

An administrator needs to restrict which users can create and modify resources in a Kubernetes Service cluster. Which mechanism is appropriate?

ACG rules applied to worker nodes
Container Registry image tags
Role-based access control with roles and role bindings Correct answer.
Init Script on the control plane

Explanation

Kubernetes RBAC grants permissions to users and service accounts through roles and bindings scoped to a namespace or the whole cluster. ACGs govern network traffic, image tags are labels, and init scripts configure servers at boot rather than authorizing API actions.

Question 45Compute (Server, Kubernetes Service, Container Registry)

You want to roll out a new version of an application on Kubernetes Service with zero downtime and the ability to revert immediately. Which approach should you use?

Change the node pool specification to force a restart
Delete all pods and let the ReplicaSet recreate them with the new image
Edit the running container's files in place with a shell
Perform a rolling update of the Deployment and keep the previous revision for rollback Correct answer.

Explanation

A Deployment rolling update gradually replaces pods while respecting availability settings, and revision history enables a rollback command. Deleting all pods causes downtime, editing containers in place is not reproducible, and resizing node pools is unrelated to application versioning.

Question 46Compute (Server, Kubernetes Service, Container Registry)

Which statement about Container Registry image tags is accurate?

Tags are automatically deleted when a pod pulls the image.
A tag permanently identifies one immutable image and cannot be reused.
Tags determine the CPU request of pods that use the image.
A tag is a mutable pointer, so pushing the same tag again replaces what that tag references. Correct answer.

Explanation

Tags are human-readable pointers that can be reassigned, so pushing an existing tag updates it to the new digest. This is why production deployments often pin images by digest. Tags are not deleted by pulls and have no bearing on resource requests.

Question 47Compute (Server, Kubernetes Service, Container Registry)

A pod in Kubernetes Service stays in Pending state and the event log reports insufficient CPU on all nodes. What is the most direct remedy?

Add a new namespace
Lower the pod's CPU request or add capacity to the node pool Correct answer.
Convert the Deployment into a CronJob
Change the image tag to latest

Explanation

Pending with insufficient CPU means the scheduler cannot find a node whose allocatable resources satisfy the pod request. Reducing the request or scaling the node pool provides a feasible placement. Image tags, namespaces, and workload kind do not create CPU capacity.

Question 48Compute (Server, Kubernetes Service, Container Registry)

In Kubernetes Service, how does a Service of type ClusterIP make a set of pods reachable to other pods?

By writing the pod IPs into a ConfigMap that clients read
By giving each pod a public IP address
By providing a stable virtual IP and DNS name that load-balance to the selected pods Correct answer.
By mounting the pod network into a persistent volume

Explanation

A ClusterIP Service allocates a stable virtual address and DNS name, and kube-proxy programs forwarding so traffic is distributed across pods matching the selector. Pods do not get public IPs for this purpose, and client-side ConfigMap lookups or volume mounts are not how Service discovery works.

Question 49Compute (Server, Kubernetes Service, Container Registry)

What distinguishes a StatefulSet from a Deployment in Kubernetes Service?

StatefulSet pods get stable identities and ordered, per-pod persistent storage. Correct answer.
StatefulSet always runs exactly one pod.
StatefulSet ignores the desired replica count.
StatefulSet pods cannot use persistent volumes at all.

Explanation

StatefulSet provides stable network identities, ordered creation and scaling, and persistent volume claims that remain bound to specific pod ordinals, which suits databases and clustered systems. It does honor replica counts and is designed around persistent storage rather than excluding it.

Question 50Compute (Server, Kubernetes Service, Container Registry)

An application image built on a general-purpose base is several gigabytes and pod start-up is slow. Which change most effectively reduces image size and pull time?

Increase the pod CPU request
Add more layers that each install build tools
Push the image with additional tags
Use a minimal base image and a multi-stage build that copies only runtime artifacts Correct answer.

Explanation

A minimal base plus multi-stage build keeps compilers and build dependencies out of the final image, shrinking layers and speeding pulls. Adding build tools increases size, extra tags do not change content, and more CPU does not reduce download time.