CCNA Describe cloud concepts Questions

75 of 294 questions · Page 1/4 · Describe cloud concepts · Answers revealed

1
MCQmedium

A company plans to migrate a line-of-business application to Azure. The application will run on a virtual machine (IaaS). The company wants to ensure that the operating system is kept up to date with security patches. According to the shared responsibility model, who is primarily responsible for applying these patches?

A.Microsoft, because they manage all operating system updates in Azure.
B.The customer, because the customer manages the guest operating system and is responsible for patching it.
C.Both Microsoft and the customer share responsibility equally for operating system patching.
D.The cloud service provider, as a general rule for all services in Azure.
AnswerB

This is correct. In IaaS, the customer is responsible for maintaining the guest OS, including applying security patches and updates.

Why this answer

In the shared responsibility model for IaaS, the customer retains control over the guest operating system, including applying security patches. Microsoft manages the physical host and hypervisor but does not patch the OS running inside the VM. Therefore, the customer is primarily responsible for keeping the OS up to date.

Exam trap

The trap here is that candidates often assume Microsoft handles all patching in Azure because of the 'as a service' nature, but in IaaS, the customer retains full control and responsibility for the guest OS.

How to eliminate wrong answers

Option A is wrong because Microsoft does not manage all operating system updates in Azure; they only manage the underlying infrastructure (hypervisor, physical hosts), not the guest OS. Option C is wrong because responsibility is not shared equally for OS patching in IaaS; the customer is fully responsible for the guest OS, while Microsoft handles the host OS and physical security. Option D is wrong because the cloud service provider is not responsible for OS patching in all services; in IaaS, the customer manages the guest OS, whereas in PaaS or SaaS, the provider may handle patching.

2
MCQeasy

Which statement accurately describes the consumption-based pricing model in cloud computing?

A.You pay a flat monthly fee regardless of how much you use
B.You pay only for the resources you actually use
C.You must commit to a one-year contract
D.Cloud resources are always free during off-peak hours
AnswerB

Consumption-based pricing means costs scale directly with usage — no idle capacity costs, no upfront investment.

Why this answer

The consumption-based pricing model, also known as pay-as-you-go, is a core financial model in cloud computing where you are billed only for the specific resources you consume (e.g., compute hours, storage GB, data transfer). This model eliminates upfront capital expenditure and allows costs to scale dynamically with usage, directly aligning expenses with actual consumption rather than capacity.

Exam trap

The trap here is that candidates often confuse consumption-based pricing with a flat-rate or subscription model, mistakenly thinking that 'pay-as-you-go' means a fixed monthly fee, when in reality it is variable and directly tied to actual resource usage.

How to eliminate wrong answers

Option A is wrong because a flat monthly fee regardless of usage describes a reserved or subscription-based pricing model, not the consumption-based model which charges only for what you use. Option C is wrong because committing to a one-year contract is characteristic of reserved instances or savings plans, which offer discounted rates in exchange for a term commitment, whereas consumption-based pricing has no upfront commitment. Option D is wrong because cloud resources are never universally free during off-peak hours; while some providers offer limited free tiers or spot instances with variable pricing, the consumption model always incurs charges for resources used, regardless of time.

3
MCQeasy

A company wants to move from an on-premises data center to Azure. They currently budget for purchasing servers, networking equipment, and software licenses as a one-time capital expense. In Azure, they will pay a monthly fee based on the resources they use. What type of cloud benefit does this represent?

A.High availability
B.Scalability
C.Operational expenditure (OpEx)
D.Fault tolerance
AnswerC

OpEx is the model where costs are variable and incurred based on usage, aligning with monthly fees.

Why this answer

Option C is correct because moving from a capital expense (CapEx) model—where servers, networking gear, and licenses are purchased upfront—to a pay-as-you-go monthly fee in Azure represents a shift to operational expenditure (OpEx). This cloud benefit allows the company to avoid large upfront investments and instead pay for only the compute, storage, and network resources consumed, aligning costs with usage.

Exam trap

The trap here is that candidates confuse the financial benefit (OpEx) with operational benefits like high availability or scalability, because all three are cloud advantages, but only OpEx directly addresses the shift from upfront capital spending to ongoing usage-based payments.

How to eliminate wrong answers

Option A is wrong because high availability refers to ensuring services remain accessible despite failures, typically through redundancy across availability zones or regions, not a change in cost model. Option B is wrong because scalability is the ability to increase or decrease resources dynamically based on demand, which is a separate cloud characteristic from the financial shift from CapEx to OpEx. Option D is wrong because fault tolerance is the ability of a system to continue operating without interruption after a component failure, achieved through replication and failover mechanisms, not a billing or expenditure model.

4
MCQeasy

Which term describes the practice of deploying resources across multiple Azure availability zones to protect against datacenter-level failures?

A.Geo-redundancy
B.Zone-redundant deployment
C.Horizontal scaling
D.Disaster recovery
AnswerB

Zone-redundant deployment spreads resources across availability zones within a region, protecting against datacenter failures.

Why this answer

Zone-redundant deployment (B) is the correct term because it specifically refers to replicating resources across multiple Azure availability zones within a single Azure region. Availability zones are physically separate datacenters with independent power, cooling, and networking, so deploying across them protects against a single datacenter-level failure while keeping the application within the same low-latency region.

Exam trap

The trap here is that candidates often confuse 'zone-redundant deployment' with 'geo-redundancy,' mistakenly thinking both protect against datacenter failures, but geo-redundancy is for region-level failures and involves higher latency, while zone-redundancy is for datacenter-level failures within the same region.

How to eliminate wrong answers

Option A is wrong because geo-redundancy replicates data or services across multiple Azure regions (geographies), not across availability zones within a single region, and is designed to protect against region-wide failures, not datacenter-level failures. Option C is wrong because horizontal scaling (scale-out) adds more instances of a resource (e.g., VMs) to handle increased load, but does not inherently distribute those instances across availability zones for fault tolerance. Option D is wrong because disaster recovery is a broader strategy (e.g., Azure Site Recovery) that includes failover to a secondary region or site after a major outage, not the specific practice of deploying across zones to prevent datacenter-level failures.

5
MCQeasy

A healthcare company is planning to migrate its on-premises data center to Azure. The CFO wants to shift from making large upfront hardware purchases to paying for IT resources as an ongoing operational cost. Which cloud computing benefit does this scenario describe?

A.High availability
B.Elasticity
C.Operational expenditure (OpEx)
D.Fault tolerance
AnswerC

Operational expenditure (OpEx) is the cloud computing benefit that allows organizations to pay for IT resources as an ongoing cost rather than making large upfront capital investments. This aligns directly with the CFO's goal.

Why this answer

Option C is correct because the scenario describes shifting from capital expenditure (CapEx) for upfront hardware purchases to operational expenditure (OpEx) for ongoing, pay-as-you-go IT resource consumption. This is a core financial benefit of cloud computing, where costs are treated as variable operating expenses rather than fixed capital investments.

Exam trap

The trap here is that candidates often confuse operational expenditure (OpEx) with elasticity or high availability, but the question specifically focuses on the financial shift from upfront hardware purchases to ongoing operational costs, not on scaling or reliability features.

How to eliminate wrong answers

Option A is wrong because high availability refers to ensuring services remain accessible despite failures, not to the financial model of paying for resources. Option B is wrong because elasticity describes the ability to automatically scale resources up or down based on demand, not the shift from upfront to ongoing costs. Option D is wrong because fault tolerance is the ability of a system to continue operating after a component failure, which is a reliability feature, not a cost model.

6
MCQeasy

A company deploys their application across multiple availability zones in an Azure region. This is done to improve which aspect of the application?

A.Scalability
B.Elasticity
C.High availability
D.Cost efficiency
AnswerC

Availability zones improve uptime by isolating failures.

Why this answer

Deploying an application across multiple availability zones within an Azure region ensures that if one zone experiences an outage (e.g., due to power failure or network disruption), the application can continue serving traffic from the remaining zones. This architecture directly improves high availability by eliminating a single point of failure at the datacenter level, typically achieving a service-level agreement (SLA) of 99.99% for virtual machines when using two or more instances across zones.

Exam trap

The trap here is that candidates confuse high availability with scalability or elasticity, mistakenly thinking that distributing across zones helps handle more users or automatically adjust capacity, when in fact it is solely about maintaining uptime during failures.

How to eliminate wrong answers

Option A is wrong because scalability refers to the ability to increase or decrease resources (e.g., adding more VMs or scaling out) to handle varying load, which is achieved through features like Azure Virtual Machine Scale Sets or autoscaling, not by distributing across availability zones alone. Option B is wrong because elasticity is the ability to automatically provision and de-provision resources in response to demand changes, which is a dynamic scaling behavior often implemented with Azure Autoscale, not a direct benefit of multi-zone deployment.

7
MCQmedium

Which cloud concept allows businesses to deploy applications to global markets quickly without building physical infrastructure in those locations?

A.Elasticity
B.Capital expense avoidance
C.Global reach through cloud infrastructure
D.Fault tolerance
AnswerC

Cloud's global infrastructure allows instant deployment to any region without building physical data centers.

Why this answer

Option C is correct because global reach through cloud infrastructure enables businesses to deploy applications in multiple geographic regions using the cloud provider's existing data centers, eliminating the need to build and manage physical infrastructure in each target market. Providers like Azure offer region pairs and geographies that allow low-latency access and compliance with local data residency requirements, enabling rapid global expansion.

Exam trap

The trap here is that candidates often confuse elasticity (scaling resources) or fault tolerance (high availability) with the ability to deploy globally, but neither concept inherently provides geographic distribution without physical infrastructure.

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 deploying applications globally without physical infrastructure. Option B is wrong because capital expense avoidance describes shifting from upfront hardware purchases to operational spending, which is a financial benefit of cloud computing but does not directly address global deployment capabilities. Option D is wrong because fault tolerance ensures system availability and resilience against failures through redundancy, but it does not enable deployment to new geographic markets without building physical infrastructure.

8
Matchingmedium

Match each Azure identity service to its description.

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

Concepts
Matches

Cloud-based identity and access management

Customer identity and access management

Managed domain services like Group Policy

Automatically managed identity for Azure resources

Sync on-premises directories to Azure AD

Why these pairings

These services cover identity management for users, customers, and resources.

9
MCQmedium

What is the Microsoft Trust Center?

A.A tool for managing Azure resource permissions
B.A website providing information about Microsoft's security, privacy, and compliance practices
C.A monitoring service for Azure infrastructure health
D.An Azure portal feature for security recommendations
AnswerB

The Microsoft Trust Center publishes compliance documentation, audit reports, and transparency information about how Microsoft secures and handles data.

Why this answer

The Microsoft Trust Center is a dedicated website that provides detailed information about Microsoft's security, privacy, and compliance practices. It serves as a central resource for customers to understand how Microsoft protects their data, including certifications, audit reports, and regulatory compliance documentation. This aligns with the need for transparency in cloud services, making option B correct.

Exam trap

The trap here is that candidates confuse the Microsoft Trust Center with operational or management tools like Azure Security Center or Azure Policy, because all relate to security, but the Trust Center is purely informational and not a functional service.

How to eliminate wrong answers

Option A is wrong because the Microsoft Trust Center is not a tool for managing Azure resource permissions; that role belongs to Azure Role-Based Access Control (RBAC) and Azure Policy. Option C is wrong because monitoring Azure infrastructure health is the function of Azure Monitor and Service Health, not the Trust Center. Option D is wrong because security recommendations in the Azure portal are provided by Microsoft Defender for Cloud (formerly Azure Security Center), not the Trust Center.

10
MCQeasy

What is the primary difference between a public cloud and a private cloud?

A.Public cloud is more secure than private cloud
B.Public cloud infrastructure is shared among multiple customers; private is dedicated to one organization
C.Private cloud is always hosted by a third-party provider
D.Public cloud can only be accessed from within the organization's network
AnswerB

Public cloud is multi-tenant (shared); private cloud dedicates resources to a single organization.

Why this answer

The primary difference is that a public cloud uses a multi-tenant architecture where infrastructure resources like compute, storage, and networking are shared across multiple unrelated customers, while a private cloud provisions dedicated infrastructure for a single organization, either on-premises or hosted by a third party. This distinction is fundamental to cloud deployment models as defined by NIST SP 800-145, which emphasizes resource pooling in public clouds versus single-tenant isolation in private clouds.

Exam trap

The trap here is that candidates often confuse 'security' as the primary difference, but Azure's shared responsibility model means both public and private clouds require proper security configuration, and the real distinction is multi-tenancy versus single-tenancy.

How to eliminate wrong answers

Option A is wrong because security is not inherently a differentiator between public and private clouds; both can be secure or insecure depending on configuration, compliance controls, and shared responsibility models. Option C is wrong because a private cloud can be hosted on-premises within an organization's own data center, not exclusively by a third-party provider. Option D is wrong because public clouds are accessible over the public internet from any network, not restricted to an organization's internal network.

11
MCQeasy

A company wants to move from paying large upfront costs for hardware to a model where they only pay for what they use on a monthly basis. This represents a shift from CapEx to which type of expenditure?

A.Operational expenditure (OpEx)
B.Direct expenditure
C.Indirect expenditure
D.Capital expenditure
AnswerA

OpEx is the ongoing cost of using cloud services, matching the pay-as-you-go model.

Why this answer

This scenario describes a shift from Capital Expenditure (CapEx), where large upfront costs are incurred for hardware, to Operational Expenditure (OpEx), where costs are based on actual usage and billed monthly. In cloud computing, OpEx aligns with the consumption-based model, where you pay only for resources consumed (e.g., compute hours, storage GB) without upfront commitments. This is a core financial benefit of cloud services like Azure, enabling variable costs instead of fixed capital investments.

Exam trap

The trap here is that candidates may confuse 'Direct expenditure' or 'Indirect expenditure' with OpEx, but these are not standard financial classifications in cloud cost models; the exam specifically tests the CapEx-to-OpEx shift as a key cloud concept.

How to eliminate wrong answers

