CCNA Cloud Concepts Questions — Page 4 of 4

226

MCQmedium

A company runs its production database on an Azure SQL Database (PaaS) and its custom application on an Azure virtual machine (IaaS). The company needs to ensure that operating system security patches are applied. According to the shared responsibility model, which resource requires the company to apply OS patches?

A.Azure SQL Database only

B.Azure virtual machine only

C.Both Azure SQL Database and the virtual machine

D.Neither resource requires the company to apply OS patches

AnswerB

Azure virtual machine is an IaaS service. The customer is responsible for managing the guest operating system, including applying security patches, updates, and configuration.

Why this answer

In the shared responsibility model, the customer is responsible for securing the operating system on IaaS resources like Azure virtual machines. Azure SQL Database is a PaaS service where Microsoft manages the underlying OS, including patch management. Therefore, only the Azure virtual machine requires the company to apply OS security patches.

Exam trap

The trap here is that candidates mistakenly assume PaaS services like Azure SQL Database still require customer OS patching, confusing the boundary between customer-managed and provider-managed responsibilities under the shared responsibility model.

How to eliminate wrong answers

Option A is wrong because Azure SQL Database is a PaaS service where Microsoft handles OS patching, so the company does not need to apply OS patches to it. Option C is wrong because it incorrectly assumes the company must patch both resources; in reality, Microsoft manages the OS for Azure SQL Database, leaving only the Azure VM (IaaS) requiring customer-applied OS patches.

Practice this question →

227

MCQmedium

A company operates on-premises servers that they own. They are considering moving to Azure. Which cloud benefit would MOST directly reduce their total cost of ownership?

A.Automatic compliance with all regulations

B.Eliminating hardware purchase and maintenance costs

C.Guaranteed zero downtime for all services

D.Free support for all Azure services

AnswerB

Moving to cloud eliminates CapEx for servers, datacenter space, and hardware refresh cycles — the biggest on-premises cost drivers.

Why this answer

Option B is correct because moving to Azure eliminates the need to purchase, maintain, and eventually replace physical servers, which directly reduces capital expenditure (CapEx) and operational costs related to hardware lifecycle management. This is the most direct way to lower total cost of ownership (TCO) when transitioning from on-premises infrastructure to a public cloud model.

Exam trap

The trap here is that candidates may confuse 'eliminating hardware costs' with other indirect benefits like compliance or support, but the question specifically asks for the MOST direct reduction in TCO, which is the removal of physical hardware purchase and maintenance expenses.

How to eliminate wrong answers

Option A is wrong because Azure does not automatically ensure compliance with all regulations; it provides compliance certifications and tools (e.g., Azure Policy, Compliance Manager), but customers remain responsible for configuring their workloads to meet specific regulatory requirements (shared responsibility model). Option C is wrong because Azure does not guarantee zero downtime for all services; while it offers high-availability SLAs (e.g., 99.99% for certain services), planned maintenance, unplanned outages, and regional failures can still cause downtime, and some services have lower SLAs. Option D is wrong because Azure does not offer free support for all services; basic support is included for billing and subscription management, but technical support requires a paid support plan (e.g., Developer, Standard, Professional Direct).

Practice this question →

228

Drag & Dropmedium

Arrange the steps to implement Azure Cost Management and set a budget.

Drag steps to the numbered slots on the right, or tap a step then tap a slot.

Steps

Order

Why this order

Cost management involves portal access, budget creation, alerts, monitoring, and adjustment.

Practice this question →

229

MCQmedium

A company is migrating its customer relationship management (CRM) system to a Software as a Service (SaaS) provider. The provider manages the application, runtime, middleware, and infrastructure. The company's IT security team is concerned about who is responsible for protecting the company's data and managing user access. Based on the shared responsibility model for cloud computing, which statement is correct?

A.The SaaS provider is responsible for everything, including data classification and user access control.

B.The company is responsible for the security of the application itself, including patching vulnerabilities in the CRM software.

C.The company is responsible for managing user access and protecting their own data within the SaaS application.

D.The SaaS provider is responsible for physical security of data centers, and the company is responsible for patching the operating system of the servers hosting the CRM.

AnswerC

This is correct. Under the shared responsibility model for SaaS, the customer manages user identities, data classification, and access control. The provider secures the platform and infrastructure, but the customer must ensure only authorized users access the data and that data is handled appropriately.

Why this answer

In the shared responsibility model for SaaS, the provider manages the application, runtime, middleware, and infrastructure, but the customer retains responsibility for securing their own data and managing user access. This includes tasks such as data classification, identity and access management (IAM), and ensuring compliance with internal policies. Option C correctly identifies that the company must handle user access and data protection within the SaaS application.

Exam trap

The trap here is that candidates often assume the SaaS provider handles all security aspects, including data and access, because the provider manages the application, but the shared responsibility model clearly assigns data and access management to the customer.

How to eliminate wrong answers

Option A is wrong because it incorrectly states the SaaS provider is responsible for everything, including data classification and user access control; in reality, the customer retains responsibility for their data and user access. Option B is wrong because it claims the company is responsible for patching vulnerabilities in the CRM software, but in a SaaS model, the provider manages the application and its security patches, not the customer.

Practice this question →

230

MCQeasy

Which of the following is NOT a benefit of moving to the cloud?

A.Reduced time to provision new resources

B.Elimination of internet connectivity requirements

C.Access to a global network of data centers

D.Conversion of capital expenses to operational expenses

AnswerB

Cloud services typically require internet connectivity — this is not a cloud benefit, but rather a dependency.

Why this answer

Moving to the cloud does not eliminate the need for internet connectivity; in fact, cloud services are accessed over the internet or dedicated network connections. Option B is correct because it presents a false benefit—cloud computing still requires network connectivity to reach the provider's endpoints, and without it, resources become inaccessible. The other options are legitimate benefits: faster provisioning, global data center reach, and converting CapEx to OpEx.

Exam trap

The trap here is that candidates confuse 'cloud' with 'offline' or 'self-contained' computing, mistakenly thinking the cloud eliminates the need for a network, when in reality it is entirely dependent on network access to function.

How to eliminate wrong answers

Option A is wrong because reduced time to provision new resources is a real benefit of cloud computing—infrastructure is abstracted and can be spun up via APIs in minutes, compared to weeks for on-premises hardware. Option C is wrong because access to a global network of data centers is a core cloud benefit—providers like Azure operate regions worldwide, enabling low-latency deployment and geo-redundancy. Option D is wrong because converting capital expenses (CapEx) to operational expenses (OpEx) is a key financial advantage of the cloud—you pay for usage rather than upfront hardware costs, shifting from fixed to variable expenditure.

Practice this question →

231

MCQmedium

A company has traditionally managed on-premises servers for their internal business applications. Setting up a new test environment involves ordering hardware, waiting for delivery, racking, and configuring the OS and applications, which typically takes two to three weeks. The company is migrating their development and testing workloads to Azure. Now, developers can deploy a complete, pre-configured test environment using Azure Resource Manager templates in under two hours. This ability to rapidly provision resources and adapt to changing requirements best illustrates which benefit of cloud computing?

A.Scalability

B.Agility

C.High availability

D.Geographic distribution

AnswerB

Correct. Agility is the ability to quickly adapt to changing business requirements by provisioning and deprovisioning resources rapidly. The move from weeks to hours clearly demonstrates agility.

Why this answer

The scenario describes how the company can provision a complete test environment in under two hours using Azure Resource Manager templates, compared to the two-to-three-week on-premises process. This rapid provisioning and ability to quickly adapt to changing requirements is the definition of agility in cloud computing, which focuses on speed, flexibility, and reduced time-to-market for IT resources.

Exam trap

The trap here is that candidates often confuse agility with scalability, but agility specifically measures the speed of resource provisioning and adaptation to change, while scalability measures the capacity to handle growth or load variations.

How to eliminate wrong answers

Option A is wrong because scalability refers to the ability to increase or decrease resources (e.g., compute, storage) to handle varying loads, not the speed of provisioning or adapting to changes. Option C is wrong because high availability ensures that applications remain operational with minimal downtime through redundancy across multiple Azure Availability Zones or regions, which is unrelated to the rapid deployment of test environments described in the question.

Practice this question →

232

MCQmedium

What does 'manageability' mean as a benefit of cloud computing?

A.The ability to physically access and repair cloud hardware

B.The ability to manage cloud resources through portal, CLI, APIs, and automated monitoring

C.The right to audit the cloud provider's security practices

D.The guarantee that resources will always be available

AnswerB

Manageability covers how you control and monitor resources — through multiple interfaces and automated capabilities.

Why this answer

Manageability in cloud computing refers to the ability to efficiently administer and control cloud resources through multiple interfaces such as the Azure portal, command-line interface (CLI), APIs, and automated monitoring tools. This allows administrators to deploy, configure, update, and scale resources programmatically or via a web interface without needing physical access to hardware, enabling rapid changes and consistent management across large environments.

Exam trap

The trap here is that candidates confuse manageability with other cloud benefits like reliability or security, mistakenly thinking it involves physical access or uptime guarantees, when it specifically refers to the ease of controlling resources through management interfaces and automation.

How to eliminate wrong answers

Option A is wrong because physical access to cloud hardware is not a customer benefit; it is the cloud provider's responsibility, and customers manage resources virtually, not by physically repairing servers. Option C is wrong because auditing the provider's security practices is a compliance or transparency feature, not a core definition of manageability; manageability focuses on operational control, not audit rights. Option D is wrong because the guarantee of resource availability is a definition of reliability or high availability, not manageability; manageability is about the ease of controlling and administering resources, not their uptime.

Practice this question →

233

MCQeasy

A company is moving its IT infrastructure to the cloud to avoid large upfront hardware purchases and instead pay a predictable monthly fee. Which cloud benefit does this represent?

A.High availability

B.Elasticity

C.Consumption-based pricing

D.Scalability

AnswerC

Correct. Consumption-based pricing means you pay only for what you use, avoiding large upfront costs.

Why this answer

Consumption-based pricing is a cloud benefit where customers pay only for the resources they use (e.g., compute hours, storage GBs) rather than making large upfront capital expenditures. This model shifts costs from CapEx to OpEx, enabling predictable monthly billing based on actual consumption. The scenario explicitly describes avoiding upfront hardware purchases and paying a predictable monthly fee, which directly aligns with this pay-as-you-go model.

Exam trap

The trap here is that candidates confuse elasticity (scaling resources) with the financial model of consumption-based pricing, but the question specifically asks about avoiding upfront costs and paying a predictable monthly fee, which is purely a pricing model, not a scaling capability.

How to eliminate wrong answers

Option A is wrong because high availability refers to ensuring services remain operational despite failures (e.g., through redundancy across availability zones), not to the financial model of paying for usage. Option B is wrong because elasticity is the ability to automatically scale resources up or down based on demand (e.g., using Azure VM Scale Sets), which affects performance and cost efficiency but does not inherently eliminate upfront hardware purchases or guarantee a predictable monthly fee.

Practice this question →

234

MCQmedium

Which benefit of cloud computing allows developers to test and deploy applications globally in minutes?

A.Economies of scale

B.Speed and agility in global deployment

C.Fault tolerance

D.Predictable pricing

AnswerB

Cloud infrastructure is available in minutes globally, enabling rapid development and testing across regions.

Why this answer

Option B is correct because cloud computing enables rapid global deployment through a distributed infrastructure of data centers and content delivery networks (CDNs). Developers can replicate applications across multiple regions in minutes using automated deployment pipelines and infrastructure-as-code tools, eliminating the need to provision physical servers in each location.

Exam trap

The trap here is that candidates confuse 'fault tolerance' (high availability) with 'global deployment speed,' or assume 'economies of scale' implies faster deployment due to larger infrastructure, but neither addresses the time-to-deploy across regions.

How to eliminate wrong answers

Option A is wrong because economies of scale refer to cost advantages from large-scale operations, not the speed of global deployment. Option C is wrong because fault tolerance ensures system resilience and uptime during failures, not rapid deployment capabilities. Option D is wrong because predictable pricing involves cost forecasting and budgeting, not the ability to deploy applications quickly across regions.

Practice this question →

235

MCQmedium

A retail company experiences fluctuating customer traffic throughout the year. During peak seasons, traffic can increase by 300% for a few weeks. The company wants to pay only for the compute resources it uses, without needing to invest in permanent infrastructure to handle peak loads. Which cloud computing characteristic best supports this requirement?

A.High availability

B.Elasticity

C.Fault tolerance

D.Geo-redundancy

AnswerB

Elasticity allows resources to be dynamically provisioned and de-provisioned in response to changing demand. This directly supports paying only for what is used and avoids over-provisioning for peak loads.

Why this answer

Elasticity is the cloud computing characteristic that allows resources to automatically scale up or down based on demand. In this scenario, the retail company needs to handle a 300% traffic spike during peak seasons without permanently provisioning infrastructure, and elasticity enables dynamic provisioning and de-provisioning of compute resources to match the fluctuating load, ensuring they pay only for what they use.

Exam trap

The trap here is that candidates often confuse elasticity with high availability, thinking that keeping services running during spikes is the same as scaling resources, but high availability ensures uptime, not dynamic capacity adjustment.

