CCNA Cloud Concepts Questions — Page 4 of 4

226

MCQmedium

A startup is migrating a web application to AWS. The application runs on Amazon EC2 instances that use a custom Amazon Machine Image (AMI) with the company's proprietary software. The security team needs to understand which security tasks the company must perform. Under the AWS Shared Responsibility Model, which of the following is the customer's responsibility?

A.Patching the hypervisor that hosts the EC2 instances

B.Configuring security groups to control inbound traffic to the instances

C.Physical security of the data center where the instances run

D.Maintaining the underlying network infrastructure

AnswerB

Configuring security groups is the customer's responsibility. Security groups act as virtual firewalls for EC2 instances, and customers define the rules for allowed traffic, making this a task the customer must perform.

Why this answer

Configuring security groups is a customer responsibility because security groups act as a virtual firewall for EC2 instances, controlling inbound and outbound traffic at the instance level. Under the AWS Shared Responsibility Model, the customer is responsible for configuring network access controls, while AWS manages the underlying infrastructure. This includes defining rules based on IP protocols, ports, and source/destination CIDR ranges.

Exam trap

The trap here is that candidates often confuse 'patching the hypervisor' (AWS responsibility) with 'patching the guest OS' (customer responsibility), leading them to incorrectly select Option A as a customer task.

How to eliminate wrong answers

Option A is wrong because patching the hypervisor is an AWS responsibility, as the hypervisor is part of the virtualization layer that AWS manages to isolate customer instances. Option C is wrong because physical security of the data center is entirely AWS's responsibility under the model, covering guards, access controls, and environmental systems. Option D is wrong because maintaining the underlying network infrastructure, including routers, switches, and cabling, is AWS's responsibility as part of the 'Security of the Cloud'.

Practice this question →

227

MCQeasy

A developer needs to launch a test server for a new application prototype. The developer logs into the AWS Management Console, selects an Amazon EC2 instance type, configures the security group, and starts the instance. The instance is running within two minutes, and the developer did not need to submit a formal request to the company's IT procurement team or wait for approval from a cloud administrator. Which essential characteristic of cloud computing does this scenario best demonstrate?

A.On-demand self-service

B.Broad network access

C.Resource pooling

D.Rapid elasticity

AnswerA

Correct. On-demand self-service means a user can provision computing capabilities as needed automatically without requiring human interaction with each service provider. The developer launched an EC2 instance directly via the console with no IT intervention, perfectly matching this characteristic.

Why this answer

The scenario demonstrates on-demand self-service because the developer was able to provision and launch an EC2 instance directly through the AWS Management Console without any human interaction with IT procurement or a cloud administrator. This characteristic, defined by NIST as a core pillar of cloud computing, allows users to unilaterally provision computing capabilities as needed automatically, which is exactly what happened when the instance was running within two minutes of the console action.

Exam trap

The trap here is that candidates often confuse 'on-demand self-service' with 'resource pooling' because both involve rapid provisioning, but the key differentiator is the absence of human interaction versus the multi-tenant sharing of underlying infrastructure.

How to eliminate wrong answers

Option B (Broad network access) is wrong because the scenario does not describe network connectivity from multiple heterogeneous client platforms (e.g., mobile phones, laptops, or workstations) or mention any specific protocols like HTTPS, SSH, or RDP being used to access the instance. Option C (Resource pooling) is wrong because the scenario does not illustrate the provider's computing resources being pooled to serve multiple consumers using a multi-tenant model, nor does it mention physical or virtual resources dynamically assigned and reassigned according to consumer demand.

Practice this question →

228

MCQmedium

A gaming company runs a multiplayer game backend on Amazon EC2 instances. The game experiences variable traffic patterns: low usage during weekday mornings and high usage during evenings and weekends. The company uses an Auto Scaling group to automatically add instances during peak hours and remove them during low traffic. The company is billed only for the compute capacity actually consumed during each hour. Which characteristic of cloud computing does this usage-based billing model best illustrate?

A.Rapid elasticity

B.Measured service

C.Resource pooling

D.On-demand self-service

AnswerB

Measured service is the correct characteristic. Cloud providers meter usage at a granular level (e.g., per hour or per GB) and bill customers only for what they consume. In this scenario, the company pays only for the compute capacity used each hour, which is a textbook example of measured service.

Why this answer

The usage-based billing model, where the company pays only for the compute capacity consumed each hour, is a direct example of measured service. This characteristic of cloud computing involves metering resource usage (e.g., CPU hours, data transfer) and charging based on that consumption, which is exactly what the Auto Scaling group enables by dynamically adjusting instance count and billing only for active hours.