Option B (Direct expenditure) is wrong because it is not a standard accounting term used to categorize IT spending models; CapEx and OpEx are the recognized classifications. Option C (Indirect expenditure) is wrong because it refers to costs not directly traceable to a specific product or service, such as overhead, not the consumption-based billing model. Option D (Capital expenditure) is wrong because it describes the exact opposite of the shift—large upfront costs for long-term assets—which the company is moving away from.

12
MCQeasy

Which of the following is an advantage of cloud computing related to speed of deployment?

A.You never need to patch operating systems
B.Resources can be provisioned in minutes rather than weeks
C.You own the physical hardware
D.All data is automatically encrypted at rest
AnswerB

Cloud agility means spinning up resources nearly instantly, unlike lengthy on-premises procurement cycles.

Why this answer

Cloud computing enables rapid provisioning of resources through self-service portals and automation, allowing virtual machines, storage, and networks to be deployed in minutes via APIs or management consoles. This contrasts with on-premises environments where hardware procurement, racking, and configuration can take weeks. The speed of deployment is a core agility benefit of the cloud, directly supporting faster time-to-market for applications.

Exam trap

The trap here is that candidates confuse 'speed of deployment' with other cloud benefits like 'no maintenance' or 'automatic security,' leading them to select options that describe different advantages (e.g., patching or encryption) rather than the specific agility metric of rapid provisioning.

How to eliminate wrong answers

Option A is wrong because cloud customers are often responsible for patching their own operating systems on IaaS virtual machines, though PaaS and SaaS may offload this; the statement 'never need to patch' is absolute and incorrect. Option C is wrong because cloud computing is defined by renting or consuming shared physical hardware owned by the cloud provider, not owning it yourself. Option D is wrong because while many cloud services offer encryption at rest, it is not automatically enabled for all services by default; customers must configure encryption settings or use provider-managed keys.

13
MCQmedium

A company runs multiple virtual machines (VMs) in Azure. The IT team notices that their VMs are hosted on physical hardware that is shared among multiple customers. The team has no ability to specify or control which physical server their VMs run on, and they cannot see the underlying hardware details. The VMs are, however, always available when requested. This scenario exemplifies which essential characteristic of cloud computing as defined by the National Institute of Standards and Technology (NIST)?

A.On-demand self-service
B.Broad network access
C.Resource pooling
D.Rapid elasticity
AnswerC

Resource pooling is the 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. The customer has no knowledge or control over the exact location of the provided resources, which matches the scenario described.

Why this answer

Resource pooling is the correct answer because the scenario describes the cloud provider's ability to serve multiple customers from the same physical hardware, with the customer having no control or knowledge of the exact underlying server. This is a core NIST characteristic where computing resources (including storage, processing, memory, and network bandwidth) are pooled to serve multiple consumers using a multi-tenant model, with physical and virtual resources dynamically assigned and reassigned according to consumer demand. The fact that VMs are always available when requested further aligns with the elasticity and on-demand nature of resource pooling, but the key is the shared, abstracted infrastructure.

Exam trap

The trap here is that candidates confuse 'resource pooling' with 'on-demand self-service' because both involve automation and abstraction, but the key differentiator is the multi-tenant hardware sharing and lack of customer control over the physical server, which is unique to resource pooling.

How to eliminate wrong answers

Option A is wrong because on-demand self-service refers to a user's ability to provision computing capabilities (like VMs) automatically without requiring human interaction with each service provider, not the underlying hardware sharing or lack of control over physical servers. Option B is wrong because broad network access describes capabilities that are available over the network and accessed through standard mechanisms (e.g., mobile phones, tablets, laptops, and workstations), which is unrelated to the multi-tenant hardware sharing or the inability to specify physical server details.

14
MCQmedium

A company is evaluating whether to move to cloud. Their IT manager says they are concerned about losing control over their data. Which Azure feature MOST directly addresses this concern?

A.Azure guarantees data never leaves the specified region unless configured to do so
B.Microsoft employees have unrestricted access to all customer data
C.Data is automatically shared with government agencies
D.All Azure data is stored in the United States
AnswerA

Azure data residency guarantees that data stored in a region stays there — customers control and configure any replication to other regions.

Why this answer

Azure data residency controls, combined with Azure regions and data sovereignty guarantees, ensure that customer data stays within specified geographic boundaries. Microsoft's contractual commitments in the Microsoft Products and Services Data Protection Addendum (DPA) address data sovereignty concerns.

15
MCQeasy

Which statement best describes the 'economies of scale' advantage of cloud computing for customers?

A.Organizations save money by eliminating all IT staff when using the cloud
B.Cloud providers achieve lower per-unit costs through massive purchasing power, offering customers lower prices
C.Organizations can use cloud resources without paying anything
D.Organizations pay less because cloud resources are lower quality than enterprise hardware
AnswerB

Economies of scale mean lower per-unit costs from massive purchases, enabling cloud providers to offer lower prices to customers.

Why this answer

Economies of scale in cloud computing means that cloud providers like AWS, Azure, or Google Cloud operate at a massive scale, allowing them to negotiate bulk discounts on hardware, power, and cooling. These cost savings are passed down to customers in the form of lower pay-as-you-go prices, making it cheaper for individual organizations than running their own on-premises data centers.

Exam trap

The trap here is confusing 'economies of scale' with 'free resources' or 'eliminating staff,' when the core concept is about cost reduction through provider-level efficiency and bulk purchasing power.

How to eliminate wrong answers

Option A is wrong because cloud computing does not eliminate the need for all IT staff; organizations still require staff to manage cloud resources, architecture, security, and governance. Option C is wrong because cloud resources are not free; providers charge based on consumption models like pay-as-you-go or reserved instances, though some services offer limited free tiers. Option D is wrong because cloud providers use enterprise-grade hardware and often offer higher reliability and performance than typical on-premises deployments, not lower quality.

16
MCQeasy

A company wants to move its on-premises applications to the cloud to benefit from the ability to quickly scale resources up or down based on demand. They want to pay only for what they use. This combination of characteristics is known as:

A.High availability
B.Elasticity
C.Fault tolerance
D.Disaster recovery
AnswerB

Elasticity allows resources to be dynamically added or removed to match demand, and you pay only for what you use.

Why this answer

Elasticity is the correct term because it describes the ability to automatically scale computing resources up or down based on demand, combined with a pay-as-you-go pricing model. This allows the company to only pay for the resources they actually use, which is a core benefit of cloud computing.

Exam trap

The trap here is that candidates often confuse elasticity with high availability, because both involve scaling, but elasticity is specifically about dynamic resource adjustment based on demand, while high availability is about uptime and redundancy.

How to eliminate wrong answers

Option A is wrong because high availability refers to ensuring that applications or services remain accessible and operational for a high percentage of time, typically through redundancy and failover mechanisms, not dynamic scaling based on demand. 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 through redundant components, not the ability to scale resources up or down. Option D is wrong because disaster recovery involves policies, tools, and procedures to recover IT infrastructure and data after a catastrophic event, not the ability to dynamically adjust resource capacity.

17
MCQeasy

What does 'high availability' mean in Azure?

A.Resources that are accessible from any device regardless of operating system
B.Services that remain operational and accessible with minimal planned or unplanned downtime
C.Resources that can be scaled up to handle maximum load
D.Data that is encrypted and protected from unauthorized access
AnswerB

High availability means systems stay up and accessible with minimal downtime through redundancy and failover.

Why this answer

High availability in Azure refers to the ability of services and resources to remain operational and accessible despite failures, with minimal planned or unplanned downtime. It is achieved through redundancy, fault tolerance, and automatic failover mechanisms, such as Azure Availability Zones and Availability Sets, which ensure that if one component fails, another takes over without significant interruption.

Exam trap

The trap here is that candidates often confuse high availability with scalability or disaster recovery, mistakenly thinking that scaling up (Option C) or data protection (Option D) directly ensures uptime, whereas high availability is specifically about minimizing downtime through redundancy and failover.

How to eliminate wrong answers

Option A is wrong because it describes cross-platform accessibility, not high availability; Azure resources can be accessed from any device via web browsers or APIs, but that is a matter of platform compatibility, not uptime guarantees. Option C is wrong because it describes scalability (specifically vertical scaling), which is about handling increased load by adding resources, not about minimizing downtime; high availability focuses on continuity, not capacity. Option D is wrong because it describes data security and encryption, which are part of Azure's security and compliance features (e.g., Azure Key Vault, encryption at rest/transit), not availability.

18
MCQeasy

A multinational corporation wants to reduce its carbon footprint by shifting workloads to the cloud. They want to understand how using a cloud provider's shared infrastructure contributes to sustainability. Which cloud computing concept is most directly related to this environmental benefit?

A.Broad network access
B.Resource pooling
C.On-demand self-service
D.Rapid elasticity
AnswerB

Resource pooling enables sharing of resources among multiple customers, improving utilization and reducing waste.

Why this answer

Resource pooling is the cloud computing concept most directly related to sustainability because it allows a cloud provider to serve multiple customers from the same shared physical infrastructure. By dynamically allocating and reallocating resources based on demand, the provider maximizes utilization rates, reducing the total number of physical servers and data centers needed. This consolidation directly lowers energy consumption and carbon emissions per workload, which is the core environmental benefit of shifting to the cloud.

Exam trap

The trap here is that candidates often confuse rapid elasticity (scaling) with resource pooling (sharing), mistakenly thinking that the ability to scale up and down is what reduces carbon footprint, when in fact the environmental benefit comes from the provider's ability to share infrastructure across many customers, not from the scaling mechanism itself.

How to eliminate wrong answers

Option A is wrong because broad network access refers to the ability to access cloud services over the network via standard protocols (e.g., HTTP, HTTPS) from various devices, and it does not inherently reduce resource usage or carbon footprint. Option C is wrong because on-demand self-service allows users to provision resources automatically without human interaction, which improves agility but does not directly contribute to the environmental benefit of shared infrastructure. Option D is wrong because rapid elasticity enables resources to scale up or down quickly based on demand, which can improve efficiency but is a dynamic scaling mechanism, not the fundamental shared-infrastructure model that drives sustainability.

19
MCQmedium

A company's CFO is evaluating the financial impact of moving the company's on-premises data center to Azure. The on-premises data center requires significant upfront investment for servers, storage, and networking equipment, which is depreciated over several years. In contrast, Azure offers a pay-as-you-go pricing model where the company pays only for the resources it consumes, with no upfront costs. The CFO wants to understand how this shift changes the company's financial reporting. Which statement accurately describes the financial difference between on-premises and cloud spending?

A.On-premises is an operational expenditure (OpEx), while Azure is a capital expenditure (CapEx).
B.On-premises is a capital expenditure (CapEx), while Azure is an operational expenditure (OpEx).
C.Both on-premises and Azure are classified as capital expenditures (CapEx).
D.Both on-premises and Azure are classified as operational expenditures (OpEx).
AnswerB

Correct. On-premises data center purchases (servers, storage, etc.) are CapEx because they involve large upfront investments that are depreciated. Azure's consumption-based pricing is OpEx because it is a variable cost incurred only when resources are used.

Why this answer

On-premises data centers require significant upfront capital investment for hardware, which is capitalized as a capital expenditure (CapEx) and depreciated over time. Azure's pay-as-you-go model shifts costs to operational expenditure (OpEx), where you pay only for consumed resources with no upfront costs, directly impacting financial reporting by converting fixed costs to variable costs.

Exam trap

The trap here is confusing the financial classification: candidates often mistakenly think cloud spending is CapEx because they associate 'paying for resources' with ownership, but Azure's no-upfront, consumption-based model is strictly OpEx.

How to eliminate wrong answers

Option A is wrong because it reverses the classification: on-premises is CapEx (capital expenditure) due to upfront hardware purchases, not OpEx. Option C is wrong because Azure's consumption-based model is OpEx, not CapEx; only on-premises involves capitalizing long-term assets.

20
MCQeasy

A hospital stores sensitive patient data in the cloud. They want to ensure that data remains secure and that the cloud provider has implemented strict physical security controls, such as biometric access and 24/7 surveillance at datacenters. Which aspect of the shared responsibility model does this describe?

A.Responsibility of the customer for network security
B.Responsibility of the cloud provider for physical security
C.Responsibility of the customer for data classification
D.Responsibility of the customer for identity and access management
AnswerB

The cloud provider is responsible for the physical security of datacenters, including access controls, surveillance, and environmental controls. This is a fundamental part of the shared responsibility model.

Why this answer

The shared responsibility model delineates that the cloud provider is responsible for the security 'of' the cloud, which includes physical infrastructure controls like biometric access and 24/7 surveillance at datacenters. This question specifically asks about physical security controls, which fall under the provider's domain regardless of the deployment model (IaaS, PaaS, or SaaS). Therefore, option B is correct because the provider must secure the physical premises housing the servers and storage.

Exam trap

The trap here is that candidates confuse 'physical security' with 'network security' or 'IAM,' assuming the customer must manage all security layers, but the shared responsibility model explicitly assigns physical controls to the provider.

How to eliminate wrong answers

Option A is wrong because network security is a shared responsibility where the provider secures the physical network infrastructure, but the customer is responsible for configuring network security groups, firewalls, and encryption in transit (e.g., TLS). Option C is wrong because data classification is entirely the customer's responsibility, as the customer determines sensitivity labels and access policies for their data, not the provider. Option D is wrong because identity and access management (IAM) is a customer responsibility for managing user identities, roles, and permissions (e.g., Azure AD), though the provider secures the underlying IAM service infrastructure.

21
MCQmedium

Which cloud service model gives customers the most control over the underlying infrastructure, including the operating system and networking?

A.Software as a Service (SaaS)
B.Platform as a Service (PaaS)
C.Infrastructure as a Service (IaaS)
D.Function as a Service (FaaS)
AnswerC

IaaS gives the most control — customers manage OS, networking, and applications on cloud-provided virtual machines.

Why this answer