How to eliminate wrong answers

Option A is wrong because high availability focuses on ensuring uptime and accessibility of services through redundancy and failover mechanisms, not on dynamically adjusting resource capacity to match variable demand. Option C is wrong because fault tolerance is the ability of a system to continue operating without interruption despite component failures, which does not address the need to scale resources up or down based on traffic fluctuations. Option D is wrong because geo-redundancy involves replicating data or services across multiple geographic regions for disaster recovery and data durability, not for scaling compute resources in response to demand spikes.

Practice this question →

236

MCQmedium

What is the primary advantage of deploying VMs across multiple Azure Availability Zones instead of a single Availability Set?

A.VMs in different Availability Zones are always cheaper than Availability Sets

B.Protection against datacenter-level failures with a higher SLA (99.99% vs. 99.95%)

C.VMs automatically scale in response to demand when placed in Availability Zones

D.Availability Zones reduce network latency between VM instances

AnswerB

Availability Zones protect against datacenter failures and provide 99.99% SLA vs. 99.95% for Availability Sets.

Why this answer

Azure Availability Zones are physically separate datacenters within an Azure region, each with independent power, cooling, and networking. Deploying VMs across multiple zones protects against a complete datacenter failure, enabling a 99.99% VM-to-VM connectivity SLA. In contrast, an Availability Set protects against hardware failures within a single datacenter (e.g., rack or update domain failures) and offers a 99.95% SLA.

Exam trap

The trap here is that candidates often confuse Availability Zones with Availability Sets, thinking both provide the same level of resilience, but the key difference is that Zones protect against datacenter-level failures while Sets only protect against rack-level failures within a single datacenter.

How to eliminate wrong answers

Option A is wrong because Availability Zones do not inherently reduce costs; in fact, they may incur inter-zone data transfer charges, whereas Availability Sets have no such additional cost. Option C is wrong because neither Availability Zones nor Availability Sets provide automatic scaling; scaling is handled by separate services like Virtual Machine Scale Sets or Azure Autoscale. Option D is wrong because Availability Zones typically increase network latency between VMs in different zones due to physical separation, while VMs in the same Availability Set are in the same datacenter with lower latency.

Practice this question →

237

MCQmedium

A company runs a web application on Azure App Service. During a marketing campaign, the application's traffic surges to five times its normal level. The application is configured to automatically add more instances to handle the increased load and then remove them when demand returns to normal. This ability to dynamically provision and de-provision resources based on real-time demand is a direct example of which cloud computing characteristic?

A.Elasticity

B.Scalability

C.High availability

D.Fault tolerance

AnswerA

Correct. Elasticity is the cloud characteristic that enables resources to be automatically added or removed in response to real-time demand, allowing the application to handle traffic spikes and then scale back down to optimize costs.

Why this answer

The scenario describes automatically adding and removing App Service instances in response to real-time traffic spikes, which is the definition of elasticity. Elasticity is the ability to dynamically scale resources up or down to match demand, ensuring you only pay for what you use. In Azure, this is implemented via autoscale rules that adjust the instance count based on metrics like CPU or request queue length.

Exam trap

The trap here is that candidates often confuse scalability (the ability to grow) with elasticity (the ability to both grow and shrink automatically), so they pick 'Scalability' without recognizing that the scenario explicitly mentions removing resources when demand returns to normal.

How to eliminate wrong answers

Option B (Scalability) is wrong because scalability refers to the ability to increase capacity to handle growth, but it does not inherently include the ability to automatically reduce resources when demand drops; elasticity specifically includes both scaling up and scaling down. Option C (High availability) is wrong because high availability focuses on ensuring the application remains accessible despite failures, typically through redundancy across zones or regions, not on dynamic resource provisioning based on load. Option D (Fault tolerance) is wrong because fault tolerance is the ability of a system to continue operating without interruption when one or more components fail, which is a different characteristic from adjusting capacity in response to demand changes.

Practice this question →

238

MCQhard

A financial services company is evaluating a public cloud provider. They are concerned about the shared responsibility model for security. The company must ensure that their customer data is encrypted at rest and in transit. Under the shared responsibility model, which security control is the cloud provider typically responsible for?

A.Encrypting customer data at rest

B.Patching virtual machines

C.Physical network security

D.Managing customer access policies

AnswerC

The cloud provider is responsible for the security of the physical network, including firewalls and infrastructure against physical threats.

Why this answer