Exam trap

The trap here is that candidates confuse the scaling behavior (rapid elasticity) with the billing model (measured service), but the question specifically asks which characteristic the usage-based billing model best illustrates, not the scaling mechanism.

How to eliminate wrong answers

Option A is wrong because rapid elasticity refers to the ability to quickly scale resources up or down in response to demand, which is demonstrated by the Auto Scaling group adding/removing instances, but it does not describe the billing model itself. Option C is wrong because resource pooling describes the provider's multi-tenant model where compute resources are shared across customers, not the per-hour billing mechanism. Option D is wrong because on-demand self-service allows users to provision resources without human interaction, which is a prerequisite for the scenario but not the billing characteristic illustrated by paying only for consumed capacity.

Practice this question →

229

MCQeasy

A startup runs an application on AWS and receives a monthly bill that charges exactly for the number of compute hours used, the gigabytes of data stored, and the gigabytes of data transferred. The company pays nothing for resources they did not use. Which cloud computing characteristic does this represent?

A.Measured service

B.Rapid elasticity

C.On-demand self-service

D.Resource pooling

AnswerA

Measured service is the cloud characteristic where resource usage is metered and customers are billed only for what they consume — compute hours, storage bytes, data transfer — with transparent reporting.

Why this answer

This scenario describes a pay-per-use model where costs directly correlate with actual consumption of compute hours, storage, and data transfer. Measured service is the cloud characteristic that enables this by automatically monitoring, controlling, and reporting resource usage, providing transparency for both the provider and consumer. AWS implements this through services like AWS CloudTrail and detailed billing reports, ensuring customers are charged only for what they consume.

Exam trap

The trap here is that candidates often confuse 'measured service' with 'on-demand self-service' because both involve user control, but measured service specifically focuses on the metering and billing aspect, not the provisioning mechanism.

How to eliminate wrong answers

Option B (Rapid elasticity) is wrong because it refers to the ability to scale resources up or down automatically in response to demand, not to the metering and billing of consumed resources. Option C (On-demand self-service) is wrong because it describes a user's ability to provision resources without human interaction, typically via a web console or API, not the usage-based billing model. Option D (Resource pooling) is wrong because it involves the provider's multi-tenant model where physical and virtual resources are dynamically assigned to multiple customers, which does not directly relate to charging only for used resources.

Practice this question →

230

MCQeasy

Which statement best describes the concept of 'infrastructure as code' (IaC) in the context of AWS?

A.Using the AWS Management Console to provision resources manually

B.Writing scripts to install software on EC2 instances

C.Defining and provisioning cloud resources using version-controlled configuration files

D.Backing up AWS resource configurations to Amazon S3

AnswerC

IaC treats infrastructure provisioning as a software engineering discipline — resources are defined in files, version-controlled in git, and applied through automated pipelines.

Why this answer

Option C is correct because Infrastructure as Code (IaC) is the practice of defining and managing cloud resources through machine-readable definition files (e.g., AWS CloudFormation templates or Terraform HCL) that are stored in version control. This allows for automated, repeatable, and consistent provisioning of AWS infrastructure, enabling change management, peer review, and rollback capabilities.

Exam trap

The trap here is confusing IaC with configuration management (e.g., installing software on instances) or manual provisioning, leading candidates to pick options that describe operational tasks rather than the core IaC practice of defining infrastructure in version-controlled files.

How to eliminate wrong answers

Option A is wrong because manually provisioning resources via the AWS Management Console is the opposite of IaC; it is a manual, error-prone process that lacks version control and repeatability. Option B is wrong because writing scripts to install software on EC2 instances is configuration management (e.g., using AWS Systems Manager or user data scripts), not IaC; IaC focuses on provisioning the infrastructure itself (networks, compute, storage), not post-deployment software configuration. Option D is wrong because backing up AWS resource configurations to Amazon S3 is a backup or snapshot activity, not a method for defining and provisioning resources; IaC uses declarative or imperative templates to create resources, not just archive their state.

Practice this question →

231

MCQmedium

A company runs a monthly batch data analytics job that requires 50 compute instances for exactly 2 hours. On AWS, the company launches 50 Amazon EC2 instances, runs the job, and then terminates all instances. The company's AWS bill shows a charge for only 100 instance-hours (50 instances × 2 hours). Which essential characteristic of cloud computing does this billing model best demonstrate?

A.Resource pooling

B.Measured service

C.On-demand self-service

D.Rapid elasticity

AnswerB