Infrastructure as a Service (IaaS) provides virtualized computing resources over the internet, giving customers direct control over the operating system, storage, and networking components such as virtual networks and firewalls. Unlike higher-level service models, IaaS allows users to manage and configure the underlying infrastructure without physical hardware access, making it the model with the most customer control.

Exam trap

The trap here is that candidates often confuse PaaS with IaaS because both involve virtual machines, but PaaS hides the OS and networking configuration, whereas IaaS grants full administrative access to those layers.

How to eliminate wrong answers

Option A is wrong because Software as a Service (SaaS) delivers fully managed applications where the customer only controls application-specific settings, not the underlying OS or network. Option B is wrong because Platform as a Service (PaaS) abstracts the OS and runtime environment, limiting customer control to application code and data while the provider manages the infrastructure. Option D is wrong because Function as a Service (FaaS) is a serverless compute model where the customer only provides code functions and has no control over the OS, networking, or execution environment.

22
MCQmedium

What is the key difference between an Azure 'region' and an Azure 'geography'?

A.A region contains multiple geographies; a geography contains a single region
B.A geography is a discrete market containing multiple Azure regions for data residency purposes
C.A geography and a region are identical concepts in Azure
D.A geography refers to the physical datacenter building; a region is the city it's in
AnswerB

Geography = broad market (US, Europe); Region = specific location within the geography (East US, West Europe).

Why this answer

Option B is correct because an Azure geography is a discrete market (e.g., United States, Europe) that contains at least one Azure region, and it is designed to preserve data residency and compliance boundaries. A region is a set of datacenters deployed within a latency-defined perimeter, connected through a dedicated regional low-latency network. Geographies ensure that customer data stays within the specified boundary for legal and regulatory requirements, even if a region fails.

Exam trap

The trap here is confusing the hierarchical relationship: candidates often think a region contains geographies (Option A) or that the terms are interchangeable (Option C), but Azure explicitly defines geographies as the top-level boundary for data residency, containing one or more regions.

How to eliminate wrong answers

Option A is wrong because a geography contains multiple regions, not the other way around; a region does not contain geographies. Option C is wrong because a region and a geography are distinct concepts: a region is a physical location with datacenters, while a geography is a sovereign boundary for data residency. Option D is wrong because a geography is not a physical datacenter building; it is a larger geopolitical or market boundary, and a region is not merely a city but a specific set of datacenters within that area.

23
MCQmedium

An IT team manages a customer relationship management (CRM) application hosted on a single Azure virtual machine. As the number of users grows, the CPU and memory usage on the VM consistently exceed 90%. The team decides to increase the VM size from Standard_D2s_v3 (2 vCPUs, 8 GB RAM) to Standard_D8s_v3 (8 vCPUs, 32 GB RAM) to handle the increased load. The application is not designed to run on multiple servers simultaneously. This approach represents which type of scaling in the cloud?

A.Horizontal scaling
B.Vertical scaling
C.Diagonal scaling
D.Auto-scaling
AnswerB

Vertical scaling (scaling up) increases the capacity of a single resource by upgrading its specifications (e.g., more vCPUs, RAM). This matches the action of resizing the VM to a larger SKU.

Why this answer

Increasing the VM size from Standard_D2s_v3 to Standard_D8s_v3 adds more vCPUs and RAM to the same virtual machine, which is the definition of vertical scaling (scaling up). This approach is appropriate because the application cannot run on multiple servers simultaneously, so adding resources to the existing single VM is the only viable option to handle the increased load.

Exam trap

The trap here is that candidates often confuse vertical scaling with auto-scaling, but auto-scaling is an automated process that can scale either vertically or horizontally based on rules, whereas this question describes a manual, one-time resizing without any automation.

How to eliminate wrong answers

Option A is wrong because horizontal scaling (scaling out) involves adding more VM instances to distribute the load, but the application is not designed to run on multiple servers simultaneously, making this approach incompatible. Option C is wrong because diagonal scaling is not a recognized cloud scaling term; it is a fabricated distractor that combines aspects of horizontal and vertical scaling but has no official definition in Azure or cloud computing. Option D is wrong because auto-scaling is a mechanism that automatically adjusts resources based on demand, but the question describes a manual, one-time resizing of the VM, not an automated policy-driven adjustment.

24
MCQeasy

Which Azure cloud benefit means organizations don't need to predict future resource needs exactly when planning infrastructure?

A.Economies of scale
B.Stop guessing capacity requirements
C.Increased speed and agility
D.Go global in minutes
AnswerB

Cloud eliminates upfront capacity guessing by allowing on-demand scaling to actual demand.

Why this answer

The 'Stop guessing capacity requirements' benefit, often referred to as 'Capacity Planning' in the Azure Well-Architected Framework, directly addresses the challenge of over-provisioning or under-provisioning infrastructure. Azure's elastic scaling model allows organizations to provision resources on demand and pay only for what they use, eliminating the need to predict future workloads precisely. This is a core advantage of the consumption-based model in cloud computing, where resources can be scaled up or down automatically based on real-time metrics.

Exam trap

The trap here is that candidates often confuse 'Stop guessing capacity requirements' with 'Economies of scale' because both relate to cost savings, but the former is specifically about eliminating the need for upfront capacity forecasting, while the latter is about lower unit costs from provider-scale operations.

How to eliminate wrong answers

Option A is wrong because 'Economies of scale' refers to the cost advantages that cloud providers achieve through massive infrastructure aggregation, which they pass on to customers as lower pay-as-you-go prices—it does not address the need to predict future capacity requirements. Option C is wrong because 'Increased speed and agility' describes how cloud resources can be provisioned quickly (e.g., in minutes via ARM templates or Azure CLI), but this benefit is about rapid deployment, not about eliminating the need for capacity forecasting. Option D is wrong because 'Go global in minutes' refers to Azure's ability to deploy resources across multiple regions worldwide using Azure Traffic Manager or Azure Front Door, which is about geographic reach, not about removing the burden of capacity prediction.

25
MCQmedium

A company runs a global e-commerce platform. During a flash sale, demand surges from 10,000 users to 500,000 users in minutes. The platform automatically provisions additional servers to handle the load and deprovisions them after the sale. Which cloud characteristic is most directly demonstrated?

A.Elasticity
B.High availability
C.Fault tolerance
D.Geographic distribution
AnswerA

Correct. Elasticity allows resources to be automatically adjusted to accommodate variable workloads.

Why this answer

Elasticity is the ability of a cloud system to automatically scale resources up or down based on demand. In this scenario, the platform provisions additional servers during the flash sale and deprovisions them afterward, directly demonstrating elasticity. This contrasts with other characteristics like high availability, which focuses on uptime, not dynamic scaling.

Exam trap

The trap here is that candidates often confuse elasticity with high availability, thinking that automatically adding servers during a surge is about keeping the system available, but high availability is about fault tolerance and redundancy, not dynamic scaling.

How to eliminate wrong answers

Option B (High availability) is wrong because it refers to ensuring the system remains operational and accessible despite failures, typically through redundancy across availability zones, not the dynamic scaling of resources. Option C (Fault tolerance) is wrong because it describes the system's ability to continue operating without interruption when a component fails, often via built-in redundancy, not the automatic provisioning and deprovisioning of servers. Option D (Geographic distribution) is wrong because it involves deploying resources across multiple geographic regions to reduce latency or meet compliance, not the automatic scaling of resources based on load.

26
MCQmedium

A global consulting firm has offices in New York, London, and Tokyo. They deployed a document management system on Azure App Service. Consultants need to access the system from any location worldwide using laptops or smartphones over public Wi-Fi or cellular networks, without needing a VPN connection. After deployment, all consultants can successfully log in and use the application from any internet-connected device. Which characteristic of cloud computing does this scenario best illustrate?

A.High availability
B.Broad network access
C.Resource pooling
D.Rapid elasticity
AnswerB

Broad network access means resources can be accessed over the network from a wide range of devices and locations using standard protocols, which is exactly what the consultants experience.

Why this answer

This scenario best illustrates broad network access because the document management system is accessible over the internet from any location using laptops or smartphones without requiring a VPN. Broad network access means resources can be accessed via standard network protocols (e.g., HTTPS) from a wide range of devices, including mobile phones and laptops, over public networks like Wi-Fi or cellular. The consultants' ability to log in and use the application from any internet-connected device directly demonstrates this characteristic.

Exam trap

The trap here is that candidates confuse 'broad network access' with 'high availability' because both involve being 'accessible from anywhere,' but high availability focuses on uptime and fault tolerance, not the variety of devices and network types used for access.

How to eliminate wrong answers

Option A is wrong because high availability refers to the ability of a system to remain operational and accessible for a high percentage of time (e.g., 99.99% uptime), often through redundancy across multiple availability zones, not the ability to access the system from various devices and networks. Option C is wrong because resource pooling describes the provider's multi-tenant model where computing resources are pooled to serve multiple customers, with physical and virtual resources dynamically assigned and reassigned according to demand; this scenario does not illustrate multi-tenancy or shared resource allocation. Option D is wrong because rapid elasticity involves the ability to quickly scale resources up or down based on demand, such as automatically adding virtual machines during peak usage; the scenario describes access from different locations and devices, not dynamic scaling of resources.

27
MCQmedium

A manufacturing company is evaluating whether to migrate its on-premises workloads to Azure. The IT team calculates that the total cost of running the equivalent compute and storage resources in Azure is lower than operating its own datacenter. They attribute this cost advantage to the fact that Azure purchases servers, networking gear, and power in massive quantities and passes the savings on to customers by spreading the fixed costs across a vast number of tenants. This cost-saving benefit is a direct illustration of which cloud computing concept?

A.Economies of scale
B.Resource pooling
C.Measured service
D.Rapid elasticity
AnswerA

Correct. Economies of scale means the provider can reduce per-unit cost by buying and managing resources in large volumes, passing savings to customers.

Why this answer

The scenario describes a cost advantage that arises because Azure buys hardware and energy in bulk, reducing per-unit costs and spreading fixed expenses across many customers. This is the direct definition of economies of scale, a core cloud concept where large-scale operations lower the average cost per unit, enabling providers to offer services at a lower price than individual organizations could achieve on-premises.

Exam trap

The trap here is that candidates may confuse economies of scale with resource pooling, because both involve shared infrastructure, but economies of scale specifically addresses the cost reduction from large-scale purchasing and operations, not the multi-tenant sharing of resources.

How to eliminate wrong answers

Option B (Resource pooling) is wrong because resource pooling refers to the provider's ability to serve multiple customers from a shared pool of physical and virtual resources, dynamically assigning and reassigning them based on demand; it does not directly explain the cost reduction from bulk purchasing. Option C (Measured service) is wrong because measured service is about metering and billing for resource usage (e.g., pay-as-you-go), not about the underlying cost advantage from scale. Option D (Rapid elasticity) is wrong because rapid elasticity describes the ability to quickly scale resources up or down in response to demand, not the cost efficiency gained from large-scale procurement.

28
MCQeasy

Which of the following is an example of a SaaS (Software as a Service) offering from Microsoft?

A.Azure Virtual Machines
B.Azure App Service
C.Microsoft 365
D.Azure SQL Database
AnswerC

Microsoft 365 is SaaS — Microsoft manages everything; users just access the application.

Why this answer

Microsoft 365 is a SaaS offering because it provides ready-to-use productivity applications (e.g., Word, Excel, Teams) accessed via a web browser or client, with Microsoft managing the underlying infrastructure, operating system, and application updates. The customer simply consumes the software without needing to install or maintain servers or runtime environments.

Exam trap

The trap here is that candidates often confuse PaaS (like Azure App Service or Azure SQL Database) with SaaS, because both are 'managed' services, but PaaS still requires the customer to manage application code or database schemas, whereas SaaS provides a fully finished application ready for end-user consumption.

How to eliminate wrong answers

Option A is wrong because Azure Virtual Machines are an IaaS (Infrastructure as a Service) offering, providing virtualized compute resources where the customer manages the guest OS, middleware, and applications. Option B is wrong because Azure App Service is a PaaS (Platform as a Service) offering that provides a managed hosting environment for web applications, but the customer still deploys and manages their own application code and configuration. Option D is wrong because Azure SQL Database is a PaaS offering that provides a managed relational database engine, where Microsoft handles the underlying hardware and database software patching, but the customer is responsible for schema design, indexing, and query optimization.

29
MCQeasy

Which term describes the cloud's ability to quickly provision and de-provision resources to meet demand without human intervention?

A.High availability
B.Elasticity
C.Fault tolerance
D.Disaster recovery
AnswerB

Elasticity is the automatic, dynamic scaling of resources to match demand without human intervention.

Why this answer

Elasticity is the correct term because it specifically refers to the cloud's ability to automatically scale resources up or down in response to fluctuating demand, without requiring manual intervention. This is a core characteristic of cloud computing, enabling dynamic provisioning and de-provisioning of compute, storage, or network resources based on real-time metrics like CPU utilization or request count.

Exam trap

The trap here is that candidates often confuse elasticity with high availability, but high availability is about uptime and redundancy, not the ability to dynamically adjust capacity to match demand.

How to eliminate wrong answers

Option A is wrong because high availability focuses on ensuring that applications or services remain operational and accessible despite component failures, typically through redundancy and failover mechanisms (e.g., multiple availability zones), not on dynamic scaling to meet demand. 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 hardware or software, but it does not involve provisioning or de-provisioning resources based on demand. Option D is wrong because disaster recovery refers to the processes and policies for restoring IT infrastructure and data after a catastrophic event (e.g., natural disaster or cyberattack), not to the rapid scaling of resources in response to normal demand fluctuations.

30
MCQmedium

A company wants to ensure that their cloud provider's physical data centers are located in specific geographic areas to comply with data residency requirements. Which cloud concept is this related to?

A.Data sovereignty
B.Availability
C.Disaster recovery
D.Hybrid cloud
AnswerA

Correct. Data sovereignty deals with data being stored within specific geographic or legal boundaries, directly relating to choosing Azure regions for compliance.

Why this answer