Under the shared responsibility model, the cloud provider is responsible for the security OF the cloud, which includes physical network security such as protecting the data center perimeter, network infrastructure, and hardware. This is correct because physical security controls (e.g., access badges, surveillance, and network firewalls at the provider's edge) are entirely the provider's domain and cannot be delegated to the customer.

Exam trap

The trap here is that candidates often confuse 'encryption at rest' (which is a shared or customer responsibility depending on key management) with physical security, leading them to choose A, but the provider's inherent responsibility is always the physical infrastructure, not the customer's data encryption.

How to eliminate wrong answers

Option A is wrong because encrypting customer data at rest is typically a customer responsibility, as the customer controls the encryption keys and the data itself, though some providers offer server-side encryption as an option. Option B is wrong because patching virtual machines is a customer responsibility in IaaS and PaaS models, as the customer manages the OS and application layers. Option D is wrong because managing customer access policies (e.g., Azure RBAC, IAM roles) is always the customer's responsibility, as the customer defines who can access their resources.

Practice this question →

239

MCQmedium

A company runs a nightly data processing job that requires high CPU usage for only 15 minutes. During the day, the compute resources are idle. The company wants to reduce costs by automatically starting compute resources only when the job runs and shutting them down after completion, without manual intervention. Which cloud computing characteristic directly meets this requirement?

A.High availability

B.Elasticity

C.Fault tolerance

D.Scalability

AnswerB

Elasticity is the ability to dynamically scale resources up and down, including automatically starting resources when needed and shutting them down when idle, which directly meets the cost-saving requirement in this scenario.

Why this answer

Elasticity is the cloud computing characteristic that enables resources to be automatically provisioned and de-provisioned in response to workload demands. In this scenario, the nightly job requires high CPU for only 15 minutes, and elasticity allows the compute resources to scale up exactly when the job starts and scale down to zero after completion, eliminating idle costs without manual intervention.

Exam trap

The trap here is that candidates confuse scalability (ability to handle growth, often manual or planned) with elasticity (automatic, real-time scaling to match demand), leading them to pick scalability even though the requirement explicitly calls for automatic start/stop without intervention.

How to eliminate wrong answers

Option A is wrong because high availability focuses on ensuring uptime and redundancy across failures (e.g., multiple availability zones), not on dynamically adjusting resource capacity to match workload fluctuations. Option C is wrong because fault tolerance is about maintaining system operation despite component failures (e.g., redundant servers or automatic failover), not about starting and stopping resources based on usage patterns. Option D is wrong because scalability refers to the ability to increase or decrease resources to handle growth, but it typically implies manual or planned adjustments (e.g., adding more VMs for a known event), not the automatic, real-time provisioning and de-provisioning required for a short-lived job.

Practice this question →

240

MCQmedium

A company deploys a line-of-business application on an Azure virtual machine. The IT team wants to ensure the application remains secure. According to the shared responsibility model, which of the following security tasks is the sole responsibility of the customer (the company)?

A.Protecting the physical servers in the Azure datacenter with video surveillance and access controls.

B.Configuring the network security group (NSG) rules to restrict inbound traffic to the virtual machine.

C.Ensuring the hypervisor that isolates virtual machines is free from vulnerabilities.

D.Maintaining the security of the Azure Fabric Controller that manages the host servers.

AnswerB

This is correct because configuring NSG rules is part of managing the network security for resources within the customer's Azure subscription. Under the shared responsibility model, the customer controls access to their virtual machines.

Why this answer

Option B is correct because configuring Network Security Group (NSG) rules to restrict inbound traffic is a customer responsibility under the shared responsibility model. The customer controls the virtual network and VM-level access, including defining allow/deny rules for protocols like TCP/UDP on specific ports. Azure manages the underlying infrastructure, but the customer must secure their own application traffic.

Exam trap

The trap here is that candidates confuse 'security of the cloud' (physical and hypervisor security, which Azure handles) with 'security in the cloud' (customer-managed configurations like NSGs), leading them to incorrectly assign physical or hypervisor security to the customer.

How to eliminate wrong answers

Option A is wrong because protecting physical servers with video surveillance and access controls is the responsibility of Microsoft as the cloud provider, not the customer. Option C is wrong because ensuring the hypervisor is free from vulnerabilities is a Microsoft responsibility, as the hypervisor is part of the virtualization layer managed by Azure. Option D is wrong because maintaining the security of the Azure Fabric Controller, which orchestrates host server management, is solely Microsoft's responsibility under the shared model.

Practice this question →

241

MCQmedium

A company runs an e-commerce web application on a set of Azure virtual machines behind a load balancer. The application experiences unpredictable traffic surges during flash sales. The company configures an autoscale setting that automatically adds virtual machines when the average CPU usage across the existing VMs exceeds 75% for five minutes, and removes virtual machines when CPU usage drops below 30% for ten minutes. Which essential characteristic of cloud computing does this configuration primarily demonstrate?

A.Measured service

B.Rapid elasticity

C.Resource pooling

D.Broad network access

AnswerB

Rapid elasticity is the correct answer because the autoscale configuration automatically adds and removes virtual machines based on CPU demand, enabling the system to elastically scale outward and inward. This is a core characteristic of cloud computing defined by NIST.

Why this answer

B is correct because the autoscale configuration dynamically adds and removes virtual machines in response to real-time CPU usage thresholds, which is the defining characteristic of rapid elasticity. This allows the e-commerce application to scale computing resources up and down automatically and seamlessly to match unpredictable traffic surges, ensuring performance during flash sales without manual intervention.

Exam trap

The trap here is that candidates may confuse rapid elasticity with measured service because both involve resource usage, but measured service is about billing and monitoring usage, not the ability to dynamically scale resources up or down.

How to eliminate wrong answers

Option A is wrong because measured service refers to the metering and billing of cloud resource usage (e.g., pay-per-hour or per-GB), not the dynamic scaling of resources. Option C is wrong because resource pooling describes the provider's multi-tenant model where physical and virtual resources are shared across multiple customers, not the automatic adjustment of resources for a single workload. Option D is wrong because broad network access means resources are accessible over the network via standard protocols (e.g., HTTPS, SSH), which is a prerequisite but not the primary characteristic demonstrated by autoscaling.

Practice this question →

242

MCQmedium

A company is evaluating moving their workloads to Azure. They currently operate a small on-premises data center. Their IT manager notes that by using Azure, they will benefit from the fact that Microsoft operates many large data centers globally, which allows them to achieve lower network bandwidth costs and hardware procurement discounts. The company will not have to negotiate separate contracts for power and cooling. Which cloud computing concept does this benefit best illustrate?

A.High availability

B.Elasticity

C.Economies of scale

D.Agility

AnswerC

Economies of scale are the cost advantages that enterprises obtain due to their size, output, or scale of operation. Microsoft's massive data centers and bulk purchasing power reduce per-unit costs, which is exactly what the scenario describes.

Why this answer

The scenario describes how Microsoft's global scale of operations—operating many large data centers—enables lower network bandwidth costs and hardware procurement discounts, and eliminates the need for separate power and cooling contracts. This directly illustrates economies of scale, where the average cost per unit decreases as the scale of operations increases, allowing Microsoft to pass these savings to customers. It is not about technical capabilities like availability, elasticity, or agility, but about the cost advantage derived from massive infrastructure investment.

Exam trap

The trap here is that candidates confuse economies of scale with elasticity or agility, because both involve 'scaling' in name, but elasticity is about dynamic resource adjustment while economies of scale is about cost reduction from large-scale operations.

How to eliminate wrong answers

Option A is wrong because high availability refers to ensuring services remain operational with minimal downtime through redundancy and failover mechanisms (e.g., Azure Availability Zones), not about cost savings from scale. Option B is wrong because elasticity is the ability to automatically scale resources up or down based on demand (e.g., Azure Virtual Machine Scale Sets), which is a dynamic provisioning feature, not a cost advantage from global data center scale. Option D is wrong because agility refers to the speed and ease of deploying and adapting resources (e.g., rapid provisioning via Azure Resource Manager), not the cost benefits from bulk purchasing and operational efficiencies.

Practice this question →

243

MCQeasy

A startup wants to run a web application without managing the underlying servers. They only want to upload their code and let the cloud provider handle the runtime, scaling, and maintenance. Which cloud service model is this?

A.Platform as a Service (PaaS)

B.Infrastructure as a Service (IaaS)

C.Software as a Service (SaaS)

D.Function as a Service (FaaS)

AnswerA

PaaS abstracts the underlying infrastructure, allowing you to focus on code deployment.

Why this answer

Platform as a Service (PaaS) is the correct model because it provides a managed hosting environment where the startup can deploy their web application code without managing the underlying servers, operating systems, or runtime infrastructure. Azure App Service is a prime example of PaaS, handling automatic scaling, patching, and load balancing while the customer only focuses on code and data.

Exam trap

The trap here is that candidates often confuse PaaS with FaaS because both are 'serverless' in marketing, but FaaS (e.g., Azure Functions) is event-driven and stateless per invocation, not designed for a persistent web application with session state or long-running requests.

How to eliminate wrong answers

Option B (IaaS) is wrong because it requires the startup to provision, configure, and manage virtual machines, storage, and networking, which contradicts the requirement of not managing servers. Option C (SaaS) is wrong because it delivers fully functional software applications (e.g., Office 365) that users consume, not a platform for uploading custom code. Option D (FaaS) is wrong because it is a subset of serverless computing focused on individual functions triggered by events, not a full web application runtime; the startup would need to manage function orchestration and state, which is more granular than the described need.

Practice this question →

244

MCQmedium

What does 'infrastructure as code' (IaC) mean in the context of Azure?

A.Writing code that runs directly on Azure hardware

B.Defining Azure resources in configuration files that can be version-controlled and reused

C.Using Azure CLI scripts to deploy one resource at a time imperatively

D.Converting physical server hardware into virtual machines

AnswerB

IaC defines infrastructure (VMs, VNets, databases) in code files for repeatable, version-controlled deployments.

Why this answer

Option B is correct because Infrastructure as Code (IaC) in Azure involves defining and managing Azure resources (e.g., virtual networks, VMs, storage accounts) using declarative configuration files such as ARM templates, Bicep, or Terraform. These files can be stored in version control (e.g., Git), enabling repeatable, consistent deployments and rollbacks through automation, rather than manual or imperative steps.

Exam trap

The trap here is that candidates confuse IaC with imperative scripting (Option C) or with running application code on Azure (Option A), but IaC specifically means defining infrastructure in version-controlled, declarative configuration files.

How to eliminate wrong answers

Option A is wrong because writing code that runs directly on Azure hardware describes custom runtime code or Azure Functions, not IaC; IaC focuses on resource provisioning, not application execution. Option C is wrong because using Azure CLI scripts to deploy one resource at a time imperatively is a manual, procedural approach, not IaC; IaC emphasizes declarative, idempotent configuration files that define the entire desired state. Option D is wrong because converting physical server hardware into virtual machines describes server virtualization or migration (e.g., Azure Migrate), not IaC; IaC is about codifying infrastructure definitions, not hardware abstraction.

Practice this question →

245

MCQeasy

A company uses Azure SQL Database (PaaS). According to the shared responsibility model, who is responsible for applying security patches to the underlying operating system that runs the database service?

A.Microsoft

B.The customer

C.Both

D.Neither

AnswerA

Microsoft handles OS patching for PaaS services like Azure SQL Database.

Why this answer

Microsoft is responsible for applying security patches to the underlying operating system that hosts Azure SQL Database because it is a Platform as a Service (PaaS) offering. In the PaaS shared responsibility model, the cloud provider manages the infrastructure, including the OS, runtime, and network, while the customer is responsible for data and access management. Azure SQL Database abstracts the OS layer entirely, so Microsoft handles all patching and maintenance to ensure security and compliance.

Exam trap

The trap here is that candidates confuse PaaS with IaaS, where the customer would be responsible for OS patching, leading them to incorrectly select 'The customer' or 'Both'.

How to eliminate wrong answers

Option B is wrong because the customer does not have access to the underlying OS in Azure SQL Database (PaaS) and therefore cannot apply patches; the customer is only responsible for data, schema, and access controls. Option C is wrong because responsibility is not shared for OS patching in PaaS; Microsoft alone manages the OS, while the customer manages their own data and configurations. Option D is wrong because Microsoft explicitly takes responsibility for the OS and infrastructure in PaaS services, so it is not 'neither'.

Practice this question →

246

MCQeasy

A company can provision virtual machines in Azure without submitting a request or waiting for hardware procurement. Which cloud characteristic does this describe?

A.Rapid elasticity

B.Measured service

C.On-demand self-service

D.Resource pooling

AnswerC

This characteristic allows users to provision resources automatically and without human interaction.

Why this answer

Option C is correct because on-demand self-service allows users to provision virtual machines and other cloud resources automatically without requiring human interaction with the service provider. This eliminates the need for submitting a formal request or waiting for hardware procurement, as the provisioning is handled through a web portal, API, or CLI.

Exam trap

The trap here is confusing on-demand self-service (the ability to provision without human interaction) with rapid elasticity (the ability to scale resources dynamically), as both involve automation but address different cloud characteristics.

How to eliminate wrong answers

Option A is wrong because rapid elasticity refers to the ability to scale resources up or down quickly in response to demand, not the initial provisioning without human intervention. Option B is wrong because measured service involves metering and billing for resource usage, such as pay-as-you-go, not the self-service provisioning capability. Option D is wrong because resource pooling describes the multi-tenant model where physical and virtual resources are shared across multiple customers, not the ability to provision without waiting.

Practice this question →

247

MCQmedium

Which cloud computing benefit specifically refers to customers being able to access the latest technology without managing upgrades?

A.Economies of scale

B.Always-current technology without customer-managed upgrades

C.Geographic distribution of data centers

D.Predictable billing with reserved capacity

AnswerB

Cloud providers handle infrastructure upgrades, giving customers automatic access to latest hardware and service improvements.

Why this answer

Option B is correct because one of the key benefits of cloud computing is that the cloud provider handles all hardware and software updates, patches, and version upgrades. Customers always have access to the latest features, security fixes, and performance improvements without needing to plan, test, or execute upgrade cycles themselves. This is a core value proposition of the consumption-based model, shifting operational overhead to the provider.

Exam trap

The trap here is that candidates often confuse 'always-current technology' with 'economies of scale' because both relate to cost savings, but the question specifically asks about accessing the latest technology without managing upgrades — a benefit of the provider's operational responsibility, not pricing efficiency.

How to eliminate wrong answers

Option A is wrong because economies of scale refer to cost advantages gained by the provider through massive infrastructure purchasing power, which are then passed to customers as lower pay-as-you-go prices — not to technology currency or upgrade management. Option C is wrong because geographic distribution of data centers provides low-latency access, data residency compliance, and disaster recovery capabilities, but does not address the automatic availability of the latest technology or the elimination of customer-managed upgrades. Option D is wrong because predictable billing with reserved capacity is a pricing and cost-management benefit that allows customers to commit to a certain usage level for a discount, but it has no relation to the automatic refresh of hardware or software versions.

Practice this question →

248

MCQmedium

A company plans to migrate a line-of-business application to Azure virtual machines (IaaS). The company's security team is reviewing the shared responsibility model to determine which security tasks are handled by Microsoft. Which of the following security responsibilities belongs to Microsoft?

A.Configuring operating system firewalls on the virtual machines

B.Patching the guest operating system of the virtual machines

C.Maintaining physical security of the datacenter where the servers are hosted

D.Managing application-level user authentication and authorization

AnswerC

This is correct. Under the shared responsibility model, Microsoft is responsible for the physical security of its datacenters, including access controls, surveillance, and environmental controls. This is a core responsibility of the cloud provider.

Why this answer

Under the shared responsibility model for IaaS, Microsoft is responsible for the physical security of its datacenters, including access controls, surveillance, and environmental safeguards. This is a foundational layer that customers cannot manage, making option C correct.

Exam trap

The trap here is that candidates often confuse Microsoft's responsibility for the physical infrastructure with customer-managed tasks like OS patching or firewall rules, leading them to incorrectly select options A or B.

How to eliminate wrong answers

Option A is wrong because configuring operating system firewalls (e.g., Windows Firewall or iptables) is a customer responsibility, as the customer manages the VM's OS and network settings. Option B is wrong because patching the guest OS (e.g., applying Windows Update or apt-get upgrades) falls to the customer, not Microsoft, who only patches the underlying hypervisor and host infrastructure. Option D is wrong because managing application-level user authentication and authorization (e.g., using Azure AD or custom identity providers) is the customer's duty, as Microsoft provides the platform but not the application logic.

Practice this question →

249

MCQhard

A company is moving to the cloud to achieve economies of scale. Which of the following best describes how cloud computing enables economies of scale?

A.Cloud providers purchase large quantities of hardware, reducing per-unit costs, which are passed to customers.

B.Customers can reserve resources in advance for a discount.

C.Multiple customers share the same physical hardware, reducing security.

D.Customers only pay for resources they use, reducing waste.

AnswerA

This is the core mechanism of economies of scale in cloud computing: bulk purchasing and operational efficiencies lower costs.

Why this answer

Economies of scale in cloud computing are achieved because providers like AWS, Microsoft Azure, or Google Cloud purchase hardware (servers, networking gear, storage) in massive volumes, negotiating lower per-unit costs from vendors. These savings are passed to customers via lower pay-as-you-go prices, making cloud services cheaper than what an individual company would pay for equivalent on-premises infrastructure.

Exam trap

The trap here is that candidates confuse customer-facing benefits (like pay-as-you-go or reserved instances) with the provider-side economic principle of economies of scale, leading them to select options B or D instead of recognizing that bulk purchasing power is the core enabler.

How to eliminate wrong answers

Option B is wrong because reserving resources in advance for a discount (e.g., Azure Reserved Instances) is a pricing model that offers cost savings, but it does not describe how cloud computing enables economies of scale at the provider level. Option C is wrong because while multi-tenancy involves sharing physical hardware, the statement incorrectly claims this reduces security; in reality, cloud providers implement strong isolation (e.g., hypervisor-level separation, virtual networks) to maintain security. Option D is wrong because paying only for resources used (the consumption-based model) reduces waste for the customer, but it is not the mechanism by which the cloud provider achieves economies of scale.

Practice this question →

250

MCQeasy

A startup company plans to move its e-commerce application to Azure. The startup has limited upfront capital and expects demand to be unpredictable initially. The key requirement is that the company should only be charged for the compute and storage resources it actually uses, with the ability to pay per hour or per minute. This requirement directly maps to which fundamental benefit of cloud computing?

A.High availability – redundant infrastructure ensures the application stays online.

B.Elasticity – resources can automatically scale out and in based on demand.

C.Consumption-based pricing – customers pay only for the resources they consume, with no upfront costs.

D.Disaster recovery – data and applications are backed up to another region.

AnswerC

Consumption-based pricing (pay-as-you-go) allows the startup to avoid capital expenditure and pay per hour or per minute for actual usage. This directly matches the requirement of charging only for resources used.

Why this answer

Option C is correct because the startup's requirement to pay only for the compute and storage resources it actually uses, with per-hour or per-minute billing and no upfront capital, directly maps to consumption-based pricing. This cloud benefit eliminates the need for large initial investments and aligns costs with actual usage, which is ideal for unpredictable demand scenarios.

Exam trap

The trap here is that candidates often confuse elasticity (the ability to scale resources) with consumption-based pricing (the billing model), but elasticity addresses dynamic resource adjustment, not the financial aspect of paying only for what you use.

How to eliminate wrong answers

Option A is wrong because high availability focuses on redundant infrastructure to keep the application online, not on the billing model or cost structure based on actual resource consumption. Option B is wrong because elasticity refers to the ability to automatically scale resources up or down based on demand, which addresses unpredictable workloads but does not inherently define the pay-per-use billing mechanism. Option D is wrong because disaster recovery involves backing up data and applications to another region for business continuity, which is unrelated to the financial model of paying only for consumed resources.

Practice this question →

251

MCQeasy

Which cloud computing characteristic allows a single set of physical hardware to serve multiple customers with isolated virtual environments?

A.High availability

B.Geo-distribution

C.Multi-tenancy

D.Elasticity

AnswerC

Multi-tenancy allows multiple customers to share the same physical hardware with logical isolation through virtualization.

Why this answer

Multi-tenancy is the cloud computing characteristic that enables a single set of physical hardware to host multiple customers (tenants) while keeping their virtual environments isolated from one another. This is achieved through hypervisor-level virtualization, where each tenant runs in its own virtual machine (VM) with dedicated memory, CPU, and storage allocations, preventing cross-tenant access. In Azure, multi-tenancy is fundamental to the public cloud model, allowing shared infrastructure without compromising security or privacy.

Exam trap

The trap here is that candidates often confuse multi-tenancy with high availability or elasticity, thinking that sharing hardware implies redundancy or scaling, but the core concept is about logical isolation of tenants on shared physical infrastructure.

How to eliminate wrong answers

Option A is wrong because high availability refers to redundant infrastructure and failover mechanisms (e.g., availability zones, load balancers) that ensure uptime, not the isolation of multiple customers on shared hardware. Option B is wrong because geo-distribution involves deploying resources across multiple geographic regions for latency and disaster recovery, not the logical separation of tenants on a single physical host. Option D is wrong because elasticity is the ability to automatically scale resources up or down based on demand, which is unrelated to the isolation of virtual environments for different customers.

Practice this question →

252

MCQeasy

A company is moving its on-premises data center to the cloud. Previously, they purchased servers and paid for maintenance. Now they pay a monthly subscription for compute and storage based on actual usage. This is an example of shifting from capital expenditure (CapEx) to which type of expenditure?

A.Operating expenditure (OpEx)

B.Variable expenditure

C.Direct expenditure

D.Indirect expenditure

AnswerA

OpEx is the ongoing cost for services, aligned with pay-as-you-go cloud billing.

Why this answer

This scenario describes a shift from upfront capital investment in physical servers and maintenance (CapEx) to a pay-as-you-go model where costs are incurred based on actual usage. In cloud computing, this is the definition of operating expenditure (OpEx), as the company pays a recurring monthly subscription for compute and storage resources rather than making a large initial purchase.

Exam trap

The trap here is that candidates may confuse 'variable expenditure' with OpEx because cloud costs can fluctuate, but the exam specifically tests the accounting distinction between CapEx (upfront capital) and OpEx (ongoing operational costs) as defined in Microsoft's cloud economics model.

How to eliminate wrong answers

Option B (Variable expenditure) is wrong because while cloud costs can vary with usage, 'variable expenditure' is not a standard accounting classification; the correct classification for ongoing operational costs is OpEx. Option C (Direct expenditure) is wrong because direct expenditure refers to costs directly tied to producing a specific product or service, not the general shift from capital to operational spending. Option D (Indirect expenditure) is wrong because indirect expenditure covers overhead costs like utilities or rent, not the consumption-based pricing model of cloud services.

Practice this question →

253

MCQeasy

What does 'pay-as-you-grow' mean in the context of cloud computing for a growing business?

A.Paying for maximum capacity upfront to ensure future needs are met

B.Scaling resources incrementally as the business grows, paying proportionally with growth

C.Getting unlimited resources free until the business reaches a profitable stage

D.Getting discounts that increase as you purchase more cloud resources

AnswerB

Cloud enables starting small and growing resources — and costs — incrementally in step with business growth.

Why this answer

B is correct because 'pay-as-you-grow' describes the ability to incrementally add cloud resources (compute, storage, networking) as demand increases, with costs scaling proportionally. This aligns with the cloud's consumption-based model, where you pay only for what you use, avoiding large upfront capital expenditures. For a growing business, this means you can start small and expand seamlessly without over-provisioning.

Exam trap

The trap here is confusing 'pay-as-you-grow' with volume-based discounts (Option D), which are a separate pricing model (e.g., reserved capacity) and not about incremental resource scaling with business growth.

How to eliminate wrong answers

Option A is wrong because paying for maximum capacity upfront contradicts the cloud's elastic, pay-per-use model; it represents a traditional on-premises capital expenditure approach, not a cloud benefit. Option C is wrong because cloud providers do not offer unlimited free resources until profitability; free tiers are limited in scope (e.g., 12 months, specific services) and never unlimited. Option D is wrong because while volume discounts exist (e.g., reserved instances or savings plans), 'pay-as-you-grow' specifically refers to scaling costs with usage, not discount tiers based on purchase volume.

Practice this question →

254

MCQmedium

A retail company runs an e-commerce application on Azure virtual machines during peak holiday seasons. The application experiences high traffic for a few weeks each year. The IT team wants to automatically provision additional compute resources during high demand and remove them when demand drops, ensuring that the company only pays for resources while they are actively in use. Which cloud computing characteristic does this approach primarily rely on?

A.Elasticity

B.Scalability

C.High availability

D.Fault tolerance

AnswerA

Elasticity is correct. It refers to the ability to automatically scale resources up or down based on real-time demand, ensuring you only pay for what you use. This matches the scenario of adding resources during holiday peaks and removing them afterward.

Why this answer

This approach relies on elasticity, which is the ability of a cloud system to automatically scale resources up or down based on real-time demand. In this scenario, Azure virtual machines are provisioned during peak holiday traffic and deprovisioned when demand drops, ensuring the company only pays for resources while they are actively in use. Elasticity specifically handles dynamic, short-term fluctuations, whereas scalability is a broader term for handling long-term growth.

Exam trap

The trap here is that candidates often confuse elasticity with scalability, but elasticity specifically implies automatic, dynamic scaling in response to real-time demand changes, while scalability is a broader capability that may require manual intervention or be used for planned growth.

How to eliminate wrong answers

Option B (Scalability) is wrong because scalability refers to the ability to increase or decrease resources to handle long-term growth or planned changes, not the automatic, real-time provisioning and deprovisioning described in the scenario. Option C (High availability) is wrong because high availability focuses on ensuring application uptime and resilience through redundancy (e.g., multiple VMs in an availability set), not on dynamic resource allocation based on demand. Option D (Fault tolerance) is wrong because fault tolerance is about maintaining system operation despite component failures (e.g., using redundant servers or automatic failover), not about scaling resources in response to traffic fluctuations.

Practice this question →

255

MCQeasy

A company hosts a customer relationship management (CRM) application on Azure virtual machines. The sales team needs to access the CRM from various locations, including the airport, home, and client offices, using company-issued laptops and personal mobile devices. The application is accessible via a standard web browser over the internet without requiring any special client software or dedicated network connections. Which fundamental characteristic of cloud computing does this scenario primarily demonstrate?

A.On-demand self-service

B.Broad network access

C.Resource pooling

D.Rapid elasticity

AnswerB

Broad network access means that cloud resources are available over the network through standard mechanisms (e.g., web browser, SSH, RDP) from a variety of client platforms (laptops, mobile phones, tablets). The scenario explicitly describes salespeople accessing the CRM via standard web browsers from any location, without special client software, which perfectly matches this characteristic.

Why this answer

The scenario describes users accessing the CRM application from various locations (airport, home, client offices) using different devices (company laptops and personal mobile phones) over the internet via a standard web browser without special client software or dedicated network connections. This directly maps to the cloud computing characteristic of broad network access, which is defined by NIST SP 800-145 as resources that are available over the network and accessed through standard mechanisms (e.g., web browsers, HTTPS) that promote use by heterogeneous client platforms (e.g., mobile phones, laptops, workstations).

Exam trap

The trap here is that candidates confuse 'broad network access' with 'on-demand self-service' because both involve user interaction over the internet, but on-demand self-service specifically requires the user to provision or manage resources themselves, not just consume an existing application.

How to eliminate wrong answers

Option A is wrong because on-demand self-service refers to a consumer's ability to unilaterally provision computing capabilities (e.g., spinning up a VM) without requiring human interaction with the service provider, which is not demonstrated in the scenario where users are simply accessing an already-deployed CRM application. Option C is wrong because resource pooling describes the provider's ability to serve multiple customers from shared physical and virtual resources that are dynamically assigned and reassigned according to consumer demand, which is an internal provider capability not directly observable by the sales team accessing the CRM from various locations.

Practice this question →

256

MCQmedium

A company is evaluating moving its on-premises applications to the cloud. The IT manager wants to avoid upfront hardware costs and instead pay for resources on a monthly basis based on usage. Which cloud characteristic enables this financial model?

A.Consumption-based pricing

B.Measured service

C.Rapid elasticity

D.Resource pooling

AnswerA

This model allows you to pay only for the resources you use, converting capital expenditure to operational expenditure.

Why this answer

Consumption-based pricing is the cloud characteristic that allows organizations to pay only for the resources they actually use, such as compute hours, storage GBs, or data transfer, without any upfront hardware costs. This model shifts IT spending from a capital expenditure (CapEx) to an operational expenditure (OpEx), aligning costs directly with usage. The IT manager's requirement to avoid upfront costs and pay monthly based on usage is the exact definition of consumption-based pricing.

Exam trap

The trap here is that candidates confuse 'measured service' (the telemetry and billing mechanism) with 'consumption-based pricing' (the financial model), but the question explicitly asks for the characteristic that enables the described financial model, not the technical feature that tracks usage.

How to eliminate wrong answers

Option B (Measured service) is wrong because measured service refers to the cloud provider's ability to monitor, control, and report resource usage for billing and optimization purposes, but it does not inherently define the financial model of paying only for what you use; it is the mechanism that enables consumption-based pricing, not the financial model itself. Option C (Rapid elasticity) is wrong because rapid elasticity describes the ability to automatically scale resources up or down based on demand, which supports cost efficiency but does not directly address the financial model of avoiding upfront costs and paying monthly based on usage.

Practice this question →

257

MCQmedium

A development team frequently needs to create and tear down test environments. In their on-premises datacenter, they must submit a ticket to the IT operations team, which often takes several days to provision the required servers. After migrating to Azure, developers can now create virtual machines, databases, and other resources directly through the Azure portal or using PowerShell scripts, without any interaction from the IT operations team. This ability to provision cloud resources directly is a direct example of which fundamental characteristic of cloud computing?

A.Resource pooling

B.Measured service

C.On-demand self-service

D.Rapid elasticity

AnswerC

On-demand self-service enables users to unilaterally provision computing capabilities as needed without requiring human interaction from the service provider. This matches the scenario where developers provision resources directly via the portal or scripts.

Why this answer

Option C is correct because the scenario describes developers provisioning virtual machines, databases, and other resources directly through the Azure portal or PowerShell scripts without needing to interact with the IT operations team. This is the definition of on-demand self-service, a core characteristic of cloud computing defined by NIST (SP 800-145) as a consumer being able to unilaterally provision computing capabilities without requiring human interaction with each service provider.

Exam trap

The trap here is that candidates often confuse 'rapid elasticity' with the ability to quickly provision resources, but rapid elasticity specifically refers to automatic scaling in response to load, not the manual self-service provisioning described in the scenario.

How to eliminate wrong answers

Option A is wrong because resource pooling refers to the provider's multi-tenant model where physical and virtual resources are dynamically assigned and reassigned according to consumer demand, not the ability for users to provision resources themselves. Option B is wrong because measured service involves metering and reporting resource usage for billing and optimization (e.g., Azure Monitor metrics), not the self-provisioning capability. Option D is wrong because rapid elasticity describes the ability to automatically scale resources up or down quickly in response to demand (e.g., autoscaling virtual machine scale sets), not the direct provisioning action by the user.

Practice this question →

258

MCQmedium

A company is migrating its on-premises virtual machines (VMs) to Azure using the Infrastructure as a Service (IaaS) model. The VMs run a custom legacy application that requires specific OS-level configurations. The company's IT team wants to understand which party is responsible for applying operating system security patches after the migration. According to the shared responsibility model, who is responsible for patching the OS of the Azure VMs?

A.Microsoft is fully responsible for applying OS patches to the virtual machines.

B.The company is responsible for patching the operating system on the virtual machines.

C.Responsibility is shared equally between Microsoft and the company for OS patching.

D.Responsibility depends on whether the VM uses Windows or Linux; Microsoft patches Windows VMs and the company patches Linux VMs.

AnswerB

Correct. Even though the VMs run on Azure infrastructure, the guest OS is managed by the customer. Patching the OS is part of the customer's responsibility under the shared responsibility model for IaaS.

Why this answer

In the shared responsibility model for IaaS, the customer retains control over the operating system, including applying security patches. Microsoft manages the physical host, hypervisor, and Azure infrastructure, but the customer is responsible for OS-level configurations and updates on their virtual machines. This applies to both Windows and Linux VMs, regardless of whether the OS is provided by Azure or the customer.

Exam trap

The trap here is that candidates often assume Microsoft patches everything in the cloud, but the shared responsibility model clearly delineates that OS patching in IaaS is the customer's duty, not Microsoft's.

How to eliminate wrong answers

Option A is wrong because Microsoft is not responsible for OS patching in IaaS; they only patch the underlying hypervisor and physical infrastructure. Option C is wrong because responsibility is not shared equally for OS patching; the customer has full responsibility for the OS, while Microsoft handles the host-level security.

Practice this question →

259

MCQmedium

A cloud provider purchases hardware in bulk and shares physical infrastructure among many customers, which allows them to offer lower prices per customer. This benefit is known as:

A.Elasticity

B.Resource pooling

C.Economies of scale

D.High availability

AnswerC

This is the cost advantage achieved from large-scale operations and bulk purchasing.

Why this answer

Option C is correct because economies of scale refer to the cost advantage that cloud providers achieve by purchasing hardware in bulk and sharing physical infrastructure across many customers. This reduces the per-unit cost of compute, storage, and networking resources, enabling providers to offer lower prices per customer. The scenario directly describes the cost benefits of large-scale operations, which is the defining characteristic of economies of scale.

Exam trap

The trap here is that candidates confuse resource pooling (the multi-tenant sharing of infrastructure) with the cost advantage of economies of scale, but resource pooling describes the architectural model while economies of scale describe the financial benefit from large-scale purchasing.

How to eliminate wrong answers

Option A is wrong because elasticity is the ability to automatically scale resources up or down based on demand, not the cost benefit from bulk purchasing and shared infrastructure. Option B is wrong because resource pooling refers to the multi-tenant model where computing resources are pooled to serve multiple customers, but it does not inherently describe the cost advantage gained from large-scale procurement and operations.

Practice this question →

260

MCQmedium

A company is designing a multi-cloud strategy to avoid dependency on a single provider. They need the ability to move workloads between different cloud providers or back to an on-premises environment with minimal rework. Which cloud characteristic is most essential for this goal?

A.Elasticity

B.Scalability

C.Portability

D.Fault tolerance

AnswerC

Correct. Portability ensures that workloads can be moved with minimal changes, supporting multi-cloud and hybrid strategies.

Why this answer

Portability is the cloud characteristic that enables workloads, data, and applications to be moved across different cloud providers or between cloud and on-premises environments with minimal rework. This is achieved through the use of standardized formats, APIs, and containerization technologies such as Docker and Kubernetes, which abstract underlying infrastructure dependencies. For a multi-cloud strategy aimed at avoiding vendor lock-in, portability is the essential enabler.

Exam trap

The trap here is that candidates confuse elasticity or scalability with portability, mistakenly thinking that the ability to scale resources automatically also implies the ability to move them across providers, but elasticity and scalability are about resource adjustment within a single environment, not cross-environment migration.

How to eliminate wrong answers

Option A is wrong because elasticity refers to the ability to automatically provision and de-provision resources in response to demand, which is about scaling up/down within a single environment, not about moving workloads across providers. Option B is wrong because scalability is the capability to handle increasing workloads by adding resources, which focuses on growth within a given platform, not on workload migration or interoperability between different cloud ecosystems.

Practice this question →

261

MCQeasy

A company currently budgets for maximum capacity to handle peak loads, resulting in underutilized resources during off-peak times. They want a model where they can quickly adjust resources up or down based on demand. Which cloud characteristic directly addresses this concern?

A.Elasticity

B.High availability

C.Geo-redundancy

D.Fault tolerance

AnswerA

Correct. Elasticity enables automatic scaling of resources based on demand, matching capacity to actual usage.

Why this answer

Elasticity is the cloud characteristic that enables automatic scaling of resources up or down in response to real-time demand. This directly addresses the company's need to avoid over-provisioning for peak loads while still being able to handle spikes without manual intervention, typically implemented through auto-scaling policies in services like Azure Virtual Machine Scale Sets or Azure App Service autoscale.

Exam trap

The trap here is that candidates confuse 'high availability' (always-on redundancy) with 'elasticity' (dynamic scaling), but the question explicitly asks about adjusting resources based on demand, not about maintaining uptime during failures.

How to eliminate wrong answers

Option B (High availability) is wrong because it focuses on ensuring uptime and accessibility through redundancy across fault domains or availability zones, not on dynamic resource adjustment based on demand. Option C (Geo-redundancy) is wrong because it refers to replicating data or services across geographically separate regions for disaster recovery, not for scaling resources to match workload fluctuations. Option D (Fault tolerance) is wrong because it describes the ability of a system to continue operating despite component failures, often through redundant hardware or software, rather than the ability to scale resources elastically.

Practice this question →

262

MCQeasy

Which type of expenditure does cloud computing convert infrastructure costs into?

A.Capital expenditure (CapEx)

B.Operational expenditure (OpEx)

C.Research and development expenditure (R&D)

D.Capital and operational expenditure equally

AnswerB

Cloud converts upfront CapEx hardware purchases into recurring OpEx (monthly service fees) based on consumption.

Why this answer

Cloud computing converts infrastructure costs from capital expenditure (CapEx) to operational expenditure (OpEx) because you pay for compute, storage, and networking resources on a consumption-based model (pay-as-you-go) rather than purchasing physical hardware upfront. This shift allows organizations to avoid large upfront investments and instead pay for only what they use, aligning costs with actual usage and reducing financial risk.

Exam trap

The trap here is that candidates often confuse CapEx with OpEx, mistakenly thinking cloud still involves significant upfront costs (like reserved instances), but the core concept tested is the fundamental shift from buying hardware (CapEx) to paying for services (OpEx) on a consumption basis.

How to eliminate wrong answers

Option A is wrong because capital expenditure (CapEx) involves upfront purchases of physical assets like servers and data centers, which is the traditional on-premises model, not the cloud model. Option C is wrong because research and development expenditure (R&D) is unrelated to infrastructure cost conversion; it covers innovation and product development costs, not IT resource consumption. Option D is wrong because cloud computing does not split costs equally between CapEx and OpEx; it fundamentally shifts the cost model from CapEx to OpEx, with no significant capital investment in physical infrastructure.

Practice this question →

263

MCQeasy

A company wants to use cloud services to quickly spin up a test environment for a new application, use it for a week, and then delete it. They want to minimize costs by only paying for the compute resources during that week. This scenario best describes which cloud characteristic?

A.Rapid elasticity

B.Measured service

C.Self-service

D.Resource pooling

AnswerC

Self-service allows users to independently provision and manage resources (e.g., VMs, storage) without manual intervention from the provider, enabling quick setup and teardown.

Why this answer

Option C is correct because self-service in cloud computing allows users to provision and de-provision resources (like compute instances) on demand without manual intervention from the cloud provider. In this scenario, the company can spin up a test environment, use it for a week, and delete it, paying only for the compute resources consumed during that period, which aligns with the self-service characteristic where users manage their own resources via a web portal or API.

Exam trap

The trap here is that candidates often confuse 'rapid elasticity' with the ability to quickly provision resources, but rapid elasticity specifically refers to automatic scaling based on load, not manual on-demand provisioning and deletion.

How to eliminate wrong answers

Option A is wrong because rapid elasticity refers to the ability to automatically scale resources up or down based on demand, not the manual provisioning and deletion of a test environment for a fixed duration. Option B is wrong because measured service involves metering resource usage for billing and optimization, but it does not describe the ability to provision and de-provision resources on demand; it is a supporting feature, not the core characteristic. Option D is wrong because resource pooling refers to the provider's multi-tenant model where physical and virtual resources are shared across multiple customers, not the user's ability to spin up and delete resources at will.

Practice this question →

264

MCQmedium

A small business wants to migrate its IT infrastructure to Azure. The owner wants the ability to provision new virtual machines, storage accounts, and databases entirely through a web-based portal, without needing to submit a formal request or wait for an administrator to manually allocate resources. The owner expects resources to be available immediately after configuration. Which characteristic of cloud computing does this scenario best illustrate?

A.On-demand self-service

B.Broad network access

C.Resource pooling

D.Rapid elasticity

AnswerA

Correct. On-demand self-service means a consumer can provision computing capabilities (e.g., virtual machines, storage) as needed automatically without requiring human interaction with each service provider. The scenario where the owner uses the Azure portal to create resources without contacting Microsoft directly perfectly matches this characteristic.

Why this answer

This scenario best illustrates on-demand self-service because the owner can provision virtual machines, storage accounts, and databases through a web-based portal (such as the Azure portal) without requiring human interaction with the cloud provider's administrators. The key characteristic is that resources are available immediately after configuration, eliminating the need for formal requests or manual allocation, which is the essence of on-demand self-service as defined by NIST SP 800-145.

Exam trap

The trap here is that candidates confuse 'rapid elasticity' with 'on-demand self-service' because both involve speed, but elasticity is about automatic scaling based on load, whereas self-service is about user-initiated provisioning without human intervention.

How to eliminate wrong answers

Option B (Broad network access) is wrong because it refers to the ability to access cloud resources over the network using standard protocols (e.g., HTTPS, SSH, RDP) from various devices, not the ability to provision resources without administrative intervention. Option C (Resource pooling) is wrong because it describes the provider's multi-tenant model where physical and virtual resources are pooled to serve multiple customers, not the user's ability to self-provision. Option D (Rapid elasticity) is wrong because it focuses on the ability to automatically scale resources up or down based on demand, not the immediate provisioning of resources through a self-service portal.

Practice this question →

265

MCQmedium

A company runs a legacy database on a single Azure virtual machine. The database is experiencing performance issues as the dataset grows. The IT team decides to increase the virtual machine size from Standard_D2s_v3 (2 vCPUs, 8 GB RAM) to Standard_D8s_v3 (8 vCPUs, 32 GB RAM) to improve performance. This process is an example of which cloud computing concept?

A.Horizontal scaling

B.Vertical scaling

C.Elasticity

D.High availability

AnswerB

Vertical scaling (scaling up) increases the power of an existing resource by adding more CPU, memory, or storage. The IT team is increasing the VM size, which is a classic example of vertical scaling.

Why this answer

Vertical scaling (also known as scaling up) involves increasing the capacity of a single resource, such as adding more vCPUs and RAM to an existing virtual machine. In this scenario, the IT team is resizing the Azure VM from Standard_D2s_v3 to Standard_D8s_v3, which increases the compute and memory resources of the same instance. This directly matches the definition of vertical scaling, where performance is improved by upgrading the existing machine rather than adding more machines.

Exam trap

The trap here is that candidates often confuse vertical scaling with elasticity, mistakenly thinking that any change in resource capacity is elasticity, but elasticity specifically requires automated, dynamic scaling based on demand, not a manual VM resize.

How to eliminate wrong answers

Option A is wrong because horizontal scaling (scaling out) involves adding more virtual machines or instances to distribute the load, not increasing the size of a single VM. Option C is wrong because elasticity refers to the ability to automatically scale resources up or down based on demand, often using autoscaling rules; this scenario describes a manual, one-time resizing of a VM, not an automated, dynamic adjustment to workload changes.

Practice this question →

266

MCQeasy

A company needs to burst compute capacity during a seasonal sale event. They plan to use Azure virtual machines to handle the extra load and then release them after the event. They want to pay only for the extra resources used during that period. Which cloud characteristic best describes this?

A.Elasticity

B.High availability

C.Geo-redundancy

D.Agility

AnswerA

Correct. Elasticity enables rapid scaling out (adding resources) during high demand and scaling in (removing resources) afterward, with consumption-based billing.

Why this answer

Elasticity is the cloud characteristic that allows resources to automatically scale up to meet increased demand and scale down when demand decreases, ensuring you only pay for what you use. In this scenario, the company needs to burst compute capacity for a seasonal sale event and then release the VMs afterward, which is a textbook example of elasticity. This contrasts with other characteristics like high availability or geo-redundancy, which focus on uptime and data replication rather than dynamic scaling.

Exam trap

The trap here is that candidates often confuse elasticity with high availability, mistakenly thinking that adding more VMs for a burst is about keeping the system up, rather than understanding that elasticity is specifically about dynamic scaling to match demand and optimize cost.

How to eliminate wrong answers

Option B is wrong because high availability refers to the ability of a system to remain operational and accessible despite component failures, typically achieved through redundancy and failover mechanisms (e.g., Azure Availability Zones), not by dynamically adding or removing resources to match workload spikes. Option C is wrong because geo-redundancy involves replicating data or services across multiple geographic regions to protect against regional outages or disasters (e.g., Azure Geo-Redundant Storage), which is unrelated to the on-demand scaling and pay-per-use model described in the question.

Practice this question →

267

MCQeasy

A cloud provider offers resources on-demand and measures usage. Customers pay only for what they consume. Which characteristic of cloud computing is this?

A.Measured service

B.Resource pooling

C.Broad network access

D.Rapid elasticity

AnswerA

Measured service is the correct term for usage tracking and pay-per-use billing.

Why this answer

This describes the 'measured service' characteristic, where cloud providers meter resource usage (e.g., compute hours, storage GB, network I/O) and bill customers based on actual consumption. This pay-per-use model is enabled by telemetry and monitoring systems that track metrics like CPU time, bandwidth, and API calls, allowing granular cost allocation.

Exam trap

The trap here is that candidates confuse 'measured service' with 'resource pooling' because both involve shared infrastructure, but measured service specifically focuses on usage tracking and billing, not the underlying multi-tenant architecture.

How to eliminate wrong answers

Option B (Resource pooling) is wrong because it refers to the provider's ability to serve multiple customers from shared physical resources using multi-tenancy, not the billing or usage measurement model. Option C (Broad network access) is wrong because it describes the availability of resources over the network via standard protocols (e.g., HTTP, HTTPS, SSH) from various devices, not the metering or consumption-based payment.

Practice this question →

268

MCQeasy

A company wants to move their on-premises infrastructure to the cloud to avoid the large upfront cost of purchasing new servers every three years. In the cloud, they will pay only for the server capacity they use, with no long-term commitment. This shift from upfront investment to variable expense is an example of which cloud benefit?

A.Consumption-based pricing

B.Economies of scale

C.Capacity planning

D.Reserved capacity

AnswerA

Correct. Consumption-based pricing means you pay only for the resources you consume, avoiding large upfront capital expenses.

Why this answer

Consumption-based pricing is a cloud model where customers pay only for the resources they actually use (e.g., compute hours, storage GBs) with no upfront costs or long-term commitments. This directly matches the scenario of avoiding large upfront server purchases and paying only for capacity used, shifting from a capital expenditure (CapEx) to an operational expenditure (OpEx) model.

Exam trap

The trap here is confusing 'consumption-based pricing' with 'reserved capacity' — candidates often think any cost-saving model involves a commitment, but the question explicitly states 'no long-term commitment,' making reserved capacity the wrong choice.

How to eliminate wrong answers

Option B (Economies of scale) is wrong because it refers to cost reductions achieved by cloud providers through massive infrastructure deployment, not the customer's shift from upfront investment to variable expense. Option C (Capacity planning) is wrong because it describes the process of predicting future resource needs, not the pricing model that eliminates upfront costs. Option D (Reserved capacity) is wrong because it involves a long-term commitment (typically 1 or 3 years) for discounted rates, which contradicts the 'no long-term commitment' requirement in the question.

Practice this question →

269

MCQmedium

A company runs a web application in Azure that experiences variable traffic throughout the day. During peak hours, the application becomes slow because the existing virtual machine (VM) cannot handle the increased load. The solution architect proposes adding more VMs of the same size and distributing incoming requests across all of them to balance the load. Which scaling concept does this approach represent?

A.Vertical scaling

B.Horizontal scaling

C.Elastic scaling

D.Disaster recovery

AnswerB

Horizontal scaling (scaling out) involves adding more instances of the same resource type and distributing the workload among them. This is exactly what is described: adding more VMs of the same size and using load balancing to distribute traffic.

Why this answer

Horizontal scaling (also known as scaling out) involves adding more virtual machines of the same size to distribute incoming traffic across them. In this scenario, adding more VMs of the same size and using a load balancer to distribute requests directly matches the definition of horizontal scaling, which increases system capacity by adding more instances rather than increasing the power of a single instance.

Exam trap

The trap here is that candidates often confuse 'horizontal scaling' with 'elastic scaling' because both involve adding resources, but elastic scaling is an automated behavior (autoscaling) that can implement either horizontal or vertical scaling, not a distinct scaling concept itself.

How to eliminate wrong answers

Option A is wrong because vertical scaling (scaling up) would involve increasing the size or resources (CPU, RAM) of the existing single VM, not adding additional VMs of the same size. Option C is wrong because elastic scaling is not a distinct scaling concept in Azure; it refers to the ability to automatically scale resources up or down based on demand, which is an operational characteristic (often enabled by autoscale) rather than a specific scaling method like horizontal or vertical.

Practice this question →

270

MCQmedium

A company runs a mission-critical application on Azure virtual machines. The application is hosted in the East US Azure region. To protect against a regional disaster, the company configures Azure Site Recovery to replicate the VMs to a secondary region (West US). If a disaster occurs in East US, the company can initiate a failover to West US and bring the application back online within minutes using the replicated data. Which cloud computing benefit does this scenario best demonstrate?

A.Elasticity

B.Pay-as-you-go pricing

C.Disaster recovery and business continuity

D.Geo-redundancy

AnswerC

Correct. Disaster recovery and business continuity ensure that applications can be restored quickly after a disruptive event. This is a major cloud advantage, as it allows organizations to implement robust DR without significant upfront capital investment.

Why this answer

Option C is correct because Azure Site Recovery provides disaster recovery and business continuity by replicating Azure VMs from the primary region (East US) to a secondary region (West US). In the event of a regional disaster, failover can be initiated to bring the application online within minutes using the replicated data, ensuring minimal downtime and data loss. This directly aligns with the cloud benefit of disaster recovery and business continuity, which focuses on maintaining operations during catastrophic failures.

Exam trap

The trap here is that candidates confuse disaster recovery and business continuity with elasticity, because both involve scaling or moving resources, but elasticity is about dynamic scaling based on load, not about replicating data for failover during a disaster.

How to eliminate wrong answers

Option A is wrong because elasticity refers to the ability to automatically scale resources up or down based on demand, such as adding more VM instances during peak traffic, not replicating VMs for disaster recovery. Option B is wrong because pay-as-you-go pricing is a consumption-based billing model where you pay only for the resources you use, not a benefit related to protecting against regional disasters or ensuring application availability.

Practice this question →

271

MCQmedium

Which type of cloud service model would a company typically use for hosting their own custom web application where they manage the code but not the server operating system?

A.IaaS (Infrastructure as a Service)

B.PaaS (Platform as a Service)

C.SaaS (Software as a Service)

D.FaaS (Function as a Service)

AnswerB

PaaS lets developers deploy custom app code without managing OS or server infrastructure (Azure App Service).

Why this answer

PaaS (Platform as a Service) is correct because the company manages only the application code and data, while the cloud provider handles the underlying server operating system, runtime, middleware, and infrastructure. This aligns with the scenario where the customer controls the custom web application but not the OS.

Exam trap

The trap here is that candidates confuse PaaS with IaaS because they think 'managing the code' implies full control over the server, but PaaS still abstracts the OS while IaaS requires OS management.

How to eliminate wrong answers

Option A is wrong because IaaS provides virtualized servers where the customer manages the OS, patches, and middleware, not just the code. Option C is wrong because SaaS delivers fully managed applications (e.g., Office 365) where the customer has no control over the code or OS. Option D is wrong because FaaS (Function as a Service) is an event-driven compute model for running individual functions, not for hosting a full custom web application with persistent code management.

Practice this question →

272

MCQmedium

A hospital stores patient data in the cloud. The hospital is responsible for encrypting the data before uploading, managing user access, and complying with healthcare regulations. The cloud provider is responsible for securing the physical datacenter, network infrastructure, and hypervisor. This model describes which concept?

A.Shared responsibility model

B.Infrastructure as a Service (IaaS)

C.Platform as a Service (PaaS)

D.Software as a Service (SaaS)

AnswerA

Correct. It describes the division of security responsibilities between provider and customer.

Why this answer

The scenario explicitly divides security responsibilities between the hospital (data encryption, access management, regulatory compliance) and the cloud provider (physical datacenter, network, hypervisor). This division of security obligations is the core definition of the shared responsibility model, which applies across all cloud service models (IaaS, PaaS, SaaS) but is most clearly illustrated here where the customer retains control over data and identity layers.

Exam trap

The trap here is that candidates confuse the shared responsibility model with a specific service model (IaaS, PaaS, or SaaS), but the question is about the security accountability framework itself, not the type of cloud service being consumed.

How to eliminate wrong answers

Option B (IaaS) is wrong because IaaS describes a service model where the provider offers virtualized computing resources, not a security responsibility framework; the question focuses on who manages what, not the type of service delivered. Option C (PaaS) is wrong because PaaS shifts more responsibility to the provider (runtime, middleware) but still doesn't define the security boundary concept itself; the question's split of duties is the model, not the platform layer. Option D (SaaS) is wrong because SaaS offloads nearly all security to the provider, contradicting the hospital's active role in encryption and access management; the scenario's explicit separation of duties is the shared responsibility model, not a specific service category.

Practice this question →

273

MCQmedium

A hospital is subject to strict data residency laws that require patient data to remain within the country's borders. They are considering using a public cloud provider. Which cloud deployment model would best meet this compliance requirement?

A.Public cloud

B.Private cloud

C.Hybrid cloud

D.Community cloud

AnswerB

A private cloud is dedicated to a single organization, providing maximum control over data location and compliance.

Why this answer

A private cloud is dedicated to a single organization, allowing the hospital to deploy and manage infrastructure within its own data center or a colocation facility located within the country's borders. This ensures full control over data storage and processing, directly satisfying data residency laws that prohibit patient data from leaving the country. In contrast, public cloud providers may have data centers in multiple regions, making it harder to guarantee data never crosses borders.

Exam trap

The trap here is that candidates often choose hybrid cloud thinking it offers the best of both worlds, but they overlook that the public cloud component could inadvertently store or process data outside the required geographic boundary, violating strict data residency laws.

How to eliminate wrong answers

Option A is wrong because a public cloud shares physical infrastructure across multiple tenants and typically offers data center regions that may be outside the required country, making it difficult to guarantee strict data residency without complex policy configurations. Option C is wrong because a hybrid cloud combines public and private clouds, and if any workload or data storage extends to the public cloud portion, it could violate data residency laws unless the public cloud component is also restricted to in-country regions, which adds complexity and risk. Option D is wrong because a community cloud is shared by several organizations with common concerns (e.g., healthcare), but it does not inherently enforce data residency within a specific country unless all participating organizations and the cloud infrastructure are physically located within that country, which is not guaranteed.

Practice this question →

274

MCQmedium

A company runs a legacy application on-premises that cannot be migrated to the cloud due to strict data sovereignty laws requiring customer data to remain within the country's physical borders. The company wants to use Azure's advanced analytics services to gain insights from the data. They plan to keep the data on-premises but run the analytics workloads in Azure. Which cloud deployment model should they use?

A.Public cloud

B.Private cloud

C.Hybrid cloud

D.Community cloud

AnswerC

A hybrid cloud connects on-premises infrastructure with public cloud services, enabling the company to keep sensitive data on-premises while using Azure for analytics. This satisfies the data sovereignty requirement and the need for Azure services.

Why this answer

The hybrid cloud model is correct because it combines on-premises infrastructure (for data sovereignty compliance) with Azure's public cloud services (for advanced analytics). This allows the company to keep customer data within the country's physical borders while leveraging Azure's analytics workloads, such as Azure Synapse Analytics or Azure Machine Learning, without migrating the data to the cloud.

Exam trap

The trap here is that candidates often confuse hybrid cloud with public cloud, assuming that any use of Azure services automatically means a public cloud deployment, but hybrid cloud specifically addresses scenarios where data must remain on-premises due to compliance or regulatory requirements.

How to eliminate wrong answers

Option A is wrong because a public cloud model would require the data to be stored and processed entirely in Azure's data centers, which violates the data sovereignty laws mandating that customer data remain within the country's physical borders. Option B is wrong because a private cloud model, while offering dedicated infrastructure, would not provide access to Azure's advanced analytics services unless it is a fully on-premises Azure Stack deployment, which still requires data to be processed locally and does not leverage the public cloud's analytics capabilities as described.

Practice this question →

275

MCQeasy

A company is evaluating moving its on-premises datacenter to Azure. The CFO points out that Microsoft purchases servers, networking equipment, and cooling systems in enormous quantities, enabling them to negotiate lower prices from hardware vendors. The company expects to benefit from these lower hardware costs as it migrates. Which cloud computing benefit does this scenario primarily describe?

A.Elasticity

B.High availability

C.Economies of scale

D.Measured service

AnswerC

Economies of scale mean that the average cost per unit decreases as the volume of production increases. Microsoft's massive scale allows it to obtain hardware at lower per-unit costs, which translates into lower prices for customers. This is the benefit described in the scenario.

Why this answer

The scenario describes how Microsoft's massive purchasing power reduces per-unit costs for hardware like servers and cooling systems, which is the definition of economies of scale. This benefit is passed to customers through lower Azure service prices, not through any operational or architectural feature of the cloud itself.

Exam trap

The trap here is confusing economies of scale (a financial benefit from bulk purchasing) with elasticity (a technical scaling feature), as both involve 'scaling' but in completely different contexts.

How to eliminate wrong answers

Option A is wrong because elasticity refers to the ability to automatically scale resources up or down based on demand, not to cost savings from bulk hardware procurement. Option B is wrong because high availability ensures that applications remain operational despite failures, typically through redundancy across multiple datacenters, which is unrelated to hardware cost reductions.

Practice this question →

276

MCQmedium

A company wants to ensure their application remains available even if an entire Azure region experiences an outage. Which Azure feature should they implement?

A.Availability sets

B.Availability zones

C.Region pairs

D.Load balancer

AnswerC

Region pairs provide cross-region disaster recovery and are designed for regional outages.

Why this answer

Region pairs are designed to provide resilience against a complete Azure region outage by pairing each region with another region in the same geography (e.g., East US paired with West US). If one region fails, Azure can fail over services like storage (GRS) and SQL Database (Geo-Replication) to the paired region, ensuring application availability. This is the only option that protects against an entire region failure, as it leverages physically separate datacenters with independent power, cooling, and networking.

Exam trap

The trap here is that candidates confuse Availability zones (which protect against datacenter failures within a region) with Region pairs (which protect against full region outages), and they often overlook that Availability zones cannot survive a complete region failure because they share the same regional boundary.

How to eliminate wrong answers

Option A is wrong because Availability sets protect against failures within a single datacenter (e.g., rack or update domain failures) but do not protect against a full region outage. Option B is wrong because Availability zones protect against failures within a single region (e.g., a datacenter failure) by distributing VMs across isolated zones, but they cannot survive a complete region outage since all zones are in the same region. Option D is wrong because a Load balancer distributes traffic across healthy resources within a region but does not provide cross-region failover or protection against a region-wide outage.

Practice this question →

277

MCQeasy

A company is considering moving its IT infrastructure to the cloud. The CFO wants to understand the financial impact: instead of purchasing servers and paying for maintenance, the company will pay a monthly fee based on usage. This shift represents moving from which type of expenditure to which?

A.From capital expenditure (CapEx) to operational expenditure (OpEx)

B.From operational expenditure (OpEx) to capital expenditure (CapEx)

C.From direct expenditure to indirect expenditure

D.From variable expenditure to fixed expenditure

AnswerA

This is the classic financial model shift in cloud computing, where upfront hardware costs are replaced by ongoing operational costs.

Why this answer

This shift represents moving from capital expenditure (CapEx) to operational expenditure (OpEx). CapEx involves upfront costs for physical assets like servers, which depreciate over time, while OpEx involves ongoing, usage-based payments for cloud services. In Azure, this aligns with the consumption-based model where you pay only for resources consumed (e.g., VM hours, storage GBs), eliminating large initial investments and shifting financial risk to the provider.

Exam trap

The trap here is that candidates confuse the financial terms and select 'From OpEx to CapEx' (Option B) because they mistakenly think cloud costs are capital expenses due to long-term commitments like Reserved Instances, but the core shift is from upfront hardware purchases (CapEx) to ongoing service payments (OpEx).

How to eliminate wrong answers

Option B is wrong because it reverses the financial model: moving from OpEx to CapEx would mean transitioning from ongoing operational costs to upfront capital purchases, which is the opposite of cloud adoption. Option C is wrong because 'direct expenditure' and 'indirect expenditure' are not standard accounting classifications for cloud cost models; the correct terms are CapEx and OpEx, which are defined by GAAP and IFRS. Option D is wrong because cloud costs are typically variable (usage-based), not fixed; moving from fixed costs (e.g., owned servers with constant depreciation) to variable costs (pay-per-use) is a key benefit, but the question specifically asks about CapEx vs.

OpEx.

Practice this question →

278

MCQeasy

What is 'fault tolerance' in cloud computing?

A.The ability to automatically scale resources during peak usage

B.The ability to continue operating correctly despite component failures

C.The ability to restore data after a major disaster

D.The ability to deploy applications in multiple geographic regions

AnswerB

Fault tolerance means the system keeps working even when individual components fail, thanks to redundancy.

Why this answer

Fault tolerance in cloud computing refers to a system's ability to continue operating correctly, without interruption, even when one or more of its components fail. This is achieved through redundancy—such as duplicate hardware, software, or data paths—so that if a component fails, another automatically takes over without any impact on the user. It is a core design principle for high-availability systems, ensuring zero downtime despite failures.

Exam trap

The trap here is that candidates often confuse 'fault tolerance' with 'disaster recovery' (Option C) or 'high availability' (which is related but not identical), leading them to pick a broader or adjacent concept instead of the precise definition of continued operation during component failures.

How to eliminate wrong answers

Option A is wrong because automatically scaling resources during peak usage describes 'elasticity' or 'autoscaling', not fault tolerance; scaling handles demand changes, not component failures. Option C is wrong because restoring data after a major disaster describes 'disaster recovery' (often involving backup and restore procedures), not the continuous operation during failures that fault tolerance ensures. Option D is wrong because deploying applications in multiple geographic regions describes 'geo-redundancy' or 'multi-region deployment', which is a strategy to support fault tolerance or disaster recovery, but it is not the definition of fault tolerance itself—fault tolerance can be achieved within a single region through redundant components.

Practice this question →

279

MCQmedium

A retail company hosts an e-commerce website on on-premises servers. During seasonal sales events, the website experiences traffic spikes that last for a few hours. Several years ago, the company purchased additional servers to handle these spikes, but those servers now sit idle for most of the year. The company is considering moving the website to Azure. Which benefit of cloud computing would most directly help the company avoid maintaining idle hardware while still being able to handle traffic spikes?

A.High availability

B.Elasticity

C.Disaster recovery

D.Geo-redundancy

AnswerB

Elasticity is the ability of a cloud service to automatically increase or decrease the resources allocated to a workload based on real-time demand. This allows the company to handle traffic spikes without maintaining permanently provisioned hardware, and to pay only for what is used.

Why this answer

Elasticity is the correct answer because it allows the company to automatically scale computing resources up during traffic spikes and scale down when demand drops, eliminating the need to maintain idle on-premises servers. In Azure, this is achieved through features like Virtual Machine Scale Sets and autoscale rules that adjust capacity based on metrics such as CPU usage or request count, ensuring the company only pays for resources consumed during peak periods.

Exam trap

The trap here is that candidates often confuse elasticity with high availability, but high availability ensures uptime during failures, not the ability to dynamically adjust capacity to match variable demand.

How to eliminate wrong answers

Option A is wrong because high availability focuses on ensuring applications remain operational during failures through redundancy (e.g., availability zones), not on dynamically adjusting capacity to match variable demand. Option C is wrong because disaster recovery is about restoring services after a catastrophic failure (e.g., using Azure Site Recovery), not about handling short-lived traffic spikes. Option D is wrong because geo-redundancy replicates data or services across multiple geographic regions for durability and failover, not for scaling resources up and down in response to demand fluctuations.

Practice this question →

280

MCQmedium

A company migrates its on-premises infrastructure to Azure. The IT manager notes that Azure dynamically allocates and reallocates compute and storage resources across multiple customers based on demand, while ensuring each customer's data and workloads remain isolated from others. Which cloud computing characteristic does this describe?

A.Rapid elasticity

B.Resource pooling

C.Measured service

D.On-demand self-service

AnswerB

Resource pooling is the correct answer because the scenario explicitly mentions Azure allocating and reallocating compute and storage resources across multiple customers while maintaining isolation. This is the definition of resource pooling in the NIST cloud computing model.

Why this answer

Resource pooling is the cloud computing characteristic where the provider's computing resources are pooled to serve multiple customers using a multi-tenant model, with physical and virtual resources dynamically assigned and reassigned according to demand. This ensures each customer's data and workloads remain isolated while the provider can efficiently allocate compute and storage across tenants. The scenario directly describes this multi-tenant isolation and dynamic allocation, which is the essence of resource pooling.

Exam trap

The trap here is that candidates confuse 'resource pooling' with 'rapid elasticity' because both involve dynamic allocation, but resource pooling focuses on multi-tenant isolation and shared infrastructure, while rapid elasticity is about scaling speed and flexibility.

How to eliminate wrong answers

Option A is wrong because rapid elasticity refers to the ability to quickly scale resources up or down, not the pooling and isolation of resources across multiple customers. Option C is wrong because measured service involves metering resource usage for billing and optimization, not the dynamic allocation and isolation described. Option D is wrong because on-demand self-service allows users to provision resources without human interaction, but does not cover the multi-tenant pooling or isolation aspect.

Practice this question →

281

MCQmedium

A healthcare organization migrates its patient data management application to Azure. The organization's compliance team learns that Azure's underlying physical infrastructure, including servers and storage, is shared by many customers globally. The team is concerned about data leakage and wants to understand which fundamental cloud computing characteristic allows the provider to share physical hardware among multiple tenants while ensuring that each tenant's data and compute resources remain logically isolated and secure from one another.

A.Rapid elasticity

B.Resource pooling

C.Measured service

D.Broad network access

AnswerB

Resource pooling is the correct characteristic. It means the cloud provider's computing resources are pooled to serve multiple customers using a multi-tenant model, with strict logical isolation so that each tenant's data and processes are secure and private, even though they share the same physical hardware.

Why this answer

Resource pooling is the correct answer because it is the fundamental cloud computing characteristic that enables a provider to serve multiple customers (tenants) from the same physical hardware while maintaining logical isolation. In Azure, this is achieved through hypervisor-level virtualization (e.g., Hyper-V) where each tenant's virtual machines and data are isolated at the kernel and memory level, preventing cross-tenant data leakage even though the underlying servers and storage are shared.

Exam trap

The trap here is that candidates confuse resource pooling with security isolation mechanisms like encryption or firewalls, but the question specifically asks for the fundamental cloud characteristic that enables shared physical hardware with logical isolation, which is resource pooling, not a specific security feature.

How to eliminate wrong answers

Option A is wrong because rapid elasticity refers to the ability to quickly scale resources up or down based on demand, not to multi-tenant isolation or data security. Option C is wrong because measured service involves metering and billing for resource usage (e.g., pay-as-you-go), which is unrelated to logical separation of tenant data on shared hardware. Option D is wrong because broad network access describes the ability to access cloud resources over standard network protocols (e.g., HTTPS, SSH) from various devices, not the mechanism for isolating tenant workloads on shared infrastructure.

Practice this question →

282

MCQmedium

A company runs a critical transaction processing application on two Azure virtual machines. The infrastructure is designed so that if one virtual machine encounters a hardware failure and stops functioning, the other virtual machine continues to serve traffic without any interruption or loss of service. Which cloud computing characteristic does this design primarily address?

A.High availability

B.Fault tolerance

C.Disaster recovery

D.Scalability

AnswerB

Correct. Fault tolerance is the ability of a system to continue operating without interruption even when one or more components fail. The design where a failure of one VM causes no service disruption is a classic example of fault tolerance.

Why this answer

The design ensures that if one virtual machine fails due to a hardware failure, the other continues serving traffic without any interruption or loss of service. This is the definition of fault tolerance, which eliminates any single point of failure and maintains continuous operation even when a component fails. High availability reduces downtime but may allow brief interruptions during failover, whereas fault tolerance guarantees zero interruption.

Exam trap

The trap here is that candidates confuse high availability with fault tolerance, but high availability allows for brief downtime during failover, while fault tolerance guarantees zero interruption, which is the key distinction tested in this question.

How to eliminate wrong answers

Option A is wrong because high availability focuses on minimizing downtime through redundancy and automatic failover, but it typically allows a brief interruption (e.g., seconds to minutes) during the failover process, whereas the scenario explicitly states 'without any interruption or loss of service.' Option C is wrong because disaster recovery involves restoring systems and data after a major disaster (e.g., region-wide outage) from a secondary site, not maintaining continuous service during a local hardware failure. Option D is wrong because scalability refers to the ability to increase or decrease resources to handle varying load, not to maintain service continuity during a hardware failure.

Practice this question →

283

Matchingmedium

Match each Azure networking service to its purpose.

Drag a concept onto its matching description — or click a concept then click the description.

Concepts

Matches

Distribute traffic across VMs

Layer 7 load balancer with WAF

DNS-based traffic routing across regions

Send encrypted traffic between networks

Dedicated private connection to Azure

Why these pairings

These services address different networking and load balancing needs.

Practice this question →

284

MCQmedium

A company is developing a custom web application that will be deployed to Azure. The development team wants to minimize operational overhead and avoid any responsibility for managing the underlying operating system, runtime, or middleware. They want to focus solely on writing application code and managing data. Which cloud service model should the company use for this application?

A.Infrastructure as a Service (IaaS)

B.Platform as a Service (PaaS)

C.Software as a Service (SaaS)

D.Functions as a Service (FaaS)

AnswerB

PaaS abstracts the underlying infrastructure, including the OS and runtime, so the team can focus on application code and data. Azure App Service is a common PaaS offering for web applications.

Why this answer

Platform as a Service (PaaS) is the correct model because it abstracts the underlying OS, runtime, and middleware, allowing developers to focus solely on writing application code and managing data. Azure App Service is a PaaS offering that provides automatic patching, load balancing, and scaling without any responsibility for the host OS or runtime environment. This directly matches the requirement to minimize operational overhead and avoid managing infrastructure layers.

Exam trap

The trap here is that candidates often confuse PaaS with IaaS because they think 'custom application' requires full control over the OS, but the question explicitly states the team wants to avoid managing the OS, runtime, or middleware, which is the defining characteristic of PaaS.

How to eliminate wrong answers

Option A (IaaS) is wrong because it provides virtualized computing resources (e.g., Azure VMs) where the customer is responsible for managing the OS, runtime, and middleware, including patching and configuration, which contradicts the goal of minimizing operational overhead. Option C (SaaS) is wrong because it delivers fully managed software applications (e.g., Office 365) where the customer does not write custom code or manage data at the application layer; the scenario explicitly requires developing a custom web application. Option D (FaaS) is wrong because it is a subset of serverless computing (e.g., Azure Functions) that focuses on event-driven, stateless code execution, but it still requires managing triggers, bindings, and scaling configurations, and does not provide a full runtime environment for a custom web application with persistent data management.

Practice this question →

285

MCQmedium

A manufacturing company traditionally purchased and maintained its own servers, paying a large upfront capital expense (CapEx) for hardware that was expected to last five years. After migrating its workloads to Azure virtual machines, the company now receives a monthly invoice that reflects only the compute and storage resources actually consumed during that month. There are no upfront payments. This change in cost structure best illustrates which benefit of cloud computing?

A.Scalability to handle variable demand

B.High availability through geographic redundancy

C.Consumption-based pricing model

D.Resource pooling through multi-tenancy

AnswerC

This is the correct benefit. The cloud's consumption-based (pay-as-you-go) model eliminates large upfront capital expenses and replaces them with variable operational expenses based on actual resource usage.

Why this answer

The scenario describes a shift from a large upfront capital expenditure (CapEx) for hardware to a monthly invoice based on actual compute and storage consumption. This directly illustrates the consumption-based pricing model, where you pay only for the resources you use (e.g., VM hours, storage GB-months) with no upfront costs. This is a core financial benefit of cloud computing, enabling operational expenditure (OpEx) instead of CapEx.

Exam trap

The trap here is that candidates confuse the financial benefit of consumption-based pricing with the operational benefit of scalability, but the question explicitly contrasts upfront CapEx with monthly usage-based billing, making the pricing model the clear focus.

How to eliminate wrong answers

Option A is wrong because scalability refers to the ability to dynamically increase or decrease resources to handle variable demand, not the change in cost structure from upfront to pay-as-you-go. Option B is wrong because high availability through geographic redundancy involves replicating workloads across multiple Azure regions to ensure uptime, which is unrelated to the payment model described. Option D is wrong because resource pooling through multi-tenancy allows multiple customers to share the same physical infrastructure, driving cost efficiency for the provider, but the question focuses on the customer's billing model, not the provider's infrastructure sharing.

Practice this question →

286

MCQmedium

A company runs a web application on an Azure virtual machine. The application experiences periodic traffic surges during promotional campaigns. To handle the increased load, the IT team manually changes the VM size from Standard_D2s_v3 to Standard_D8s_v3 before each campaign and then changes it back after the campaign ends. Which cloud computing concept does this scenario exemplify?

A.Elasticity

B.Scalability

C.High availability

D.Disaster recovery

AnswerB

Scalability is the ability to allocate more or fewer resources to a workload as needed. The manual resizing of the VM to handle traffic surges and the subsequent reduction is a clear example of vertical scalability.

Why this answer

This scenario exemplifies scalability, specifically vertical scaling (scaling up), because the IT team manually increases the VM size to handle higher demand and then reduces it afterward. Scalability is the ability to adjust resources to meet changing workload demands, which is exactly what occurs when changing from Standard_D2s_v3 to Standard_D8s_v3.

Exam trap

The trap here is that candidates confuse manual scaling with elasticity, but elasticity specifically requires automatic, on-demand resource adjustment without human intervention.

How to eliminate wrong answers

Option A is wrong because elasticity refers to the automatic, dynamic provisioning and de-provisioning of resources in response to real-time demand, whereas this scenario describes a manual, scheduled change. Option C is wrong because high availability ensures that applications remain accessible despite component failures through redundancy (e.g., multiple VMs in an availability set), not by resizing a single VM. Option D is wrong because disaster recovery involves restoring systems and data after a catastrophic failure (e.g., using Azure Site Recovery), not adjusting capacity for traffic surges.

Practice this question →

287

MCQmedium

A company runs a web application on Azure. At the end of each month, the finance team reviews an invoice that itemizes charges by resource type, such as virtual machine compute hours, storage capacity used, and data transfer volume. The total cost directly corresponds to the exact quantity of resources consumed during the billing period. This capability is an example of which fundamental characteristic of cloud computing?

A.Rapid elasticity

B.Measured service

C.Resource pooling

D.On-demand self-service

AnswerB

Measured service means that cloud providers automatically meter and control resource usage, providing transparency for both provider and consumer. This allows a pay-per-use billing model where charges are based on exact consumption, exactly as described in the scenario.

Why this answer

Measured service is the correct answer because it refers to the cloud provider's ability to meter and bill customers based on actual resource consumption. In this scenario, the invoice itemizes charges by resource type (compute hours, storage, data transfer) and the total cost directly corresponds to the exact quantity consumed, which is the defining characteristic of measured service. This capability relies on metering telemetry (e.g., Azure Monitor metrics, usage logs) to track usage and generate a pay-per-use billing model.

Exam trap

The trap here is that candidates often confuse 'measured service' with 'on-demand self-service' because both involve user-driven actions, but measured service specifically focuses on the metering and billing of consumed resources, not the provisioning process.

How to eliminate wrong answers

Option A is wrong because rapid elasticity describes the ability to automatically scale resources up or down in response to demand, not the billing or metering of consumed resources. Option C is wrong because resource pooling refers to the provider's multi-tenant model where physical and virtual resources are dynamically assigned to serve multiple customers, not the itemized billing based on exact usage. Option D is wrong because on-demand self-service allows users to provision resources without human interaction (e.g., via Azure Portal or CLI), but does not cover the metering and billing aspect described in the question.

Practice this question →

288

MCQmedium

Which of the following BEST describes the concept of 'security' as a cloud benefit?

A.Cloud is inherently insecure because data is shared with other customers

B.Cloud providers invest in extensive security teams and technologies that most organizations can't match

C.Moving to cloud automatically makes you compliant with all regulations

D.Cloud security means you never need to patch your applications

AnswerB

Cloud security benefit comes from providers' massive security investment — threat intelligence, expert teams, and built-in controls exceed typical org capabilities.

Why this answer

Cloud providers like Microsoft invest heavily in physical and digital security — building teams of security experts, applying the latest threat intelligence, and maintaining compliance certifications. Most organizations cannot match this investment on-premises, making cloud security a net benefit for many customers.

Practice this question →

289

MCQmedium

A company runs a web application on Azure virtual machines. The application experiences unpredictable traffic patterns with occasional sharp spikes. The operations team wants to configure the infrastructure so that the number of running virtual machines automatically increases during spikes and decreases during low traffic periods, without manual intervention. Which cloud computing characteristic does this requirement describe?

A.High availability

B.Elasticity

C.Fault tolerance

D.Geographic distribution

AnswerB

Elasticity is the correct characteristic. It enables resources (such as virtual machines) to be automatically added or removed in response to changing workload demands, which matches the described requirement.

Why this answer

Elasticity is the cloud computing characteristic that enables resources to automatically scale out (increase) during demand spikes and scale in (decrease) during low traffic periods, matching capacity to workload in real time. In Azure, this is implemented via Virtual Machine Scale Sets with autoscale rules based on metrics like CPU or memory thresholds, allowing the number of VMs to adjust without manual intervention.

Exam trap

The trap here is that candidates confuse elasticity with high availability, thinking that automatically adding VMs during spikes is about keeping the app available, but high availability is about redundancy and failover, not dynamic capacity adjustment.

How to eliminate wrong answers

Option A is wrong because high availability focuses on ensuring applications remain accessible despite failures, typically through redundancy across availability zones or regions, not on dynamically adjusting capacity based on traffic patterns. Option C is wrong because fault tolerance is the ability of a system to continue operating without interruption when one or more components fail, often using redundant components in an active-active configuration, not the automatic scaling of resources up and down in response to load changes.

Practice this question →

290

MCQeasy

A company pays a monthly subscription fee for cloud services based on the resources they consume, such as the number of virtual machines or amount of storage used. There are no upfront costs or fixed long-term commitments. This pricing model is known as:

A.Pay-as-you-go

B.Reserved instances

C.Spot pricing

D.Hybrid benefit

AnswerA

Correct. Pay-as-you-go allows you to pay for resources as you use them, with no upfront payment or long-term commitment.

Why this answer

Pay-as-you-go (also called consumption-based pricing) is the correct model because it charges the customer only for the actual resources consumed (e.g., VM hours, storage GBs) with no upfront payment or termination penalties. This aligns directly with the scenario of a monthly subscription fee based on resource usage without long-term commitments.

Exam trap

The trap here is that candidates often confuse 'pay-as-you-go' with 'reserved instances' because both involve monthly payments, but reserved instances require a fixed-term commitment (1 or 3 years) and upfront payment options, which the question explicitly excludes.

How to eliminate wrong answers

Option B (Reserved instances) is wrong because it requires a 1- or 3-year commitment in exchange for a discounted hourly rate, contradicting the 'no fixed long-term commitments' condition. Option C (Spot pricing) is wrong because it offers deeply discounted, interruptible compute capacity that can be terminated by Azure at any moment, not a simple monthly subscription based on consumption. Option D (Hybrid benefit) is wrong because it is a licensing discount program that allows customers to use on-premises Windows Server and SQL Server licenses with Software Assurance on Azure, not a pricing model for resource consumption.

Practice this question →

291

MCQeasy

A company is moving from an on-premises data center to the cloud. Previously, they paid a large upfront sum for hardware and then annual maintenance fees. Now they pay a monthly subscription based on actual usage of compute and storage. This shift represents moving from which type of expenditure to which?

A.From OpEx to CapEx

B.From CapEx to OpEx

C.From variable to fixed costs

D.From direct to indirect costs

AnswerB

The company is moving from capital expenditure (buying hardware) to operational expenditure (paying for usage). This is a common shift when adopting the cloud.

Why this answer

Option B is correct because the scenario describes a shift from paying a large upfront sum for hardware (a capital expenditure, or CapEx) to a monthly subscription based on actual usage (an operational expenditure, or OpEx). In cloud computing, CapEx involves significant upfront costs for physical infrastructure, while OpEx involves ongoing, pay-as-you-go costs for services like compute and storage. This transition is a fundamental benefit of cloud adoption, allowing organizations to avoid large initial investments and instead pay for what they consume.

Exam trap

The trap here is that candidates often confuse the direction of the expenditure shift, mistakenly thinking that moving to the cloud increases upfront costs (OpEx to CapEx), when in reality it reduces them by converting capital expenses into operational expenses.

How to eliminate wrong answers

Option A is wrong because it reverses the direction of the shift: moving from CapEx to OpEx, not from OpEx to CapEx. Option C is wrong because the scenario describes a change from fixed costs (large upfront hardware plus annual fees) to variable costs (monthly subscription based on usage), not from variable to fixed costs; the cloud model typically converts fixed capital expenses into variable operational expenses.

Practice this question →

292

MCQmedium

What is the key difference between capital expenditure (CapEx) and operational expenditure (OpEx) in the context of cloud computing?

A.CapEx is for cloud spending; OpEx is for on-premises spending

B.CapEx is upfront investment in owned infrastructure; OpEx is ongoing pay-as-you-go service costs

C.CapEx and OpEx are identical in cloud environments

D.OpEx covers hardware costs; CapEx covers software licensing costs

AnswerB

CapEx = upfront infrastructure investment (on-premises); OpEx = ongoing service consumption (cloud).

Why this answer

Option B is correct because capital expenditure (CapEx) involves a large upfront investment to purchase and own physical infrastructure (servers, storage, networking), while operational expenditure (OpEx) represents ongoing, consumption-based costs where you pay only for the resources you use (e.g., per-hour VM billing, per-GB storage fees). In cloud computing, the shift from CapEx to OpEx is a fundamental financial model change, enabling organizations to avoid large capital outlays and instead align costs with actual usage.

Exam trap

The trap here is that candidates confuse the financial classification with the deployment location, thinking CapEx is only for on-premises and OpEx only for cloud, when in reality both models can exist in either environment depending on the purchasing commitment (e.g., reserved instances are CapEx-like even in cloud).

How to eliminate wrong answers

Option A is wrong because CapEx and OpEx are not defined by deployment location (cloud vs. on-premises); both models can apply in either environment (e.g., reserved instances in cloud are CapEx-like, while on-premises managed services can be OpEx). Option C is wrong because CapEx and OpEx are fundamentally different financial models—CapEx involves ownership and depreciation, while OpEx involves consumption-based billing with no long-term asset. Option D is wrong because it incorrectly reverses the typical association: hardware costs are usually CapEx (purchased assets), while software licensing can be either CapEx (perpetual licenses) or OpEx (subscription-based SaaS), but the key distinction is the timing and nature of payment, not the type of cost.

Practice this question →

293

MCQmedium

A company migrates its web application to Azure App Service (PaaS) and its data to Azure SQL Database (PaaS). The company wants to understand which security responsibilities it retains after the migration. According to the shared responsibility model, which of the following responsibilities remains the responsibility of the company (customer) when using these PaaS services?

A.Patching the operating system of the web server

B.Managing network security groups for the virtual network

C.Managing user access to the application and database

D.Physical security of the Azure data center

AnswerC

Correct. Identity and access management, including who can access the application and the data, is always the customer's responsibility, regardless of the service model. The customer must enforce authentication and authorization.

Why this answer

In the shared responsibility model for PaaS, the cloud provider manages the underlying infrastructure, including the OS and network security groups, while the customer retains responsibility for managing access to their application and data. For Azure App Service and Azure SQL Database, this means the customer must configure authentication, authorization, and user permissions (e.g., using Azure Active Directory or SQL logins) to control who can access the application and database.

Exam trap

The trap here is that candidates often confuse PaaS with IaaS, assuming they must manage OS patching or network security groups, when in fact PaaS shifts those responsibilities to the provider, leaving user access management as the key retained duty.

How to eliminate wrong answers

Option A is wrong because patching the operating system of the web server is the responsibility of Microsoft for PaaS services like Azure App Service, as the OS is part of the managed platform. Option B is wrong because managing network security groups for the virtual network is typically a customer responsibility in IaaS, but for PaaS services, network security is partially abstracted; however, in this context, the customer does not manage NSGs for the underlying virtual network—Microsoft handles the platform-level network controls. Option D is wrong because physical security of the Azure data center is entirely Microsoft's responsibility under the shared responsibility model, as the customer has no access to the physical infrastructure.

Practice this question →

294

MCQeasy

What is 'agility' in the context of cloud computing?

A.The ability to protect data from unauthorized access

B.The ability to quickly deploy and configure resources to meet business needs

C.The ability to run applications across multiple cloud providers

D.The ability to store data permanently without loss

AnswerB

Agility is rapid provisioning of cloud resources to respond quickly to changing business requirements.

Why this answer

Agility in cloud computing refers to the ability to rapidly provision, scale, and decommission resources (such as virtual machines, databases, or containers) to adapt to changing business demands. This is enabled by infrastructure-as-code (IaC) tools like Azure Resource Manager (ARM) templates, which allow you to deploy and configure resources in minutes rather than weeks, directly supporting business responsiveness.

Exam trap

The trap here is that candidates confuse 'agility' with other cloud benefits like scalability or elasticity, but agility specifically emphasizes the speed of deployment and configuration changes to meet business needs, not just the ability to scale resources.

How to eliminate wrong answers

Option A is wrong because it describes security (specifically data protection and access control), not agility; security is a separate pillar in the Microsoft Well-Architected Framework. Option C is wrong because it describes multi-cloud portability or interoperability, which is about running workloads across providers like Azure, AWS, and GCP, not the speed of resource deployment. Option D is wrong because it describes data durability or reliability (e.g., Azure Storage's 11 nines of durability), which ensures data persists without loss, not the ability to quickly adjust resources.

Practice this question →