Measured service means that cloud resource usage is metered, monitored, controlled, and reported, enabling a pay-per-use billing model. In this scenario, the company is charged exactly for the 100 instance-hours consumed, which is a direct application of measured service.

Why this answer

The billing model charges only for the actual compute time consumed (100 instance-hours), which is a direct application of the 'measured service' characteristic. Measured service means cloud providers meter and bill customers based on actual resource usage (e.g., EC2 instance-hours, storage GB-months), enabling pay-as-you-go pricing. In this scenario, the company is charged precisely for the 50 instances × 2 hours of runtime, with no upfront or fixed costs, demonstrating usage-based metering.

Exam trap

The trap here is that candidates confuse 'measured service' (usage-based billing) with 'rapid elasticity' (scaling speed), but the question explicitly focuses on the billing charge for exactly the hours used, not the ability to scale quickly.

How to eliminate wrong answers

Option A is wrong because resource pooling refers to the provider's ability to serve multiple customers from shared physical resources (e.g., hypervisor-level multi-tenancy), not to billing granularity. Option C is wrong because on-demand self-service describes the ability to provision resources automatically without human interaction (e.g., via AWS Console or API), not the metered billing model. Option D is wrong because rapid elasticity is the ability to scale resources up or down quickly in response to demand (e.g., Auto Scaling groups), not the per-hour billing granularity shown here.

Practice this question →

232

MCQmedium

A company is adopting the cloud and wants to improve operational efficiency by treating their infrastructure as code. Which AWS service allows them to define and provision AWS infrastructure using JSON or YAML templates?

A.AWS Systems Manager

B.AWS CloudFormation

C.AWS OpsWorks

D.AWS Config

AnswerB

CloudFormation templates define all AWS resources declaratively in JSON/YAML — CloudFormation provisions, updates, and deletes them in a consistent, repeatable way.

Why this answer

AWS CloudFormation is the correct service because it allows you to define and provision AWS infrastructure as code using JSON or YAML templates. This enables repeatable, version-controlled deployments, directly supporting the goal of improving operational efficiency through infrastructure as code.

Exam trap

The trap here is that candidates may confuse AWS CloudFormation with AWS OpsWorks or AWS Systems Manager, as both can manage infrastructure but use different paradigms (declarative templates vs. configuration management) and are not designed for JSON/YAML-based infrastructure provisioning.

How to eliminate wrong answers

Option A is wrong because AWS Systems Manager is a management service for operational tasks like patching and configuration, not for defining infrastructure as code with templates. Option C is wrong because AWS OpsWorks is a configuration management service using Chef and Puppet, not JSON/YAML templates for infrastructure provisioning. Option D is wrong because AWS Config is a service for evaluating and auditing resource compliance, not for defining or provisioning infrastructure.

Practice this question →

233

MCQeasy

A global company has employees who work from various locations and use different devices such as laptops, tablets, and smartphones to access corporate applications. The company plans to migrate its applications to AWS and wants all employees to access these applications directly from the internet using standard web browsers without requiring any dedicated hardware or software at each branch. Which essential characteristic of cloud computing does this scenario BEST demonstrate?

A.Measured service

B.Resource pooling

C.Broad network access

D.Rapid elasticity

AnswerC

Broad network access is a core cloud characteristic that allows resources to be accessed over the network using standard protocols (such as HTTP/HTTPS) from a wide range of client devices (laptops, tablets, smartphones). This aligns directly with the requirement for employees to access applications via standard web browsers from various devices without dedicated hardware or software.

Why this answer

The scenario describes employees accessing corporate applications from various devices and locations using only standard web browsers, without dedicated hardware or software. This directly aligns with the cloud computing characteristic of broad network access, which mandates that resources are accessible over the network by standard mechanisms (e.g., HTTPS, TLS 1.2/1.3) from heterogeneous client platforms (laptops, tablets, smartphones). The key is that no site-to-site VPN appliances or thick client software are required—just a browser and an internet connection.

Exam trap

The trap here is that candidates confuse 'broad network access' with 'resource pooling' because both involve multi-device scenarios, but broad network access is specifically about the accessibility of services over the internet using standard protocols, not about how resources are shared among tenants.

How to eliminate wrong answers

Option A is wrong because measured service refers to the metering and billing of cloud resource usage (e.g., per-hour or per-GB charges), not to the method of access. Option B is wrong because resource pooling describes the multi-tenant model where physical and virtual resources are dynamically assigned to multiple customers; it does not address how users connect from diverse devices. Option D is wrong because rapid elasticity is the ability to automatically scale resources up or down based on demand; it is unrelated to the access method or client diversity.

Practice this question →