Data sovereignty is the concept that data is subject to the laws and regulations of the country or region where it is physically stored. By ensuring their cloud provider's data centers are located in specific geographic areas, the company is directly addressing data sovereignty requirements to comply with local data residency laws, such as GDPR in Europe or the Personal Information Protection and Electronic Documents Act (PIPEDA) in Canada.

Exam trap

The trap here is that candidates often confuse data sovereignty with availability or disaster recovery, mistakenly thinking that geographic placement is about uptime or backup rather than legal jurisdiction and data residency compliance.

How to eliminate wrong answers

Option B is wrong because availability refers to the ability of a system to remain operational and accessible, typically measured by uptime percentages (e.g., 99.99%), and does not involve geographic placement for legal compliance. Option C is wrong because disaster recovery focuses on restoring IT infrastructure and data after a disruptive event (e.g., using Azure Site Recovery), not on the initial geographic location of data centers for regulatory purposes. Option D is wrong because hybrid cloud describes a combination of on-premises and public cloud environments (e.g., using Azure Arc), which is a deployment model, not a concept related to data residency or legal jurisdiction.

31
MCQmedium

A company's CTO asks why Azure can offer services at lower costs than building an equivalent on-premises solution. Which cloud principle BEST explains this?

A.Elasticity
B.Economies of scale
C.High availability
D.Geo-distribution
AnswerB

Cloud providers achieve economies of scale by serving millions of customers, allowing them to buy infrastructure at lower per-unit costs and pass savings to customers.

Why this answer

Economies of scale is the correct answer because cloud providers like Azure operate massive, standardized data centers that serve millions of customers simultaneously. This allows them to negotiate bulk discounts on hardware, power, and cooling, and to spread fixed operational costs across a vast customer base, resulting in per-unit costs far lower than what a single company would pay for an equivalent on-premises deployment.

Exam trap

The trap here is that candidates often confuse elasticity (scaling to meet demand) with cost savings, but elasticity reduces waste from over-provisioning, not the fundamental unit cost of compute or storage, which is where economies of scale provide the primary cost advantage.

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, which reduces waste but does not directly explain the lower baseline cost of cloud services compared to on-premises. Option C is wrong because high availability ensures uptime through redundancy and failover mechanisms, which can actually increase costs due to duplicate infrastructure, not lower them. Option D is wrong because geo-distribution involves deploying resources across multiple geographic regions to reduce latency and improve resilience, but this typically adds cost for data replication and cross-region networking, rather than reducing overall expenditure.

32
MCQeasy

A company traditionally purchased physical servers and networking equipment every three years, paying the full cost upfront. They are now migrating their workloads to Azure virtual machines. The finance team wants to understand the primary financial benefit of the new cloud model. Which statement best describes this benefit?

A.The company can stop paying for electricity and cooling because Azure includes those costs in the monthly bill.
B.The company can replace large upfront capital expenditures with variable monthly payments based on actual usage.
C.The company will pay a fixed monthly fee for each virtual machine, regardless of whether it is running or stopped.
D.The company can reduce its overall IT spending by 50% or more when moving to the cloud.
AnswerB

This correctly describes the consumption-based model (OpEx) of cloud computing. Instead of buying hardware every few years, you pay only for what you use, which improves cash flow and aligns costs with business activity.

Why this answer

Option B is correct because migrating from on-premises physical servers to Azure virtual machines shifts the cost model from Capital Expenditure (CapEx) — paying the full hardware cost upfront every three years — to Operational Expenditure (OpEx), where you pay only for the compute, storage, and network resources you actually consume on a monthly basis. This aligns costs directly with usage, avoiding large upfront investments and enabling better cash flow management.

Exam trap

The trap here is that candidates often confuse the 'pay-as-you-go' model with a simple reduction in total cost, when the actual exam focus is on the shift from CapEx to OpEx as the primary financial benefit of cloud computing.

How to eliminate wrong answers

Option A is wrong because while Azure does include the cost of electricity, cooling, and physical infrastructure in its pricing, the primary financial benefit of the cloud is not merely shifting utility costs; it is the fundamental change from CapEx to OpEx, which improves financial flexibility and reduces upfront risk. Option C is wrong because Azure virtual machines incur charges only when they are in a 'Running' state (allocated); stopped (deallocated) VMs do not incur compute charges, though storage costs for disks still apply — so a fixed monthly fee regardless of state is incorrect. Option D is wrong because there is no guaranteed 50% or more reduction in IT spending when moving to the cloud; actual savings depend on workload optimization, reserved instances, and usage patterns, and costs can sometimes increase if resources are not managed properly.

33
MCQmedium

A manufacturing company runs its proprietary production scheduling software on on-premises servers. The IT team also manages on-premises file servers. The company decides to move its email system to Microsoft 365 but keeps all other systems on-premises. Which cloud deployment model does this scenario best describe?

A.Private cloud
B.Public cloud
C.Hybrid cloud
D.Community cloud
AnswerC

Correct. A hybrid cloud combines on-premises infrastructure (or private cloud) with public cloud services. The company keeps its core on-premises systems and adds Microsoft 365 for email, creating a mixed environment that spans both private and public clouds.

Why this answer

This scenario describes a hybrid cloud because the company uses a mix of on-premises infrastructure (production scheduling servers and file servers) and a public cloud service (Microsoft 365 for email). In a hybrid cloud model, organizations integrate on-premises resources with public cloud services, allowing data and applications to be shared between them. Here, the email system runs in Microsoft's public cloud while all other systems remain on-premises, creating a hybrid deployment.

Exam trap

The trap here is that candidates often think hybrid cloud requires active data sharing or integration between on-premises and cloud, but the AZ-900 definition includes any mix of on-premises and public cloud resources, even if they are used independently.

How to eliminate wrong answers

Option A is wrong because a private cloud is dedicated to a single organization and hosted either on-premises or by a third-party provider, but here the email system is moved to Microsoft 365, which is a multi-tenant public cloud service, not a private cloud. Option B is wrong because a public cloud model would involve moving all workloads to a cloud provider like Azure or AWS, but the company keeps its production scheduling and file servers on-premises, so it is not fully public. Option D is wrong because a community cloud is shared by several organizations with common concerns (e.g., compliance or security requirements), and this scenario involves only one company using Microsoft 365, not a shared infrastructure among multiple entities.

34
Matchingmedium

Match each Azure service to its primary function.

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

Concepts
Matches

Serverless compute service

Workflow automation service

Event routing service

Message broker service

Simple message queue service

Why these pairings

These are common Azure services with distinct roles in compute and messaging.

35
MCQmedium

A cloud provider uses virtualization technology to host multiple customers on the same physical server. Each customer's data, applications, and operating systems are logically isolated and secured from one another. Which characteristic of cloud computing does this scenario best describe?

A.Resource pooling
B.Rapid elasticity
C.Measured service
D.On-demand self-service
AnswerA

Correct. Resource pooling (often called multi-tenancy) is the cloud characteristic where computing resources are pooled to serve multiple customers, with physical and virtual resources dynamically assigned and reassigned according to demand. Customers typically have no control over the exact physical location of the resources, but logical isolation ensures security.

Why this answer

This scenario describes resource pooling, where the provider's computing resources (such as storage, memory, and network bandwidth) are pooled to serve multiple customers using a multi-tenant model. Virtualization technology creates isolated virtual machines for each tenant, ensuring logical separation of data and applications while sharing the same physical hardware. This is a core characteristic of cloud computing as defined by NIST SP 800-145.

Exam trap

The trap here is that candidates often confuse resource pooling with rapid elasticity, thinking that 'pooling' implies dynamic scaling, but resource pooling specifically refers to the multi-tenant sharing of physical infrastructure, not the speed of resource allocation.

How to eliminate wrong answers

Option B (Rapid elasticity) is wrong because it refers to the ability to automatically scale resources up or down quickly based on demand, not the logical isolation of tenants on shared hardware. Option C (Measured service) is wrong because it involves metering resource usage for billing and optimization, typically via a pay-per-use model, not the multi-tenant isolation described. Option D (On-demand self-service) is wrong because it describes a user's ability to provision resources without human interaction, not the provider's internal architecture for sharing infrastructure.

36
MCQmedium

Which of the following is an example of a 'hybrid cloud' deployment?

A.Using only Azure for all company workloads
B.Running customer-facing applications on Azure while keeping sensitive HR data on on-premises servers
C.Using both Azure and AWS for different workloads
D.Storing data only in the cloud with no on-premises infrastructure
AnswerB

Hybrid cloud combines on-premises infrastructure for sensitive workloads with public cloud for others.

Why this answer

Option B is correct because a hybrid cloud deployment combines public cloud resources (Azure) with on-premises infrastructure, connected via technologies like VPNs or Azure ExpressRoute. Running customer-facing apps on Azure while keeping sensitive HR data on-premises exemplifies this blend, allowing organizations to maintain compliance or low latency for critical data while leveraging cloud scalability.

Exam trap

The trap here is confusing multi-cloud (using multiple public cloud providers) with hybrid cloud (public cloud plus on-premises/private cloud), leading candidates to incorrectly select Option C.

How to eliminate wrong answers

Option A is wrong because using only Azure for all workloads is a public cloud deployment, not hybrid, as it lacks any on-premises or private cloud component. Option C is wrong because using both Azure and AWS is a multi-cloud deployment, not hybrid; hybrid specifically requires a mix of public cloud and on-premises/private cloud, not multiple public clouds. Option D is wrong because storing data only in the cloud with no on-premises infrastructure is a pure public cloud deployment, which excludes the on-premises element essential for hybrid.

37
MCQmedium

A startup runs a web application on Azure virtual machines. The application experiences sudden, short-lived spikes in traffic multiple times a day. The startup configures an autoscale rule that adds two additional VM instances when CPU usage exceeds 75% and removes them when CPU drops below 30%. This approach is designed to match resource consumption closely to demand. Which cloud computing characteristic does this scenario primarily demonstrate?

A.High Availability
B.Elasticity
C.Fault Tolerance
D.Durability
AnswerB

Elasticity is the cloud characteristic that enables resources to be automatically provisioned and de-provisioned in response to real-time workload changes. The autoscale rule that adds or removes VMs based on CPU usage directly embodies elasticity by ensuring resource consumption closely follows demand.

Why this answer

Elasticity is the ability of a cloud system to automatically scale resources up or down based on real-time demand. In this scenario, the autoscale rule dynamically adds two VM instances when CPU exceeds 75% and removes them when CPU drops below 30%, closely matching resource consumption to traffic spikes. This on-demand provisioning and de-provisioning of compute capacity is the defining characteristic of elasticity.

Exam trap

The trap here is that candidates often confuse elasticity with high availability, because both involve multiple instances, but elasticity is about scaling to meet demand while high availability is about maintaining uptime through redundancy.

How to eliminate wrong answers

Option A is wrong because High Availability focuses on ensuring application uptime through redundancy across fault domains or availability zones, not on dynamically scaling resources in response to load changes. Option C is wrong because Fault Tolerance refers to a system's ability to continue operating without interruption after a component failure, typically through redundant components that take over instantly, not through scaling based on CPU thresholds. Option D is wrong because Durability is a data storage characteristic that guarantees data will not be lost or corrupted over time, often through replication and backup mechanisms, and is unrelated to compute scaling.

38
MCQmedium

A manufacturing company wants to process IoT sensor data locally at their factory floor to reduce latency before sending summarized data to the cloud. Which cloud computing concept does this represent?

A.Hybrid cloud
B.Edge computing
C.Public cloud
D.Disaster recovery
AnswerB

Edge computing processes data locally near the source (factory floor) to reduce latency before sending to the cloud.

Why this answer

Edge computing is the correct concept because it involves processing data near the source (the factory floor) rather than sending it to a centralized cloud data center. This reduces latency by performing initial analysis locally, with only summarized results transmitted to the cloud. The scenario explicitly describes local processing to minimize delay, which is the core purpose of edge computing.

Exam trap

The trap here is that candidates confuse hybrid cloud with edge computing, thinking that any on-premises component automatically implies hybrid cloud, but edge computing specifically focuses on local data processing for latency reduction, not just a mix of cloud and on-premises resources.

How to eliminate wrong answers

Option A is wrong because hybrid cloud refers to a combination of on-premises infrastructure and public cloud services, not specifically to local data processing at the edge to reduce latency. Option C is wrong because public cloud involves resources hosted off-site by a third-party provider, which would introduce higher latency for real-time IoT sensor data compared to local processing. Option D is wrong because disaster recovery is a business continuity strategy for restoring systems after a failure, not a concept for reducing latency through local data processing.

39
MCQmedium

A company runs several virtual machines on Azure that are hosted on physical servers shared with other customers. The company is concerned that another customer's high workload ('noisy neighbor') could degrade their own application performance. However, Azure's infrastructure ensures that each virtual machine receives a dedicated allotment of CPU and memory resources, and performance remains consistent regardless of the activity of other tenants. Which characteristic of cloud computing does this scenario best illustrate?

A.Measured service
B.Rapid elasticity
C.Resource pooling
D.On-demand self-service
AnswerC

Resource pooling is the correct answer. The physical servers are pooled to serve multiple customers, but Azure's hypervisor and resource governance ensure that each virtual machine gets its own guaranteed resources, demonstrating the isolation aspect of resource pooling.

Why this answer

Resource pooling is the correct answer because it describes how Azure's multi-tenant architecture allows physical resources (CPU, memory, storage, network) to be shared among multiple customers while ensuring each virtual machine receives a dedicated allocation of resources. This isolation prevents a 'noisy neighbor' scenario from degrading performance, as each VM's resource allotment is guaranteed regardless of other tenants' activity.

Exam trap

The trap here is that candidates confuse 'resource pooling' with 'rapid elasticity' because both involve shared resources, but resource pooling focuses on multi-tenant isolation and dedicated allocation, not dynamic scaling.

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-as-you-go), not the isolation or allocation of resources to prevent performance interference. Option B is wrong because rapid elasticity describes the ability to quickly scale resources up or down based on demand, not the dedicated resource assignment that mitigates noisy neighbor issues. Option D is wrong because on-demand self-service allows users to provision resources without human intervention, but it does not address how resources are allocated or isolated among tenants.

