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 concept describes a logical boundary that groups resources and provides a unit for access control and billing separation?
- Project
- Region
- Zone
- Account Correct answer.
Explanation
NAVER Cloud Platform organizes resources under an account, which acts as the top-level logical and billing boundary. Access permissions and resource ownership are managed within this account scope, and sub-accounts can be delegated through identity management. Regions and zones describe physical placement, not ownership.
Question 2NAVER Cloud Platform Fundamentals and Architecture
A team needs to deploy an application so that it survives the failure of a single data center while remaining in one country. Which NAVER Cloud Platform construct should they distribute resources across?
- Multiple projects
- Multiple availability zones within a region Correct answer.
- Multiple sub-accounts
- Multiple accounts
Explanation
Availability zones are isolated data-center units inside a single region, so spreading resources across zones protects against one data-center failure while keeping data in the same country. Accounts, projects, and sub-accounts are logical identity constructs and provide no physical fault isolation.
Question 3NAVER Cloud Platform Fundamentals and Architecture
Which statement best describes the relationship between a region and an availability zone in NAVER Cloud Platform?
- An availability zone contains multiple regions for billing purposes.
- An availability zone spans several regions to provide global redundancy.
- A region and an availability zone are synonyms used interchangeably.
- A region contains multiple availability zones, and a zone belongs to exactly one region. Correct answer.
Explanation
The hierarchy is region first, then availability zone: each region holds several isolated zones, and a given zone is tied to one region. This containment drives latency, data-residency, and failover decisions. Zones never span regions, and the two terms are not interchangeable.
Question 4NAVER Cloud Platform Fundamentals and Architecture
A company wants to reach NAVER Cloud Platform services over a private connection instead of the public internet. Which networking capability addresses this requirement?
- A public IP address on each server
- A content delivery network distribution
- A dedicated private connectivity service to the platform Correct answer.
- A load balancer with SSL termination
Explanation
NAVER Cloud Platform offers a dedicated private connectivity option that links an on-premises or customer network to the platform without traversing the public internet. Public IPs, CDN, and load balancers all operate over or expose public endpoints and do not provide a private path.
Question 5NAVER Cloud Platform Fundamentals and Architecture
Which NAVER Cloud Platform service is the primary choice for creating isolated virtual networks and controlling inbound and outbound traffic rules?
- Virtual Private Cloud Correct answer.
- Cloud Log Analytics
- Object Storage
- Key Management Service
Explanation
Virtual Private Cloud lets you define subnets, route tables, and security rules so resources communicate in an isolated network. Object Storage holds data, log analytics collects telemetry, and key management handles cryptographic keys; none of them define network topology.
Question 6NAVER Cloud Platform Fundamentals and Architecture
An architect must ensure that a compute instance can be reached from the internet on port 443 only. Which combination of controls is most appropriate?
- Attach an object storage bucket to the instance and allow all ports.
- Assign a private IP and disable all security groups.
- Place the instance in a subnet with no route table and allow all ports.
- Assign a public IP and allow only port 443 in the security group or access control rules. Correct answer.
Explanation
Internet reachability requires a public IP, and restricting inbound traffic to port 443 is done through security group or access control rules. Leaving all ports open or removing rules defeats the requirement, and a subnet without routing cannot reach the internet at all.
Question 7NAVER Cloud Platform Fundamentals and Architecture
What is the main purpose of a load balancer in a NAVER Cloud Platform architecture?
- To replicate databases across regions
- To encrypt data at rest in block storage
- To schedule periodic batch jobs
- To distribute incoming traffic across multiple backend servers Correct answer.
Explanation
A load balancer accepts client traffic and spreads it across healthy backend targets, improving availability and scalability. Encryption at rest, job scheduling, and cross-region database replication are handled by other services, not by the load balancer.
Question 8NAVER Cloud Platform Fundamentals and Architecture
An application running on a NAVER Cloud Platform server needs to read and write files in a highly durable, HTTP-accessible store. Which service fits best?
- Object Storage Correct answer.
- Block Storage
- Local instance disk
- Network file share mounted as root
Explanation
Object Storage provides durable, HTTP-accessible storage for objects and is well suited to application file access over APIs. Block Storage and local disks are attached to instances and are not HTTP-accessible shared stores, and mounting a network share as root is neither a storage-service choice nor a safe design.
Question 9NAVER Cloud Platform Fundamentals and Architecture
Which identity feature allows an organization to grant different permission sets to different employees under one NAVER Cloud Platform account?
- Sub-accounts with assigned policies Correct answer.
- A single shared root credential
- Static access keys embedded in code
- Anonymous public access
Explanation
Sub-accounts let an organization create separate identities under one account and attach policies that scope what each identity may do. Sharing a root credential, embedding static keys, or allowing anonymous access removes accountability and violates least privilege.
Question 10NAVER Cloud Platform Fundamentals and Architecture
Why does NAVER Cloud Platform recommend using multiple availability zones for a production database tier?
- To lower object storage durability
- To keep a standby replica available if one zone fails Correct answer.
- To eliminate the need for backups
- To reduce the number of sub-accounts required
Explanation
Placing a standby in a different zone lets the database fail over when one zone becomes unavailable, improving availability. Multi-zone placement does not remove the need for backups, does not affect identity design, and does not change storage durability guarantees.
Question 11NAVER Cloud Platform Fundamentals and Architecture
A workload must keep data within a specific country for regulatory reasons. Which NAVER Cloud Platform decision most directly enforces this?
- Enabling a CDN distribution
- Choosing a larger instance type
- Choosing a region located in that country Correct answer.
- Creating additional sub-accounts
Explanation
Data residency is controlled by the region in which resources are provisioned, because each region corresponds to physical facilities in a location. Instance size, CDN, and identity structure do not determine where data is stored.
Question 12NAVER Cloud Platform Fundamentals and Architecture
Which NAVER Cloud Platform service is designed to centrally manage encryption keys used by other services?
- Key Management Service Correct answer.
- Load Balancer
- Virtual Private Cloud
- Cloud Log Analytics
Explanation
Key Management Service stores and controls cryptographic keys so other services can encrypt data without exposing key material. Log analytics, VPC, and load balancers handle telemetry, networking, and traffic distribution respectively, and none of them manage encryption keys.
Question 13NAVER Cloud Platform Fundamentals and Architecture
An operations team wants to receive alerts when CPU utilization on production servers stays above a threshold. Which platform capability should they use?
- Security group outbound rules
- Object storage lifecycle rules
- Monitoring with metric-based alarm rules Correct answer.
- Subnet route table entries
Explanation
Monitoring collects metrics such as CPU utilization and can trigger alarms when a rule threshold is crossed. Lifecycle rules manage stored objects, route tables direct packets, and security group rules filter traffic; none of them generate threshold alerts.
Question 14NAVER Cloud Platform Fundamentals and Architecture
Which statement about the shared responsibility model on NAVER Cloud Platform is accurate?
- All security duties belong to the provider regardless of service type.
- The customer is responsible for physical data-center security.
- The provider secures the physical facilities, while the customer secures guest operating systems and their configurations. Correct answer.
- The provider configures the customer's application-level access rules.
Explanation
Under the shared responsibility model the provider secures the underlying infrastructure such as facilities and hardware, while the customer is responsible for what they deploy, including guest OS patching and configuration. Physical security and application-level authorization remain customer or provider duties respectively, not reversed.
Question 15NAVER Cloud Platform Fundamentals and Architecture
A team wants to run containerized microservices without managing the underlying cluster nodes. Which NAVER Cloud Platform offering best matches this need?
- A DNS record set
- A managed Kubernetes service Correct answer.
- A block storage volume
- A bare-metal server
Explanation
A managed Kubernetes service runs the control plane and node lifecycle for you, so teams deploy containerized workloads without operating clusters themselves. Bare-metal servers, block volumes, and DNS records do not provide orchestrated container hosting.
Question 16NAVER Cloud Platform Fundamentals and Architecture
Which characteristic distinguishes serverless functions from always-on virtual server instances on NAVER Cloud Platform?
- Functions cannot be triggered by HTTP requests.
- Functions store persistent state on local disk between invocations.
- Functions require a fixed number of reserved instances to be running at all times.
- Functions execute in response to events and scale automatically without pre-provisioned servers. Correct answer.
Explanation
Serverless functions are event-driven: the platform provisions capacity per invocation and scales with demand, so no server is kept running idle. They can be invoked over HTTP and are stateless by design, so local disk state does not persist between calls.
Question 17NAVER Cloud Platform Fundamentals and Architecture
What is the primary role of a content delivery network in a NAVER Cloud Platform web architecture?
- Storing database transaction logs
- Caching static content at edge locations closer to users Correct answer.
- Assigning private IP addresses to instances
- Rotating encryption keys
Explanation
A CDN caches content at edge nodes near end users, reducing latency and origin load for static assets. Transaction log storage, private IP assignment, and key rotation are handled by storage, networking, and key management services respectively.
Question 18NAVER Cloud Platform Fundamentals and Architecture
An architect is designing a three-tier web application on NAVER Cloud Platform. Which placement best isolates the database tier from direct internet access?
- Assign the database a public IP and rely on the database password alone.
- Place the database in a public subnet with a public IP and allow all inbound ports.
- Place the database in a private subnet with no public IP and restrict access to the application tier. Correct answer.
- Attach a CDN distribution directly to the database.
Explanation
Keeping the database in a private subnet without a public IP and limiting inbound rules to the application tier removes direct internet exposure. Public IPs, open ports, and password-only protection leave the database reachable and violate least privilege.
Question 19NAVER Cloud Platform Fundamentals and Architecture
Which NAVER Cloud Platform capability supports automated backup and point-in-time recovery for a managed database?
- Object storage lifecycle transitions
- Database backup and recovery features of the managed database service Correct answer.
- Security group logging
- DNS failover records
Explanation
Managed database services provide scheduled backups and point-in-time recovery so data can be restored to a prior moment. Lifecycle transitions, security group logs, and DNS failover records address storage tiering, traffic auditing, and name resolution rather than database recovery.
Question 20NAVER Cloud Platform Fundamentals and Architecture
A company must prove that only approved changes were made to its cloud environment. Which NAVER Cloud Platform practice best supports this?
- Enabling activity logging that records API calls per identity Correct answer.
- Disabling all audit logs to reduce storage cost
- Granting every sub-account administrator policy
- Using a single shared credential for all engineers
Explanation
Activity logging records which identity performed which API action, creating the audit trail needed to demonstrate controlled change. Suppressing logs, sharing credentials, or over-granting policies destroys attribution and weakens governance.
Question 21NAVER Cloud Platform Fundamentals and Architecture
Which scenario best justifies choosing a multi-region architecture on NAVER Cloud Platform?
- The team wants to reduce the number of security groups in use.
- The team wants to simplify identity policy management.
- The application must remain available even if an entire region becomes unavailable. Correct answer.
- The application needs a larger block storage volume per server.
Explanation
Multi-region designs protect against the loss of a whole region, which is a larger failure domain than a single zone. Security group count, volume size, and identity policy complexity are unrelated to region-level resilience and are addressed by other design choices.
Question 22NAVER Cloud Platform Fundamentals and Architecture
What does an auto scaling policy do for a compute fleet on NAVER Cloud Platform?
- It archives old logs to object storage.
- It assigns domain names to load balancers.
- It encrypts traffic between instances.
- It adjusts the number of running instances based on defined metrics or schedules. Correct answer.
Explanation
Auto scaling changes instance count according to metric thresholds or schedules so capacity tracks demand. Traffic encryption, DNS naming, and log archival are handled by other services and are not scaling functions.
Question 23NAVER Cloud Platform Fundamentals and Architecture
Which NAVER Cloud Platform service would you use to translate a domain name into the IP address of a load balancer?
- DNS service Correct answer.
- Object Storage
- Cloud Log Analytics
- Key Management Service
Explanation
A DNS service maps names to addresses, including the endpoint of a load balancer, so clients can resolve a friendly hostname. Object storage, key management, and log analytics do not provide name resolution.
Question 24NAVER Cloud Platform Fundamentals and Architecture
An application experiences sudden traffic spikes and the team wants to avoid manual capacity changes while controlling cost. Which combination is most appropriate?
- Disabling health checks on all backends
- A single oversized instance with no monitoring
- Auto scaling driven by metrics combined with a load balancer distributing traffic Correct answer.
- Manual instance creation each time traffic rises
Explanation
Metric-driven auto scaling adds and removes capacity as demand changes, and a load balancer spreads traffic across the current fleet. A single unmonitored instance cannot absorb spikes, manual provisioning is slow, and disabling health checks lets traffic reach failed backends.
Question 25NAVER Cloud Platform Fundamentals and Architecture
Which statement correctly describes how a VPC subnet relates to an availability zone?
- A subnet is created within a single availability zone of the VPC's region. Correct answer.
- A subnet can contain only object storage buckets.
- A subnet is a billing construct unrelated to networking.
- A subnet automatically spans every region in the account.
Explanation
A subnet is scoped to one availability zone inside the VPC's region, which is why multi-zone designs create separate subnets per zone. Subnets do not span regions, are networking constructs rather than billing units, and host network interfaces rather than storage buckets.
Question 26NAVER Cloud Platform Fundamentals and Architecture
On NAVER Cloud Platform, which component provides the logically isolated virtual network boundary in which subnets and resources such as servers are created?
- The Global CDN
- The VPC Correct answer.
- The Access Control Group
- The Placement Group
Explanation
A VPC (Virtual Private Cloud) is the logical network isolation unit on NAVER Cloud Platform; subnets, Access Control Groups, and servers are all defined inside it. Without a VPC, no subnet or compute resource can be launched.
Question 27NAVER Cloud Platform Fundamentals and Architecture
A team is deploying a NAVER Cloud Platform server and wants inbound traffic restricted so that only port 22 from the office IP range is allowed. Which object should they configure?
- A DNS record set
- A NAT Gateway rule
- A CDN origin policy
- An Access Control Group rule Correct answer.
Explanation
Access Control Groups act as virtual firewalls attached to servers, and their rules define which source IP ranges and ports may reach the server. Restricting inbound SSH to a known CIDR is a standard ACG rule.
Question 28NAVER Cloud Platform Fundamentals and Architecture
Which statement best describes how NAVER Cloud Platform organizes regions and zones for resource deployment?
- A region is a single data center, and zones are logical tags applied to servers after creation.
- Each zone contains multiple regions, and a server is placed in a zone that spans all regions.
- Regions and zones are interchangeable terms used only for billing purposes.
- A region contains multiple zones, and a server is created in one zone within a chosen region. Correct answer.
Explanation
NAVER Cloud Platform groups its infrastructure into regions, and each region contains multiple zones that correspond to distinct physical facilities. When creating a server you select a region and a zone, which determines the physical location of that instance.
Question 29NAVER Cloud Platform Fundamentals and Architecture
An architect needs private servers that have no public IP address but still must download software patches from the internet. Which NAVER Cloud Platform design achieves this?
- Create the servers in a different region where public IPs are not offered.
- Assign a public IP to each server and rely on Access Control Group rules to block inbound traffic.
- Put the servers in a private subnet and route outbound traffic through a NAT Gateway. Correct answer.
- Place the servers in a public subnet and attach a load balancer to them.
Explanation
A NAT Gateway lets instances in a private subnet initiate outbound connections to the internet while remaining unreachable from inbound internet traffic. This is the standard pattern for patch downloads on servers that must not expose public addresses.
Question 30NAVER Cloud Platform Fundamentals and Architecture
A company wants a managed relational database on NAVER Cloud Platform and needs to know which operational task remains the customer's responsibility.
- Maintaining the physical power and cooling of the data center
- Replacing failed disks in the storage array that holds the database
- Installing database engine patches on the underlying host operating system
- Designing schemas, indexes, and query logic for the application's data Correct answer.
Explanation
With a managed database service, the provider handles the host, storage, patching, and facility concerns, while the customer still owns logical design work such as schema, indexing, and query tuning. Those decisions directly affect performance and correctness and cannot be delegated to the platform.
Question 31NAVER Cloud Platform Fundamentals and Architecture
A web tier must remain available even if one zone in its region becomes unavailable. Which deployment approach on NAVER Cloud Platform best meets this requirement with minimal manual intervention?
- Deploy web servers across multiple zones in the region and place them behind a load balancer. Correct answer.
- Deploy web servers in one zone and add a standby server in the same zone.
- Deploy all web servers in a single zone and take periodic snapshots of their disks.
- Deploy web servers in one zone and increase the server specification to absorb failures.
Explanation
Spreading instances across zones removes the single point of physical failure, and a load balancer distributes traffic only to healthy targets so the surviving zone continues serving requests. Snapshots or larger specifications in one zone cannot compensate for the loss of that zone.
Question 32NAVER Cloud Platform Fundamentals and Architecture
A developer needs object storage on NAVER Cloud Platform and wants to control who can read a specific bucket without changing permissions for the whole account. Which approach fits?
- Disable authentication on the bucket so any caller can read it.
- Move the bucket to another region so the default permissions no longer apply.
- Use bucket and object policies or Access Control Group rules to grant scoped permissions to the required identities. Correct answer.
- Rely on the account's root credentials being shared with the requesting team.
Explanation
Object storage permissions can be scoped at the bucket or object level through policies that name the identities allowed to perform specific actions. This grants least-privilege access without broadening account-wide rights or sharing root credentials.
Question 33NAVER Cloud Platform Fundamentals and Architecture
An operations team wants a managed message queue so that a producer service and a consumer service can be decoupled and tolerate consumer downtime. Which NAVER Cloud Platform service category should they select?
- A container registry
- A domain name service
- A managed database service
- A message queue service Correct answer.
Explanation
A message queue buffers messages between producers and consumers so that consumers can process at their own pace and survive temporary outages without losing work. Decoupling asynchronously is precisely the role of a queue rather than a database or registry.
Question 34NAVER Cloud Platform Fundamentals and Architecture
A team wants to run a batch job on NAVER Cloud Platform that runs for a few minutes, scales automatically with demand, and incurs cost only while executing. Which platform capability matches this requirement?
- An always-on virtual server instance sized for peak load
- A dedicated load balancer with static IP addresses
- A serverless functions platform triggered by events or schedules Correct answer.
- A managed relational database with read replicas
Explanation
Serverless functions execute on demand in response to events or schedules, scale with invocation volume, and bill for actual execution rather than idle capacity. This matches short, bursty batch work better than provisioning servers for peak load.
Question 35NAVER Cloud Platform Fundamentals and Architecture
An architect must justify why a NAVER Cloud Platform design places the database in a private subnet while the web tier sits in a public subnet behind a load balancer. Which reasoning is most defensible?
- Placing the database in a private subnet removes the need to back it up.
- Private subnets offer higher network throughput than public subnets for database traffic.
- Keeping the database off the public internet reduces its attack surface while the load balancer exposes only the web tier. Correct answer.
- Public subnets cannot host more than one server, so the database must be placed elsewhere.
Explanation
Tier isolation limits exposure: only the load balancer and web tier accept internet traffic, while the database is reachable only from inside the VPC. This reduces the attack surface without changing throughput characteristics or backup obligations.
Question 36NAVER Cloud Platform Fundamentals and Architecture
A company runs a stateless API on NAVER Cloud Platform and expects unpredictable traffic. They want the fleet to grow and shrink automatically while keeping response times stable. Which combination of design decisions is most appropriate?
- A fixed fleet sized for the yearly peak, with manual intervention whenever traffic rises
- Auto scaling driven by a metric such as CPU utilization, with servers distributed across zones behind a load balancer Correct answer.
- A single large server in one zone with a scheduled restart each night
- A fleet that scales on a fixed calendar schedule only, ignoring actual load
Explanation
Metric-driven auto scaling adjusts capacity to observed demand, and distributing the fleet across zones behind a load balancer keeps latency stable while absorbing zone-level failures. Because the API is stateless, any instance can serve any request, which makes horizontal scaling safe.
Question 37Compute (Server, Container, and Auto Scaling)
In NAVER Cloud Platform, which server product provides a virtual machine where you select the operating system and specifications yourself and manage it directly?
- Cloud Functions
- Object Storage
- Global CDN
- Server (VM) Correct answer.
Explanation
The Server product is the classic IaaS virtual machine offering, letting you choose OS images, vCPU and memory specifications, and storage, then administer the guest OS yourself. The other products are serverless functions, storage, and content delivery services rather than general-purpose VMs.
Question 38Compute (Server, Container, and Auto Scaling)
When you create a Server instance in NAVER Cloud Platform, which item must be chosen to define the CPU and memory size of the instance?
- The server specification (vCPU/memory) Correct answer.
- The ACG rule set
- The public IP bandwidth
- The server image type
Explanation
The server specification determines the number of vCPUs and the amount of memory allocated to the instance. Images define the OS and software baseline, ACGs control network access, and bandwidth is a separate network configuration.
Question 39Compute (Server, Container, and Auto Scaling)
Which NAVER Cloud Platform capability lets you apply a predefined or custom script automatically when a Server instance is first booted?
- Snapshot schedule
- ACG rule
- Placement group
- Init script Correct answer.
Explanation
Init scripts run user-supplied shell commands during the initial boot of an instance, which is useful for installing packages or configuring services automatically. ACGs, placement groups, and snapshot schedules handle networking, physical placement, and backup respectively.
Question 40Compute (Server, Container, and Auto Scaling)
In NAVER Cloud Platform, what is the purpose of an Access Control Group (ACG) applied to a Server instance?
- To schedule automatic scaling of the instance count
- To select the operating system image at creation time
- To define inbound and outbound traffic rules acting as a virtual firewall Correct answer.
- To encrypt the instance's block storage volume
Explanation
An ACG is a virtual firewall whose rules specify allowed protocols, ports, and source or destination addresses for traffic reaching or leaving instances. It is separate from image selection, scaling policy, and storage encryption.
Question 41Compute (Server, Container, and Auto Scaling)
Which NAVER Cloud Platform service is designed to run containerized applications using Kubernetes while NAVER manages the control plane?
- Data Box
- Ncloud Kubernetes Service Correct answer.
- Server (VM)
- Cloud Functions
Explanation
Ncloud Kubernetes Service (NKS) provides a managed Kubernetes cluster in which the control plane is operated by NAVER Cloud Platform and customers manage worker node pools and workloads. It is distinct from plain VMs, serverless functions, and data transfer appliances.
Question 42Compute (Server, Container, and Auto Scaling)
In NAVER Cloud Platform Auto Scaling, what is a Launch Configuration used for?
- Listing the load balancer listener ports
- Storing the access keys used by the scaling policy
- Recording the CPU metrics that trigger scaling
- Defining the template of image, specification, and scripts used when scaling out new servers Correct answer.
Explanation
A Launch Configuration captures the server template, such as image, specification, ACG, and init script, that Auto Scaling uses whenever it creates additional instances. Metrics, credentials, and load balancer settings are configured elsewhere.
Question 43Compute (Server, Container, and Auto Scaling)
Which statement describes a container registry's role in a NAVER Cloud Platform container workflow?
- It terminates TLS for inbound web traffic
- It assigns public IP addresses to worker nodes
- It provisions the Kubernetes control plane
- It stores and distributes container images that clusters pull when deploying workloads Correct answer.
Explanation
A container registry is an image repository: you push built images and clusters pull them when starting pods. IP assignment, TLS termination, and control plane provisioning belong to networking, load balancing, and the managed Kubernetes service.
Question 44Compute (Server, Container, and Auto Scaling)
What does a server image in NAVER Cloud Platform primarily determine when a new Server instance is created?
- The number of vCPUs assigned
- The physical rack location of the host
- The monthly billing currency
- The operating system and preinstalled software baseline Correct answer.
Explanation
A server image is the template of the root volume, containing the operating system and any preinstalled packages, so it defines the software baseline of the instance. vCPU count comes from the specification, while billing and host placement are platform-managed.
Question 45Compute (Server, Container, and Auto Scaling)
A team wants Auto Scaling to add instances when average CPU utilization exceeds 70 percent for several minutes. Which configuration element expresses this condition?
- An ACG inbound rule
- A server snapshot
- A scaling policy with a metric-based trigger and threshold Correct answer.
- A Launch Configuration init script
Explanation
Auto Scaling reacts to triggers defined in a scaling policy, where you choose a metric such as CPU utilization, a comparison threshold, and an evaluation period. Init scripts, ACG rules, and snapshots do not evaluate metrics to change instance count.
Question 46Compute (Server, Container, and Auto Scaling)
You need a Server instance reachable from the internet on HTTP port 80 while blocking all other inbound ports. What must you configure?
- An outbound rule allowing TCP 80 only
- An init script that opens port 80 in the OS firewall only
- An ACG inbound rule allowing TCP 80 and no other inbound allowances Correct answer.
- A placement group spanning two zones
Explanation
Inbound reachability is governed by ACG inbound rules, so allowing TCP 80 and leaving other inbound ports closed achieves the goal. Outbound rules govern traffic leaving the instance, and an OS-level firewall alone does not override the ACG.
Question 47Compute (Server, Container, and Auto Scaling)
A workload must survive the loss of a single availability zone. Which Server deployment approach best meets this requirement?
- Attach additional block storage to a single instance
- Place all instances in one availability zone with a larger specification
- Enable a snapshot schedule on one instance
- Distribute instances across multiple availability zones behind a load balancer Correct answer.
Explanation
Spreading instances across availability zones removes a single zone as a point of failure, and a load balancer directs traffic to healthy instances. Larger specifications, extra storage, and snapshots do not provide zone-level redundancy.
Question 48Compute (Server, Container, and Auto Scaling)
An operator wants to change the instance specification used by an existing Auto Scaling group going forward. What is the appropriate action?
- Change the load balancer listener protocol
- Delete the scaling policy
- Create or update the Launch Configuration referenced by the group and apply it Correct answer.
- Edit the ACG rules of the running instances
Explanation
New instances created by scale-out take their template from the Launch Configuration, so updating that configuration changes the specification of future instances. ACG rules, listener protocols, and policy deletion do not alter instance specifications.
Question 49Compute (Server, Container, and Auto Scaling)
A developer needs a containerized web application with a stable DNS name and automatic restart of failed pods on managed Kubernetes. Which NAVER Cloud Platform combination fits best?
- Cloud Functions with an HTTP trigger
- Object Storage with a static website endpoint
- Ncloud Kubernetes Service with a Deployment and a Service of load balancer type Correct answer.
- A single Server instance running the container manually
Explanation
A Kubernetes Deployment maintains the desired number of pod replicas and restarts failed ones, while a load balancer Service exposes them under a stable endpoint. A manually run container on one VM lacks orchestration, and the other options are not container orchestration.
Question 50Compute (Server, Container, and Auto Scaling)
Why would an administrator place instances into a placement group in NAVER Cloud Platform?
- To attach a container registry to the instance
- To control how instances are distributed across physical hosts for availability or performance Correct answer.
- To reduce the number of vCPUs billed
- To assign a public IP address to each instance
Explanation
A placement group influences the physical placement of instances, which can be used to spread them for resilience or to co-locate them for low latency. It does not handle IP assignment, registry attachment, or billing of vCPUs.