234

MCQhard

A company is designing a cloud architecture and wants to follow the Well-Architected Framework principle of 'stop guessing capacity.' Which AWS feature directly supports this principle?

A.AWS CloudFormation for repeatable deployments

B.Amazon EC2 Auto Scaling based on CloudWatch metrics

C.AWS Trusted Advisor cost optimization checks

D.AWS Cost Explorer right-sizing recommendations

AnswerB

Auto Scaling automatically adjusts EC2 capacity based on actual demand metrics, eliminating both over-provisioning (waste) and under-provisioning (performance degradation).

Why this answer

Amazon EC2 Auto Scaling directly supports the 'stop guessing capacity' principle by automatically adjusting the number of EC2 instances in response to real-time demand using CloudWatch metrics (e.g., CPU utilization, memory). This eliminates the need to manually provision for peak loads, ensuring you only pay for what you need while maintaining performance.

Exam trap

The trap here is that candidates confuse 'stop guessing capacity' with cost optimization tools like Cost Explorer or Trusted Advisor, but the principle is specifically about dynamic scaling to match demand, not about analyzing or reducing costs after the fact.

How to eliminate wrong answers

Option A is wrong because AWS CloudFormation enables repeatable infrastructure deployments via templates, but it does not dynamically adjust capacity based on demand; it provisions static resources. Option C is wrong because AWS Trusted Advisor cost optimization checks provide recommendations to reduce costs (e.g., idle instances), but they do not automatically scale capacity to match workload changes. Option D is wrong because AWS Cost Explorer right-sizing recommendations analyze historical usage to suggest instance type changes, but they are advisory and do not provide real-time, automated scaling to handle fluctuating demand.

Practice this question →

235

MCQeasy

A company is migrating its IT operations to AWS. Previously, when a developer needed a new server for a project, the developer had to submit a formal request to the IT department. The request would be reviewed, approved, and then a physical server would be procured, configured, and deployed—a process that often took several weeks. After migrating to AWS, the developer can log in to the AWS Management Console and launch a new Amazon EC2 instance with the exact required configuration within minutes, without any interaction with IT staff. Which essential characteristic of cloud computing does this scenario BEST demonstrate?

A.On-demand self-service

B.Broad network access

C.Resource pooling

D.Measured service

AnswerA

Correct. On-demand self-service allows users to provision and manage computing resources as needed without requiring human interaction with the service provider. The developer's ability to launch an EC2 instance directly from the AWS Management Console without IT involvement is a clear example of this characteristic.

Why this answer

The scenario describes a developer provisioning an EC2 instance directly via the AWS Management Console without any human intervention from IT staff. This aligns with the NIST-defined characteristic of on-demand self-service, where a consumer can unilaterally provision computing capabilities as needed automatically without requiring human interaction with each service provider.

Exam trap

The trap here is that candidates confuse 'on-demand self-service' with 'resource pooling' because both involve rapid provisioning, but the key differentiator is the absence of human interaction with the provider (IT staff) versus the multi-tenant sharing of resources.

How to eliminate wrong answers

Option B (Broad network access) is wrong because that characteristic refers to capabilities being available over the network and accessed through standard mechanisms (e.g., HTTPS, SSH) that promote use by heterogeneous client platforms (mobile phones, laptops, etc.), not the ability to self-provision without IT approval. Option C (Resource pooling) is wrong because that characteristic describes the provider’s computing resources being pooled to serve multiple consumers using a multi-tenant model, with physical and virtual resources dynamically assigned and reassigned according to consumer demand; it does not address the self-service provisioning workflow described.

Practice this question →

236

MCQmedium

A company is moving its workloads to AWS. The compliance team requires that all data must reside within the European Union (EU) and must not be stored on any physical server located outside the EU. The team also understands that AWS does not provide information about the specific physical server or data center where their data is stored. Which essential characteristic of cloud computing does this situation best describe?

A.On-demand self-service

B.Broad network access

C.Resource pooling

D.Rapid elasticity

AnswerC

Resource pooling means the provider's compute, storage, network, and other resources are pooled to serve many customers, with the customer having no knowledge or control over the exact physical location of the resources. The customer can specify location at a higher level (e.g., a specific Region or country), which meets the compliance requirement of keeping data within the EU.

Why this answer

Option C is correct because resource pooling allows AWS to serve multiple customers from shared physical resources, with the provider abstracting the exact physical server location. The compliance requirement that data must reside only in the EU is satisfied by selecting an EU Region (e.g., eu-west-1), but AWS does not disclose the specific physical server or data center within that Region, which is a direct consequence of resource pooling—the provider's multi-tenant model hides the underlying hardware details from the customer.