40
MCQmedium

A retail company runs an e-commerce application on Azure virtual machines. Traffic follows a predictable daily pattern: peak load occurs from 9 AM to 5 PM on weekdays. To handle this, the company configures an Azure autoscale rule that adds virtual machines at 8:30 AM and removes them at 5:30 PM each weekday. This scenario best demonstrates which cloud computing characteristic?

A.High availability
B.Elasticity
C.Agility
D.Fault tolerance
AnswerB

Elasticity is the correct concept. Azure autoscale automatically adds or removes resources (VMs) based on defined rules or schedules to match workload demand. Here, the predictable daily pattern triggers scheduled scaling, which is a classic implementation of elasticity.

Why this answer

Elasticity is the ability to dynamically scale resources up or down to match demand. In this scenario, the autoscale rule adds VMs at 8:30 AM to handle the predictable peak load and removes them at 5:30 PM, demonstrating automatic resource provisioning and de-provisioning based on a schedule. This is a textbook example of elasticity in cloud computing.

Exam trap

The trap here is confusing elasticity with high availability: candidates often pick 'high availability' because they see multiple VMs being added, but the key is the scheduled scaling in response to predictable load, not redundancy for uptime.

How to eliminate wrong answers

Option A is wrong because high availability refers to ensuring application uptime through redundancy (e.g., multiple VMs in an availability set), not scaling based on load patterns. Option C is wrong because agility refers to the speed of deploying and iterating on resources (e.g., spinning up a new VM in minutes), not the automatic scaling behavior shown here. Option D is wrong because fault tolerance is the ability to continue operating without interruption after a component failure (e.g., using Azure Site Recovery), not the scheduled addition and removal of resources.

41
MCQmedium

A company currently runs its application on-premises in a data center. The IT manager calculates that the cost per server per month is approximately $200 when considering hardware depreciation, electricity, cooling, and staff. The company is considering moving to Azure and discovers that Azure can provision the same server capacity for $150 per month, but only if the company commits to a three-year reservation. Which cloud concept best explains why Azure can offer a lower price even with the reservation commitment?

A.Rapid elasticity
B.Economies of scale
C.High availability
D.Measured service
AnswerB

Economies of scale is the correct concept. Cloud providers purchase hardware, electricity, and bandwidth in massive volumes, reducing their per-unit costs far below what a typical organization can achieve. These savings are passed to customers, even with reserved pricing.

Why this answer

Azure can offer a lower price for a three-year reserved instance because of economies of scale. Microsoft operates massive, globally distributed data centers that purchase hardware, power, and cooling in bulk, significantly reducing per-unit costs. This cost advantage is passed to customers who commit to longer-term reservations, as the provider can better predict and optimize resource utilization.

Exam trap

The trap here is that candidates confuse 'reservation' with 'reserved capacity' and assume the discount comes from the commitment itself, rather than understanding that the underlying cost advantage is driven by economies of scale at the provider level.

How to eliminate wrong answers

Option A is wrong because rapid elasticity refers to the ability to automatically scale resources up or down in response to demand, not to cost reductions from long-term commitments. Option C is wrong because high availability describes the ability of a system to remain operational despite failures, typically achieved through redundancy and SLAs, not through pricing discounts. Option D is wrong because measured service is the capability to track and bill resource usage (metering), which enables pay-as-you-go models but does not inherently explain lower prices from reservation commitments.

42
MCQmedium

A company hosts a critical line-of-business application on Azure virtual machines. The application must remain available even if a single virtual machine fails due to hardware failure or operating system crash. The company deploys two virtual machines in an Availability Set and configures an Azure Load Balancer to distribute traffic. If one VM becomes unavailable, the Load Balancer automatically redirects traffic to the healthy VM. This configuration primarily demonstrates which benefit of cloud computing?

A.Elasticity – ability to scale resources up and down
B.Reliability – ability to recover from failures and continue functioning
C.Security – protection against unauthorized access
D.Cost efficiency – paying only for consumed resources
AnswerB

Correct. The use of an Availability Set and Load Balancer ensures that the application can tolerate the failure of a single VM and continue serving traffic. This is a direct example of reliability, a key benefit of cloud computing.

Why this answer

This configuration demonstrates reliability, a core cloud computing benefit, because the combination of an Availability Set and Azure Load Balancer ensures that the application remains operational even when a single VM fails due to hardware or OS issues. The Availability Set spreads VMs across fault domains and update domains to isolate failures, while the Load Balancer uses health probes to detect VM unavailability and redirect traffic only to healthy instances. This built-in redundancy and automatic failover capability directly aligns with the cloud's promise of high availability and fault tolerance.

Exam trap

The trap here is that candidates confuse reliability (the ability to recover from failures and continue functioning) with elasticity (scaling), because both involve multiple VMs, but the key distinction is that reliability focuses on fault tolerance and automatic failover, not dynamic scaling based on load.

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 VMs during peak traffic, not to maintaining availability during a failure. Option C is wrong because security involves protecting resources through measures like network security groups, encryption, or Azure Active Directory, which are not part of the described failover configuration. Option D is wrong because cost efficiency relates to the pay-as-you-go model and optimizing resource usage to reduce expenses, not to the redundancy and automatic recovery provided by the Availability Set and Load Balancer.

43
MCQmedium

A company is migrating its on-premises SQL Server databases to Azure SQL Database, which is a Platform as a Service (PaaS) offering. The on-premises IT team is accustomed to manually applying monthly security patches to the SQL Server software. After the migration, the team wants to understand their responsibilities for securing the database. According to the shared responsibility model, which party is responsible for applying security patches to the SQL Server database engine in Azure SQL Database?

A.The customer, because the database engine is a customer-managed application.
B.Microsoft, because Azure SQL Database is a PaaS service where Microsoft manages the database engine.
C.Both the customer and Microsoft share equal responsibility for patching the database engine.
D.The customer, but only if the Azure SQL Database is configured with the serverless compute tier.
AnswerB

Correct. For PaaS services like Azure SQL Database, Microsoft is responsible for maintaining the database engine, including applying security patches. The customer focuses on data, schema, and access controls.

Why this answer

Azure SQL Database is a Platform as a Service (PaaS) offering where Microsoft manages the underlying infrastructure, including the operating system and the SQL Server database engine. Under the shared responsibility model, Microsoft is responsible for applying security patches to the database engine, while the customer is responsible for securing their data, access controls, and database-level configurations. This frees the customer from manual patching tasks they performed on-premises.

Exam trap

The trap here is that candidates mistakenly apply on-premises patching habits to PaaS, assuming the customer retains full control over the database engine, when in fact Microsoft manages the underlying platform and engine updates under the shared responsibility model.

How to eliminate wrong answers

Option A is wrong because Azure SQL Database is a PaaS service, not a customer-managed application; the database engine is managed by Microsoft, not the customer, so patching is Microsoft's responsibility. Option C is wrong because the shared responsibility model for PaaS does not assign equal patching responsibility; Microsoft handles the underlying platform and engine patches, while the customer manages data and access, making responsibility distinct and not shared equally.

44
MCQmedium

What does 'disaster recovery' mean in cloud computing, and how does Azure support it?

A.Disaster recovery means the cloud never experiences any failures
B.The ability to restore systems and data after a major outage, supported by services like Azure Site Recovery
C.Disaster recovery is only relevant for on-premises systems
D.Azure automatically protects all data with no configuration required
AnswerB

DR is about planning and executing recovery from major failures; Azure Site Recovery replicates VMs to secondary regions for failover.

Why this answer

Disaster recovery (DR) in cloud computing refers to the strategies and processes used to restore IT systems and data after a catastrophic failure, such as a natural disaster or large-scale outage. Azure supports DR primarily through Azure Site Recovery (ASR), which orchestrates replication, failover, and failback of virtual machines and workloads between Azure regions or from on-premises to Azure, ensuring business continuity with defined recovery point objectives (RPO) and recovery time objectives (RTO).

Exam trap

The trap here is that candidates may assume disaster recovery is only about preventing failures (Option A) or that it is automatically handled by the cloud provider (Option D), when in fact DR requires active configuration and planning by the customer.

How to eliminate wrong answers

Option A is wrong because it incorrectly states that the cloud never experiences failures; in reality, cloud providers like Azure design for resilience but still face outages, which is why DR is necessary. Option C is wrong because disaster recovery is equally relevant for cloud systems, not just on-premises; Azure provides DR services like ASR for cloud-native and hybrid scenarios. Option D is wrong because Azure does not automatically protect all data with no configuration; customers must explicitly configure replication, backup policies, and DR settings using services like ASR or Azure Backup.

45
MCQmedium

A company is migrating its on-premises infrastructure to Azure. In the past, to provision a new server, the IT team had to submit a formal request to the data center operations team. The operations team would then procure hardware, install the operating system, configure networking, and make the server available. This process often took several weeks. After migrating to Azure, a developer can log into the Azure portal, select a virtual machine configuration, and have it provisioned and running within minutes, without any need to interact with Azure support or operations staff. Which essential characteristic of cloud computing does this scenario best illustrate?

A.Rapid elasticity
B.On-demand self-service
C.Resource pooling
D.Measured service
AnswerB

Correct. On-demand self-service is the cloud characteristic that allows users to provision and manage computing resources as needed automatically without requiring human interaction with the service provider.

Why this answer

The scenario describes a developer provisioning a virtual machine directly through the Azure portal without any human intervention from IT or operations staff. This aligns with the cloud characteristic of on-demand self-service, where users can provision and manage computing resources as needed automatically, without requiring manual approval or interaction with service providers.

Exam trap

The trap here is that candidates confuse rapid elasticity with on-demand self-service, but rapid elasticity focuses on scaling resources automatically in response to load, while on-demand self-service is about the user's ability to provision resources without human intervention.

How to eliminate wrong answers

Option A is wrong because rapid elasticity refers to the ability to automatically scale resources up or down quickly based on demand, not the ability to provision a single resource without human interaction. Option C is wrong because resource pooling describes the provider's multi-tenant model where physical and virtual resources are dynamically assigned and reassigned according to consumer demand, not the user's ability to self-provision resources.

46
MCQeasy

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

A.From CapEx to OpEx
B.From OpEx to CapEx
C.From direct cost to indirect cost
D.From variable cost to fixed cost
AnswerA

Correct. The move from upfront hardware purchases (CapEx) to monthly usage-based billing (OpEx) is a fundamental benefit of cloud computing.

Why this answer

This scenario describes a shift from Capital Expenditure (CapEx) to Operational Expenditure (OpEx). CapEx involves upfront purchases of physical assets like servers and storage, which are capitalized and depreciated over time. OpEx, on the other hand, is a pay-as-you-go model where costs are incurred based on actual usage, such as monthly cloud subscription fees for compute and storage resources.

Exam trap

The trap here is confusing the direction of the shift—candidates may incorrectly think moving from upfront payments to monthly subscriptions is from OpEx to CapEx, but OpEx is the ongoing operational cost, not the initial capital outlay.

How to eliminate wrong answers

Option B is wrong because moving from upfront server purchases to a monthly subscription is the opposite of going from OpEx to CapEx; OpEx is ongoing operational costs, not capital investments. Option C is wrong because both CapEx and OpEx are direct costs tied to specific IT resources, not indirect costs like administrative overhead or utilities; the question is about expenditure type, not cost classification.

47
MCQmedium

A retail company migrates its e-commerce platform to Azure Virtual Machines. The workload is seasonal, with high traffic during holiday sales and low traffic otherwise. To manage costs, the IT team configures Azure Automation to power off VMs during low-traffic periods and power them back on when demand increases. The company's monthly bill reflects charges only for the hours each VM was actually running; no charges are incurred for the time the VMs were in the 'Stopped (deallocated)' state. This consumption-based billing model is a direct example of which fundamental characteristic of cloud computing?

A.Rapid elasticity
B.Resource pooling
C.Measured service
D.Broad network access
AnswerC

Measured service is correct because cloud providers meter resource usage (e.g., VM compute hours) and bill customers accordingly. The company pays only for the hours VMs are running, which is the essence of consumption-based billing.

Why this answer

The correct answer is C because the scenario describes a consumption-based billing model where charges are incurred only for the hours each VM is actually running, and no charges apply when VMs are in the 'Stopped (deallocated)' state. This directly exemplifies the 'measured service' characteristic of cloud computing, where resource usage (e.g., compute hours) is metered and billed based on actual consumption, enabling pay-as-you-go pricing.

Exam trap

The trap here is that candidates often confuse 'measured service' with 'rapid elasticity' because both involve dynamic behavior, but measured service is about metering and billing, while rapid elasticity is about scaling resources automatically to match demand.

How to eliminate wrong answers

Option A is wrong because rapid elasticity refers to the ability to automatically scale resources up or down quickly in response to demand, not to billing based on usage. Option B is wrong because resource pooling involves the provider sharing compute, storage, and network resources among multiple tenants using a multi-tenant model, which is unrelated to billing for actual VM runtime. Option D is wrong because broad network access describes the ability to access cloud resources over standard network protocols (e.g., HTTPS, RDP, SSH) from various devices, not the metering or billing of consumed resources.

48
MCQmedium

A manufacturing company is planning to move its on-premises infrastructure to Azure. The CFO wants to understand the financial impact. Currently, the company purchases servers and networking equipment upfront, which depreciates over three years. In Azure, they will pay only for the compute and storage resources they consume on a monthly basis. Which cloud concept best describes this shift in cost structure?

A.Scalability
B.High availability
C.Operational expenditure (OpEx)
D.Resource pooling
AnswerC

Operational expenditure (OpEx) refers to ongoing costs for services consumed, such as monthly Azure charges. This contrasts with capital expenditure (CapEx), where hardware is purchased upfront. Moving to Azure converts large upfront investments into variable monthly costs.

Why this answer

The shift from upfront hardware purchases (capital expenditure) to paying only for consumed resources monthly is the definition of operational expenditure (OpEx). In Azure, this is enabled by the consumption-based pricing model, where you are billed for compute hours, storage GBs, and data egress rather than owning physical assets. This directly addresses the CFO's concern about financial impact by converting large upfront costs into predictable, variable monthly payments.

Exam trap

The trap here is that candidates confuse 'operational expenditure' with 'scalability' because both involve paying for what you use, but scalability is about resource adjustment, not the financial accounting shift from CapEx to OpEx.

How to eliminate wrong answers

Option A is wrong because scalability refers to the ability to increase or decrease resources dynamically based on demand, not the financial model of paying for what you use. Option B is wrong because high availability ensures that applications remain accessible despite failures through redundancy (e.g., availability zones), which is a technical resilience feature, not a cost structure. Option D is wrong because resource pooling is a cloud characteristic where multi-tenant providers share physical resources among customers, enabling economies of scale, but it does not describe the shift from CapEx to OpEx billing.

49
MCQeasy

A company wants to run some applications in its own on-premises datacenter for compliance reasons, while also using cloud services for burst capacity and development/testing. Which cloud deployment model should they adopt?

A.Private cloud
B.Public cloud
C.Hybrid cloud
D.Community cloud
AnswerC

Correct. Hybrid cloud enables the use of both on-premises and public cloud resources.

Why this answer

The hybrid cloud model is correct because it combines on-premises infrastructure (private cloud) with public cloud services, enabling the company to keep sensitive applications in its own datacenter for compliance while using the public cloud for burst capacity and development/testing. This directly matches the scenario's requirement for a unified environment that spans both local and cloud resources.

Exam trap

The trap here is that candidates often confuse 'hybrid cloud' with 'private cloud' because both involve on-premises infrastructure, but hybrid cloud explicitly requires integration with a public cloud for scenarios like burst capacity and dev/test.

How to eliminate wrong answers

Option A is wrong because a private cloud is dedicated to a single organization and hosted either on-premises or by a third-party, but it does not include public cloud services for burst capacity or development/testing. Option B is wrong because a public cloud is fully hosted by a third-party provider (e.g., Azure, AWS) and does not allow running applications in the company's own on-premises datacenter for compliance. Option D is wrong because a community cloud is shared among several organizations with common concerns (e.g., regulatory compliance), but it does not specifically combine on-premises and public cloud resources as required.

50
MCQmedium

A development team lead needs to quickly provision a new Azure virtual machine for a short-term testing project. Instead of submitting a ticket to the IT procurement team and waiting several days for hardware approval and setup, the lead directly signs into the Azure portal, configures the VM settings, and has it running within 15 minutes. The entire process required no human interaction from the cloud provider's staff. Which cloud computing characteristic does this scenario primarily demonstrate?

A.On-demand self-service
B.Broad network access
C.Measured service
D.Resource pooling
AnswerA

Correct. The team lead provisioned the VM directly through the portal without any human intervention from the provider, demonstrating on-demand self-service.

Why this answer

The scenario demonstrates on-demand self-service because the development team lead was able to provision and configure an Azure virtual machine directly through the Azure portal without any human interaction from Microsoft's staff. This characteristic allows users to automatically obtain computing resources, such as VM time and storage, as needed without requiring manual approval or provisioning from the cloud provider's IT team.

Exam trap

The trap here is that candidates may confuse on-demand self-service with resource pooling, but resource pooling is a provider-side characteristic (multi-tenancy), while on-demand self-service is a user-facing capability to provision resources without human interaction.

How to eliminate wrong answers

Option B is wrong because broad network access refers to resources being accessible over the network via standard protocols (e.g., HTTPS, RDP, SSH) from various devices (mobile, laptop, workstation), not the ability to self-provision without human intervention. Option C is wrong because measured service involves metering resource usage (e.g., CPU hours, bandwidth) for billing and optimization, which is not the primary focus of this scenario. Option D is wrong because resource pooling describes the provider's multi-tenant model where physical and virtual resources are dynamically assigned to multiple customers, not the user's ability to provision resources on demand.

51
MCQmedium

A retail company runs its e-commerce platform on Azure App Service. The platform is configured with an autoscale rule that adds web server instances when CPU usage exceeds 75%. During a holiday flash sale, traffic surges from a baseline of 1,000 concurrent users to over 100,000 concurrent users within minutes. The platform automatically provisions additional instances to handle the load, and once the sale ends, it scales back down. This ability to rapidly adjust resources to meet varying demand is a direct example of which fundamental characteristic of cloud computing?

A.On-demand self-service
B.Rapid elasticity
C.Measured service
D.Resource pooling
AnswerB

Rapid elasticity is the cloud characteristic that enables resources to be scaled out and in automatically to match demand. The platform's ability to instantly add and remove instances in response to traffic spikes exemplifies this concept.

Why this answer

Rapid elasticity is the cloud characteristic that enables resources to scale out (add instances) and scale in (remove instances) automatically and quickly in response to demand changes. In this scenario, the autoscale rule on Azure App Service detects CPU usage exceeding 75% and provisions additional web server instances within minutes to handle the surge from 1,000 to over 100,000 concurrent users, then scales back down after the flash sale ends. This dynamic, near-instantaneous adjustment of capacity is the direct embodiment of rapid elasticity, distinguishing it from manual provisioning or fixed capacity models.

Exam trap

The trap here is that candidates confuse 'rapid elasticity' with 'on-demand self-service' because both involve automation, but elasticity specifically refers to the automatic scaling of resources to match demand, whereas self-service is about user-initiated provisioning without provider intervention.

How to eliminate wrong answers

Option A is wrong because on-demand self-service refers to a user's ability to provision computing resources (e.g., VMs, storage) without requiring human interaction with the cloud provider, typically via a portal or API — it does not describe the automatic scaling of resources in response to load. Option C is wrong because measured service involves metering and reporting resource usage (e.g., CPU hours, bandwidth) for billing and optimization, not the ability to rapidly adjust capacity. Option D is wrong because resource pooling describes the provider's multi-tenant model where physical and virtual resources are dynamically assigned to serve multiple customers, not the elasticity of scaling out/in for a single customer's workload.

52
MCQeasy

A company runs a seasonal e-commerce application. During holidays, traffic increases tenfold, but the company does not want to over-provision resources for the rest of the year. They want to add or remove server capacity automatically based on real-time demand and pay only for what they use. Which cloud computing characteristic does this scenario describe?

A.High availability
B.Elasticity
C.Reliability
D.Fault tolerance
AnswerB

Elasticity is the ability to automatically scale resources up or out (and down or in) according to workload demand, thereby aligning cost with usage. This is exactly what the scenario describes.

Why this answer

Elasticity is the cloud computing characteristic that enables automatic scaling of resources up or down based on real-time demand. In this scenario, the e-commerce application needs to handle a tenfold traffic increase during holidays without over-provisioning for the rest of the year, which is exactly what elasticity provides by adding or removing server capacity dynamically and charging only for what is used.

Exam trap

The trap here is that candidates often confuse elasticity with high availability, thinking that adding more servers automatically ensures uptime, but high availability focuses on fault tolerance and redundancy, not dynamic scaling based on demand.

How to eliminate wrong answers

Option A is wrong because high availability refers to ensuring that applications or services remain operational and accessible despite failures, typically through redundancy across multiple availability zones, not by dynamically adjusting capacity based on demand. Option C is wrong because reliability is the ability of a system to recover from failures and continue functioning correctly, often measured by mean time between failures (MTBF), and does not involve scaling resources up or down in response to workload changes.

53
MCQeasy

A company wants to use a cloud service that provides a fully managed database, including automated backups, patching, and high availability, without managing any underlying servers. Which cloud service model is this?

A.Infrastructure as a Service (IaaS)
B.Platform as a Service (PaaS)
C.Software as a Service (SaaS)
D.Container as a Service (CaaS)
AnswerB

PaaS includes managed database services like Azure SQL Database.

Why this answer

This scenario describes a fully managed database service where the provider handles backups, patching, and high availability, and the customer does not manage any underlying servers. This is the definition of Platform as a Service (PaaS), which provides a managed platform (including database engines like Azure SQL Database) where the customer only manages data and schema, while the provider handles the OS, runtime, and infrastructure.

Exam trap

The trap here is that candidates confuse PaaS with IaaS because both can host databases, but IaaS requires the customer to manage the OS, database software, and patching, whereas PaaS abstracts all server management away.

How to eliminate wrong answers

Option A is wrong because Infrastructure as a Service (IaaS) provides virtualized servers, storage, and networking, but the customer is responsible for managing the OS, database software, backups, and patching—not a fully managed database. Option C is wrong because Software as a Service (SaaS) delivers complete applications (e.g., Office 365) to end users, not a platform for running custom database workloads; the customer does not manage the database engine or schema. Option D is wrong because Container as a Service (CaaS) provides orchestration and management of containers (e.g., Azure Kubernetes Service), but the customer still manages the container images, application code, and often the database software within containers—not a fully managed database service.

54
MCQmedium

A company uses Azure to host a web application. At the end of each month, the finance team receives an invoice that details charges for compute hours, storage consumption, and outbound data transfer. The IT manager explains that this granular billing is possible because Azure continuously monitors resource usage and provides detailed usage data for cost allocation. This capability is a direct example of which essential characteristic of cloud computing as defined by the National Institute of Standards and Technology (NIST)?

A.On-demand self-service
B.Broad network access
C.Resource pooling
D.Measured service
AnswerD

Measured service is the correct characteristic. Cloud systems automatically control and optimize resource use by leveraging a metering capability. This allows providers to track usage (compute hours, storage, bandwidth) and bill consumers accordingly, as described in the scenario.

Why this answer

The correct answer is D, Measured service, because the scenario describes Azure's ability to continuously monitor resource usage (compute hours, storage, data transfer) and provide detailed billing data. This aligns with NIST's definition of measured service, where cloud systems automatically control and optimize resource use by leveraging a metering capability at some level of abstraction appropriate to the type of service (e.g., storage, processing, bandwidth, and active user accounts). The granular invoice is a direct output of this metering and reporting feature.

Exam trap

The trap here is that candidates may confuse 'resource pooling' (Option C) with the idea of shared resources being billed, but the key distinction is that measured service specifically addresses the metering and reporting of usage for billing and optimization, not the multi-tenant sharing aspect.

How to eliminate wrong answers

Option A is wrong because on-demand self-service refers to a consumer's ability to provision computing capabilities unilaterally without requiring human interaction with each service provider, not to the monitoring and billing of those resources after they are used. Option B is wrong because broad network access describes capabilities being available over the network and accessed through standard mechanisms (e.g., mobile phones, laptops, workstations), not the metering or cost allocation of consumed resources. Option C is wrong because resource pooling involves the provider's computing resources being pooled to serve multiple consumers using a multi-tenant model, with physical and virtual resources dynamically assigned and reassigned according to consumer demand; it does not directly explain the detailed usage tracking and invoicing described.

55
MCQeasy

What does 'geo-distribution' mean as a benefit of cloud computing?

A.The ability to automatically scale resources up and down
B.Having datacenters around the world to serve users with low latency
C.The ability to recover from hardware failures automatically
D.Paying only for what you consume
AnswerB

Geo-distribution means deploying to multiple global regions, reducing latency for users worldwide and meeting data residency requirements.

Why this answer

Geo-distribution in cloud computing refers to the global footprint of a cloud provider's infrastructure, with datacenters deployed across multiple geographic regions. This allows applications to be hosted closer to end users, reducing network latency and improving the user experience. It also supports data residency requirements and disaster recovery by replicating data across regions.

Exam trap

The trap here is that candidates confuse 'geo-distribution' with 'high availability' or 'scalability', but geo-distribution specifically focuses on the physical placement of datacenters around the world to reduce latency, not on automatic scaling or fault recovery within a single region.

How to eliminate wrong answers

Option A is wrong because it describes 'elasticity' (the ability to automatically scale resources up and down), not geo-distribution. Option C is wrong because it describes 'high availability' or 'fault tolerance' (the ability to recover from hardware failures automatically), which is a separate benefit focused on redundancy within a region, not global distribution. Option D is wrong because it describes the 'consumption-based pricing model' (paying only for what you consume), which is a financial benefit, not a geographical or performance benefit.

56
MCQmedium

A company deploys an Azure SQL Database. The company is billed based on the amount of data stored and the number of transactions per second (DTUs). At the end of each month, the company receives an invoice that itemizes the exact usage and the corresponding charges. Which of the five essential characteristics of cloud computing does this billing model primarily demonstrate?

A.On-demand self-service
B.Broad network access
C.Resource pooling
D.Measured service
AnswerD

Measured service is the correct characteristic. Cloud systems meter resource usage (such as storage and DTUs) and provide usage reports. This enables a pay-per-use billing model, as described in the scenario where the company receives a detailed invoice based on exact consumption.

Why this answer

The billing model for Azure SQL Database, which itemizes usage based on data stored and transactions per second (DTUs), directly demonstrates the 'Measured service' characteristic. This is because cloud providers meter and charge for resource consumption (storage and DTUs) with pay-per-use billing, providing transparency for both the provider and consumer. The detailed invoice showing exact usage and charges is the hallmark of measured service, where usage is monitored, controlled, and reported.

Exam trap

The trap here is that candidates often confuse 'measured service' with 'on-demand self-service' because both involve user interaction with the cloud, but measured service specifically focuses on the metering, monitoring, and billing of resource usage, not the ability to provision resources without human intervention.

How to eliminate wrong answers

Option A is wrong because on-demand self-service refers to a user's ability to provision computing resources (like a virtual machine or database) automatically without requiring human interaction with the service provider, not to the billing or metering of those resources. Option B is wrong because broad network access describes the capability of resources to be accessed over the network via standard protocols (e.g., HTTPS, SQL over TCP/IP) from various devices (workstations, laptops, mobile phones), not the billing model. Option C is wrong because resource pooling means 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 consumer demand; it does not describe how usage is metered or billed.

57
MCQeasy