Exam trap

The trap here is that candidates confuse 'resource pooling' with 'data residency' or 'compliance controls,' mistakenly thinking that choosing a Region alone satisfies the requirement, when the question specifically tests the cloud characteristic that explains why AWS does not disclose the exact physical server—resource pooling.

How to eliminate wrong answers

Option A is wrong because on-demand self-service refers to a user's ability to provision resources automatically without human interaction, not to data residency or physical server location abstraction. Option B is wrong because broad network access describes the capability to access resources over the network using standard protocols (e.g., HTTPS, SSH), which is unrelated to where the physical servers are located. Option D is wrong because rapid elasticity is the ability to scale resources up or down quickly in response to demand, not a characteristic that governs data storage location or the hiding of physical server details.

Practice this question →

237

MCQmedium

A company runs a batch processing workload on an on-premises data center. The servers are powerful machines that are used at maximum capacity only for a few days each month during financial reporting periods. For the rest of the month, the servers run at very low utilization. The CFO wants to migrate this workload to AWS to reduce costs. Which characteristic of AWS cloud computing is most directly aligned with the CFO's goal of paying only for the compute capacity actually used?

A.High availability across multiple Availability Zones

B.Elasticity to automatically scale resources up and down

C.Pay-as-you-go pricing model

D.The ability to choose from a wide variety of instance types

AnswerC

The pay-as-you-go model lets customers pay only for the compute capacity they actually use, with no upfront capital expenditure or charges for idle resources. This directly meets the CFO's objective of eliminating costs for underutilized on-premises servers.

Why this answer

The pay-as-you-go pricing model (Option C) directly aligns with the CFO's goal because it allows the company to pay only for the compute capacity they actually consume, with no upfront costs or long-term commitments. In this scenario, the batch processing workload runs at maximum capacity only a few days per month, so the company can provision resources during those peaks and stop them during low-utilization periods, avoiding the cost of idle on-premises servers. This model eliminates the need to pay for unused capacity, directly reducing costs as the CFO desires.

Exam trap

The trap here is that candidates confuse elasticity (the ability to scale) with the pay-as-you-go pricing model, but elasticity is a characteristic that enables cost optimization, while pay-as-you-go is the specific billing mechanism that directly ensures you pay only for what you use.

How to eliminate wrong answers

Option A is wrong because high availability across multiple Availability Zones is a resilience and fault-tolerance feature, not a pricing or cost-reduction mechanism; it ensures workload uptime during failures but does not directly enable paying only for used compute capacity. Option B is wrong because elasticity is the ability to automatically scale resources up and down based on demand, which supports cost efficiency but is not itself a pricing model; the CFO's goal is specifically about the payment structure (pay-as-you-go), not the scaling mechanism, and elasticity without pay-as-you-go pricing could still incur costs for provisioned resources even if scaled down.

Practice this question →

238

MCQmedium

A company is moving its on-premises workloads to AWS. The company's chief financial officer notes that AWS can provide computing resources at a lower cost per unit because AWS spreads the cost of building and maintaining vast data centers across millions of customers. This cost advantage is best described as an example of which concept?

A.Resource pooling

B.Economies of scale

C.Measured service

D.Broad network access

AnswerB

Correct. Economies of scale occur when the average cost per unit decreases as the scale of operations increases. AWS spreads its massive infrastructure investments across millions of customers, enabling lower per-unit costs than a single company could achieve on its own.

Why this answer

Economies of scale occur when a provider like AWS spreads the fixed costs of building and operating massive data centers across a huge number of customers, reducing the per-unit cost of compute, storage, and networking. This allows AWS to offer lower prices than a single company could achieve by running its own on-premises infrastructure. The CFO's observation directly describes this principle: AWS's aggregated demand drives down the average cost per resource.

Exam trap

The trap here is confusing economies of scale with resource pooling, as both involve shared infrastructure, but economies of scale specifically refer to the cost reduction from large-scale operations, not the multi-tenant resource allocation model.

How to eliminate wrong answers

Option A is wrong because resource pooling refers to the multi-tenant model where computing resources are dynamically assigned and reassigned to serve multiple customers, not the cost advantage from scale. Option C is wrong because measured service is the metering and billing of cloud resource usage (e.g., per-hour or per-GB charges), not the underlying cost efficiency from large-scale operations. Option D is wrong because broad network access describes the ability to access cloud resources over the network via standard protocols (e.g., HTTPS, SSH), not the economic benefit of shared infrastructure costs.

Practice this question →