In the shared responsibility model for cloud computing, which responsibility always remains with the customer regardless of the cloud service type?

A.Managing physical network infrastructure
B.Patching the underlying hypervisor
C.Managing data and access identities
D.Maintaining operating system patches
AnswerC

Customers always retain responsibility for their data and identity/access management regardless of service type.

Why this answer

Under the shared responsibility model, the customer is always responsible for managing data and access identities, regardless of whether the service is IaaS, PaaS, or SaaS. This includes classifying data, encrypting data at rest and in transit, and configuring identity and access management (IAM) policies. Even in SaaS, where the provider manages the application, the customer must control who has access and how data is protected.

Exam trap

The trap here is that candidates confuse 'patching the OS' (which shifts to the provider in PaaS/SaaS) with 'managing data and access identities' (which is always the customer's responsibility), leading them to incorrectly select Option D as the answer.

How to eliminate wrong answers

Option A is wrong because managing physical network infrastructure is the provider's responsibility in all cloud service types, as the customer never has physical access to the data center. Option B is wrong because patching the underlying hypervisor is the provider's responsibility, as the hypervisor is part of the virtualization layer managed by the cloud provider. Option D is wrong because maintaining operating system patches is a shared responsibility that depends on the service type; in IaaS the customer patches the OS, but in PaaS and SaaS the provider typically handles OS patches.

58
MCQhard

An organization needs to meet GDPR data residency requirements ensuring personal data of EU residents is stored only within the EU. How does Azure support this?

A.Azure automatically stores all EU customer data in EU regions without configuration
B.Azure provides EU regions and contractual commitments enabling customers to keep EU data within EU boundaries
C.Azure cannot support GDPR data residency as it's a US company
D.Data residency is automatically enforced by Azure Policy without customer configuration
AnswerB

Azure offers EU-specific regions and DPA (Data Processing Agreement) commitments to support GDPR data residency requirements.

Why this answer

Azure supports GDPR data residency by offering data center regions within the EU (e.g., West Europe, North Europe, France Central) and including contractual commitments in the Microsoft Online Services Terms that guarantee customer data remains stored in the chosen EU region. Customers must explicitly select these regions during resource deployment and can use Azure Policy to enforce region restrictions, but the core support comes from Azure's physical infrastructure and legal agreements, not automatic enforcement.

Exam trap

The trap here is that candidates assume Azure automatically handles GDPR data residency without customer action, but the exam tests that customers must actively select EU regions and configure policies to enforce residency, and that Azure's US corporate status does not prevent GDPR compliance.

How to eliminate wrong answers

Option A is wrong because Azure does not automatically store EU customer data in EU regions; customers must manually select the region during resource creation, and data can be stored in non-EU regions if not configured correctly. Option C is wrong because Azure, despite being a US company, complies with GDPR through contractual commitments, data residency options, and certifications (e.g., EU Model Clauses), so it fully supports GDPR data residency. Option D is wrong because data residency is not automatically enforced by Azure Policy without customer configuration; Azure Policy can be used to restrict region deployment, but it requires explicit policy definitions and assignment by the customer.

59
MCQeasy

A company is evaluating cloud deployment models. They need to keep sensitive data on-premises due to regulations but want to use Azure for development and testing workloads. Which cloud deployment model is most suitable?

A.Hybrid cloud
B.Public cloud
C.Private cloud
D.Community cloud
AnswerA

Correct. Hybrid cloud connects on-premises environments with public cloud, enabling you to choose where workloads run based on compliance and other requirements.

Why this answer

A hybrid cloud deployment model is most suitable because it combines on-premises infrastructure (private cloud) with public cloud services like Azure. This allows the company to keep sensitive data on-premises to meet regulatory compliance while leveraging Azure for development and testing workloads, which do not have the same data residency constraints.

Exam trap

The trap here is that candidates may choose Public cloud thinking Azure can handle all workloads, overlooking the regulatory requirement to keep sensitive data on-premises, or choose Private cloud assuming it's the only compliant option, missing the hybrid model's ability to segregate workloads.

How to eliminate wrong answers

Option B (Public cloud) is wrong because it would require all workloads, including sensitive data, to be hosted on Azure's shared infrastructure, which violates the regulatory requirement to keep sensitive data on-premises. Option C (Private cloud) is wrong because it would mean all resources, including development and testing workloads, are hosted on-premises, failing to utilize Azure's scalability and cost benefits for non-sensitive workloads.

60
MCQmedium

What is the role of a cloud 'service level objective' (SLO) versus a 'service level agreement' (SLA)?

A.SLA and SLO are identical terms for the same concept
B.SLA is the provider's contractual guarantee; SLO is an internal organizational goal
C.SLO is the provider's contractual guarantee; SLA is the customer's internal target
D.SLA defines performance; SLO defines security requirements
AnswerB

Azure SLAs commit to uptime; organizations set SLOs as internal targets, typically stricter than SLAs.

Why this answer

Option B is correct because an SLA is a legally binding contract between a cloud provider and a customer that specifies guaranteed uptime, performance, and credits for breaches, while an SLO is an internal target (e.g., 99.9% uptime) that the provider sets to meet or exceed the SLA. The SLA defines the minimum commitment; the SLO is a stricter internal goal used to drive operational excellence and avoid SLA violations.

Exam trap

The trap here is that candidates confuse SLO with SLA, assuming both are contractual guarantees, when in fact the SLO is an internal metric that supports the SLA but is not legally binding.

How to eliminate wrong answers

Option A is wrong because SLA and SLO are not identical; an SLA is a contractual guarantee with legal remedies, while an SLO is an internal performance target. Option C is wrong because it reverses the roles: the SLO is not the provider's contractual guarantee; that is the SLA's function. Option D is wrong because both SLA and SLO can define performance metrics (e.g., uptime, latency), but neither exclusively defines security requirements; security is typically covered in a separate document like a Data Processing Agreement (DPA) or security addendum.

61
MCQmedium

A startup wants to migrate its application to Azure. The development team needs to be able to provision virtual machines and storage on demand without waiting for manual approval from a central IT team. Which characteristic of cloud computing directly fulfills this requirement?

A.Measured service
B.On-demand self-service
C.Rapid elasticity
D.Resource pooling
AnswerB

On-demand self-service is the correct characteristic. It allows a cloud consumer to unilaterally provision computing capabilities, such as server time and network storage, as needed automatically without requiring human interaction with each service provider.

Why this answer

B is correct because on-demand self-service allows users to provision cloud resources like virtual machines and storage automatically, without requiring human interaction or manual approval from a central IT team. This characteristic is defined by NIST SP 800-145 as the ability for a consumer to unilaterally provision computing capabilities as needed, which directly matches the startup's requirement for no-wait provisioning.

Exam trap

The trap here is that candidates often confuse rapid elasticity with on-demand self-service, but rapid elasticity is about scaling capacity up/down dynamically, not the initial provisioning without human intervention.

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-use), not the ability to provision without approval. Option C is wrong because rapid elasticity describes the ability to scale resources up or down automatically in response to demand, not the self-service provisioning process. Option D is wrong because resource pooling means the provider's computing resources are shared across multiple tenants using a multi-tenant model, which does not address the requirement for on-demand provisioning without manual approval.

62
MCQmedium

A company wants to ensure that its cloud resources are available even if a major disaster occurs in one region. They plan to deploy resources in two different geographic locations. Which cloud computing characteristic does this scenario primarily address?

A.A) Scalability
B.B) Elasticity
C.C) High availability
D.D) Disaster recovery
AnswerD

Disaster recovery prepares for major regional failures by replicating resources to another geographic region.

Why this answer

Option D (Disaster recovery) is correct because the scenario explicitly describes deploying resources in two different geographic locations to ensure availability despite a major regional disaster. Disaster recovery (DR) focuses on restoring services and data after a catastrophic failure, often using paired regions (e.g., Azure paired regions) to provide geo-redundancy and failover capabilities. This goes beyond simple uptime guarantees to address full recovery from region-level outages.

Exam trap

The trap here is that candidates confuse high availability (which handles failures within a region, like a datacenter outage) with disaster recovery (which handles region-wide failures), leading them to incorrectly select Option C.

How to eliminate wrong answers

Option A (Scalability) is wrong because scalability refers to the ability to increase or decrease resources to handle varying load, not to survive a regional disaster. Option B (Elasticity) is wrong because elasticity is the automatic provisioning and de-provisioning of resources in response to demand changes, not geo-redundancy for disaster recovery. Option C (High availability) is wrong because high availability focuses on minimizing downtime within a single region or datacenter (e.g., using availability zones or load balancers), not on recovering from a complete region failure, which requires disaster recovery planning.

63
MCQeasy

Which cloud deployment model combines on-premises infrastructure with public cloud resources, allowing data and applications to be shared between them?

A.Public cloud
B.Private cloud
C.Hybrid cloud
D.Community cloud
AnswerC

Hybrid cloud integrates on-premises infrastructure with public cloud resources, allowing workloads to move between them.

Why this answer

Option C is correct because a hybrid cloud deployment model explicitly combines on-premises infrastructure (private cloud or local datacenter) with public cloud resources, enabling data and application portability through technologies like VPNs, dedicated interconnects, or orchestration tools. This model allows workloads to burst to the public cloud during peak demand while keeping sensitive data on-premises, fulfilling the scenario described in the question.

Exam trap

The trap here is that candidates often confuse hybrid cloud with 'public cloud' or 'private cloud' because they assume any cloud usage with on-premises is hybrid, but hybrid specifically requires integrated orchestration and data sharing between both environments, not just separate usage.

How to eliminate wrong answers

Option A is wrong because a public cloud model involves resources owned and operated by a third-party provider (e.g., Azure, AWS) and delivered over the internet, with no on-premises infrastructure integration. Option B is wrong because a private cloud model is dedicated to a single organization, either on-premises or hosted by a third-party, and does not combine with public cloud resources. Option D is wrong because a community cloud model is shared among several organizations with common concerns (e.g., compliance, security), but it does not inherently combine on-premises infrastructure with public cloud resources.

64
MCQeasy

A company uses a public cloud provider that shares the same physical infrastructure among many customers. This allows the provider to offer lower prices due to economies of scale. Which cloud characteristic describes the sharing of infrastructure?

A.Measured service
B.Resource pooling
C.Rapid elasticity
D.On-demand self-service
AnswerB

Pooling allows providers to aggregate customers to achieve economies of scale.

Why this answer

Resource pooling is the cloud characteristic that allows a provider to serve multiple customers from the same physical infrastructure, using multi-tenant models. This sharing enables economies of scale because the provider can amortize hardware costs across many tenants, reducing per-customer pricing. The scenario directly describes multi-tenancy and shared infrastructure, which is the essence of resource pooling.

Exam trap

The trap here is that candidates confuse 'resource pooling' with 'rapid elasticity' because both involve shared resources, but elasticity focuses on scaling speed, not the multi-tenant sharing of physical hardware.

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 sharing of physical infrastructure. Option C is wrong because rapid elasticity describes the ability to automatically scale resources up or down quickly in response to demand, not the underlying shared hardware. Option D is wrong because on-demand self-service allows users to provision resources without human interaction via a web portal or API, but it does not describe the multi-tenant sharing of infrastructure.

65
MCQeasy

A company wants to use cloud services to temporarily increase compute capacity for a promotional event, then reduce resources afterward. They want to pay only for the extra resources used during that event. Which cloud benefit does this scenario best describe?

A.Scalability
B.High availability
C.Agility
D.Reliability
AnswerA

Correct. Scalability allows you to increase or decrease resources to match demand, and cloud providers support scaling with pay-as-you-go pricing.

Why this answer

This scenario describes scalability, specifically the ability to scale out (increase capacity) for a promotional event and then scale in (reduce resources) afterward, paying only for what is used. Azure Auto Scaling (e.g., Virtual Machine Scale Sets or Azure App Service autoscale) automatically adjusts compute resources based on demand, aligning with the pay-as-you-go model. The key is that resources are temporarily increased and then reduced, which is the hallmark of scalability, not just the ability to handle load.

Exam trap

The trap here is that candidates confuse scalability with agility, because both involve responding to demand, but agility is about the speed of provisioning and deployment, not the elastic adjustment of capacity for a temporary event.

How to eliminate wrong answers

Option B (High availability) is wrong because high availability ensures that applications remain accessible during failures (e.g., using Availability Zones or redundant deployments), not the ability to temporarily increase capacity for a short-term event. Option C (Agility) is wrong because agility refers to the speed of deploying and adapting resources (e.g., rapid provisioning via ARM templates), not the specific act of scaling resources up and down for a defined period. Option D (Reliability) is wrong because reliability focuses on consistent operation and fault tolerance (e.g., Azure Site Recovery or load balancers), not the elastic adjustment of compute capacity based on demand.

66
MCQeasy

A startup wants to use a cloud-based email service without installing any software on their own computers. They access the service through a web browser and the provider manages all updates and maintenance. Which cloud service model does this represent?

A.Infrastructure as a Service (IaaS)
B.Platform as a Service (PaaS)
C.Software as a Service (SaaS)
D.Anything as a Service (XaaS)
AnswerC

SaaS delivers the entire application as a service, such as email or CRM, where the provider manages everything.

Why this answer

This scenario describes Software as a Service (SaaS) because the startup is using a fully managed cloud-based email application accessed via a web browser, with no local installation required. The provider handles all updates, maintenance, and infrastructure, which is the defining characteristic of SaaS. Examples include Microsoft 365 or Google Workspace, where the consumer only uses the software without managing the underlying platform or infrastructure.

Exam trap

The trap here is that candidates confuse 'accessing via a browser' with PaaS (since PaaS often provides web-based tools), but PaaS is for building and deploying applications, not for consuming a finished software product like email.

How to eliminate wrong answers

Option A is wrong because Infrastructure as a Service (IaaS) provides virtualized computing resources like VMs, storage, and networking, not a ready-to-use email application; the user would still need to install and manage the email server software. Option B is wrong because Platform as a Service (PaaS) provides a development and deployment environment (e.g., runtime, database, middleware) for building custom applications, not a pre-built email service accessed via a browser. Option D is wrong because Anything as a Service (XaaS) is a broad umbrella term for any cloud service model, not a specific model; the question asks for the precise model that matches the described behavior, which is SaaS.

67
MCQeasy

What is 'defense in depth' in cloud security?

A.Using a very strong single password for all Azure accounts
B.A layered security approach where multiple defenses protect assets
C.Storing data in multiple geographic locations for backup
D.Using the most advanced encryption for all Azure data
AnswerB

Defense in depth uses multiple overlapping security layers so breaching one doesn't expose the whole system.

Why this answer

Defense in depth is a layered security strategy that uses multiple, independent security controls across different layers of the IT stack (network, compute, storage, application, data) to protect assets. If one layer is breached, additional layers are in place to prevent or limit further compromise. This approach is fundamental to Azure's security architecture, where tools like Azure Firewall, Network Security Groups (NSGs), Azure Policy, and Azure Defender work together to provide overlapping protections.

Exam trap

The trap here is that candidates confuse defense in depth with a single strong security measure (like encryption or strong passwords) or with unrelated concepts like geographic redundancy, rather than recognizing it as a layered, multi-control strategy.

How to eliminate wrong answers

Option A is wrong because using a single strong password violates the principle of least privilege and does not provide layered protection; it is a single point of failure. Option C is wrong because storing data in multiple geographic locations is a disaster recovery or high-availability strategy (geo-redundancy), not a security defense mechanism. Option D is wrong because while encryption is a critical security control, relying solely on the most advanced encryption without additional layers (e.g., network segmentation, identity management, monitoring) does not constitute defense in depth.

68
MCQeasy

What is the shared responsibility model in cloud computing?

A.The provider and customer each pay half the cost of cloud services
B.A framework dividing security responsibilities between the cloud provider and the customer
C.An agreement where customers share their infrastructure with other cloud users
D.A service where two cloud providers share management of customer workloads
AnswerB

The shared responsibility model defines which security duties the provider handles versus the customer.

Why this answer

The shared responsibility model defines the division of security and compliance obligations between the cloud provider and the customer. The provider is responsible for the security 'of' the cloud (physical hosts, network, hypervisor), while the customer is responsible for security 'in' the cloud (data, access management, OS configuration). This division varies by service model (IaaS, PaaS, SaaS), but the core principle is that security is a shared, not transferred, responsibility.

Exam trap

The trap here is that candidates often assume the provider handles all security (especially in PaaS/SaaS), forgetting that the customer always retains responsibility for data, identities, and access management regardless of the service model.

How to eliminate wrong answers

Option A is wrong because the shared responsibility model is about security obligations, not financial cost-sharing; pricing is governed by separate consumption-based or reserved-instance models. Option C is wrong because the model does not involve customers sharing infrastructure with others; multi-tenancy is a separate architectural concept, not a responsibility division. Option D is wrong because the model applies to a single provider-customer relationship, not to two providers jointly managing workloads; that scenario would involve a multi-cloud or federation arrangement, not the shared responsibility model.

69
MCQmedium

What is 'serverless computing'?

A.Computing that uses no physical servers anywhere in the world
B.A model where developers deploy code without managing server infrastructure, paying only for execution
C.Running applications without an operating system
D.Hosting applications on shared physical hardware
AnswerB

Serverless means no server management for developers — the provider handles it; billing is per execution.

Why this answer

Serverless computing is a cloud execution model where the cloud provider dynamically manages the allocation and provisioning of servers. Developers write and deploy code in the form of functions (e.g., AWS Lambda, Azure Functions) without provisioning or managing any underlying server infrastructure, and they are billed only for the actual compute time consumed during execution, not for idle capacity.

Exam trap

The trap here is that candidates confuse 'serverless' with 'no servers at all' (Option A) or 'no operating system' (Option C), when in reality serverless abstracts server management but still uses servers and OSes under the hood.

How to eliminate wrong answers

Option A is wrong because serverless computing still relies on physical servers in the cloud provider's data centers; the 'serverless' name refers to the abstraction from the developer, not the absence of hardware. Option C is wrong because serverless functions run within a containerized operating system environment (e.g., Linux containers) provided by the platform; an operating system is always present to manage execution. Option D is wrong because while serverless may share physical hardware, the defining characteristic is the event-driven, pay-per-execution billing model and the elimination of infrastructure management, not merely hardware sharing.

70
MCQmedium

Which of the following demonstrates how 'increased speed and agility' helps a development team in the cloud?

A.Waiting 6 weeks for procurement to buy servers for a new project
B.Provisioning a complete test environment in minutes to test a new feature
C.Reducing the team size needed for development projects
D.Automatically fixing bugs in production code without developer intervention
AnswerB

Cloud agility means spinning up complete environments in minutes, enabling rapid development and testing cycles.

Why this answer

Option B is correct because cloud computing enables self-service provisioning of resources via APIs, allowing a development team to spin up a complete test environment in minutes without waiting for hardware procurement. This directly demonstrates 'increased speed and agility' by reducing the time from idea to deployment, a core benefit of Infrastructure as a Service (IaaS) and Platform as a Service (PaaS) models.

Exam trap

The trap here is that candidates may confuse 'increased speed and agility' with operational automation (like auto-scaling or self-healing) rather than recognizing it as the ability to rapidly provision and de-provision resources for development and testing.

How to eliminate wrong answers

Option A is wrong because waiting 6 weeks for procurement is the opposite of increased speed and agility; it represents the traditional on-premises delay that cloud computing eliminates. Option C is wrong because cloud agility does not inherently reduce team size; it improves velocity and resource efficiency, but development teams may remain the same size or even grow to leverage faster iteration cycles. Option D is wrong because automatically fixing bugs in production code without developer intervention is not a standard cloud feature; it describes an unrealistic level of autonomous remediation, whereas cloud services provide monitoring and alerting (e.g., Azure Monitor) but still require developer action for code fixes.

71
MCQeasy

What is Software as a Service (SaaS)?

A.A model where customers manage their own virtual machines and applications
B.A model where the provider delivers complete software applications managed entirely by the provider
C.A model where customers deploy their code on provider-managed platforms
D.A model where customers rent physical hardware from the provider
AnswerB

SaaS means the provider manages everything (infrastructure, platform, and application); users just consume the software.

Why this answer

Software as a Service (SaaS) is a cloud computing model where the provider hosts and manages the entire software application, including the underlying infrastructure, middleware, and data. Customers access the application over the internet (typically via a web browser or API) without needing to install, maintain, or update anything locally. This model shifts all operational responsibility to the provider, making it the most 'hands-off' cloud service model for the customer.

Exam trap

The trap here is that candidates often confuse SaaS with PaaS (Option C) because both involve provider-managed components, but SaaS delivers a complete, ready-to-use application while PaaS only provides the platform for customers to build and deploy their own code.

How to eliminate wrong answers

Option A is wrong because it describes Infrastructure as a Service (IaaS), where customers manage their own virtual machines and applications, not SaaS. Option C is wrong because it describes Platform as a Service (PaaS), where customers deploy their own code on a provider-managed platform (e.g., runtime, OS), but the provider does not deliver a complete application. Option D is wrong because it describes a bare-metal or IaaS model where customers rent physical hardware, not a fully managed software application.

72
MCQmedium

A company is migrating a web application to Azure. The web tier will run on Azure App Service (PaaS) and the database tier will use Azure SQL Database (PaaS). The company's IT team wants to understand their patching responsibilities for the underlying operating system (OS) of each service. According to the shared responsibility model, which statement is correct?

A.The customer is responsible for patching the operating system of both Azure App Service and Azure SQL Database.
B.Microsoft is responsible for patching the operating system of Azure App Service, and the customer is responsible for patching the operating system of Azure SQL Database.
C.The customer is responsible for patching the operating system of Azure App Service, and Microsoft is responsible for patching the operating system of Azure SQL Database.
D.Microsoft is responsible for patching the operating system of both Azure App Service and Azure SQL Database.
AnswerD

This is correct. Both Azure App Service and Azure SQL Database are Platform as a Service (PaaS) offerings. In PaaS, Microsoft handles the underlying infrastructure, including OS patching, security updates, and hardware maintenance. The customer focuses on managing their application and data.

Why this answer

In the shared responsibility model, Microsoft manages the underlying infrastructure for Platform as a Service (PaaS) services. Both Azure App Service and Azure SQL Database are PaaS offerings, meaning Microsoft handles OS patching, updates, and security for the host OS. The customer is responsible only for their application code and data, not the OS.

Therefore, option D is correct.

Exam trap

The trap here is that candidates often confuse IaaS responsibilities (where customers patch the OS) with PaaS responsibilities, leading them to incorrectly assign OS patching to the customer for services like Azure App Service or Azure SQL Database.

How to eliminate wrong answers

Option A is wrong because it incorrectly assigns OS patching responsibility to the customer for both PaaS services, contradicting the PaaS model where Microsoft manages the OS. Option B is wrong because it splits responsibility incorrectly: Azure App Service (PaaS) has Microsoft managing the OS, not the customer, and Azure SQL Database (PaaS) also has Microsoft managing the OS, not the customer. Option C is wrong because it reverses the actual responsibilities: Azure App Service OS patching is Microsoft's responsibility, not the customer's, and Azure SQL Database OS patching is also Microsoft's responsibility, not the customer's.

73
MCQmedium

A manufacturing company deploys a batch processing application on Azure. The processing workload is highly unpredictable; sometimes the application requires hundreds of virtual machines for a few hours to process a large queue of jobs, and at other times it requires only a handful of virtual machines. The company configures the application to automatically add and remove virtual machines based on the size of the processing queue, ensuring that they never pay for idle capacity. Which cloud characteristic does this scenario primarily demonstrate?

A.High availability
B.Elasticity
C.Fault tolerance
D.Disaster recovery
AnswerB

Elasticity is the cloud characteristic that allows resources to be automatically provisioned and de-provisioned in response to changing demand. The scenario's automatic addition and removal of virtual machines based on queue size perfectly illustrates this principle.

Why this answer

The scenario describes automatically scaling the number of virtual machines up and down based on the queue size, which directly aligns with the cloud characteristic of elasticity. Elasticity allows resources to be dynamically provisioned and de-provisioned to match workload demand, ensuring the company never pays for idle capacity. This is distinct from high availability, fault tolerance, or disaster recovery, which focus on uptime, redundancy, and data protection rather than dynamic scaling.

Exam trap

The trap here is that candidates often confuse elasticity with high availability, thinking that scaling out to handle load also implies fault tolerance, but elasticity is purely about matching capacity to demand, not about redundancy or uptime guarantees.

How to eliminate wrong answers

Option A is wrong because high availability refers to ensuring application uptime through redundant components (e.g., availability sets or zones), not the ability to scale resources based on demand. Option C is wrong because fault tolerance is the ability to continue operating without interruption after a component failure, typically achieved through redundancy (e.g., multiple instances in different fault domains), not dynamic scaling. Option D is wrong because disaster recovery involves restoring systems and data after a catastrophic event (e.g., using Azure Site Recovery or geo-redundant storage), not automatically adjusting capacity to match workload fluctuations.

74
MCQmedium

A company is considering moving its on-premises workloads to the cloud. They want to reduce their carbon footprint by using a cloud provider that uses renewable energy. Which cloud computing benefit is most directly related to this goal?

A.A) High availability
B.B) Scalability
C.C) Sustainability
D.D) Elasticity
AnswerC

Cloud providers like Microsoft commit to using renewable energy, which helps customers reduce their carbon footprint.

Why this answer

Option C is correct because sustainability directly addresses the goal of reducing carbon footprint through the use of renewable energy. Cloud providers like Microsoft Azure invest in renewable energy projects and carbon offset programs, enabling customers to lower their environmental impact by consolidating workloads in energy-efficient data centers. This benefit is explicitly tied to environmental responsibility, not operational metrics like uptime or resource scaling.

Exam trap

The trap here is that candidates confuse sustainability with other operational benefits like high availability or scalability, assuming any cloud advantage reduces environmental impact, whereas sustainability is a distinct pillar focused on renewable energy and carbon efficiency.

How to eliminate wrong answers

Option A is wrong because high availability refers to ensuring workloads remain accessible and operational despite failures, typically through redundancy and fault-tolerant architectures (e.g., 99.99% uptime SLAs), which has no direct relation to renewable energy usage or carbon footprint reduction. Option B is wrong because scalability is the ability to dynamically adjust resources (compute, storage) based on demand, often via auto-scaling policies, which optimizes cost and performance but does not inherently involve renewable energy or environmental sustainability.

75
MCQmedium

A company is deploying a mission-critical application on Azure virtual machines. The solution must remain operational even if a single Azure datacenter within a region experiences a complete outage. Which Azure feature should the company use to protect against this specific failure scenario?

A.Availability Zones
B.Region Pairs
C.Fault Domains
D.Resource Groups
AnswerA

Correct. Availability Zones are unique physical locations within an Azure region, each with independent infrastructure. Deploying across zones ensures that a failure in one datacenter does not affect resources in other zones.

Why this answer

Availability Zones are physically separate datacenters within an Azure region, each with independent power, cooling, and networking. By deploying the application across multiple zones, the solution remains operational if one entire datacenter fails, as the other zones continue to serve traffic. This directly addresses the requirement to survive a single datacenter outage within a region.

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 region-wide disasters), leading them to choose Region Pairs even though the question specifies a single datacenter outage within a region.

How to eliminate wrong answers

Option B (Region Pairs) is wrong because region pairs protect against region-wide failures by replicating data to a paired region hundreds of miles away, not against a single datacenter outage within the same region. Option C (Fault Domains) is wrong because fault domains group VMs that share common hardware (e.g., a rack) within a single datacenter; they protect against hardware failures like a rack switch or power unit, but cannot survive an entire datacenter outage.

Page 1 of 4 · 294 questions totalNext →

Ready to test yourself?

Try a timed practice session using only Describe cloud concepts questions.