CCNA Cloud Concepts Questions

In the public cloud deployment model, the cloud provider owns and manages the physical infrastructure (servers, storage, networking), and that infrastructure is shared among multiple customer organizations (tenants). This multi-tenant architecture is a defining characteristic, enabling economies of scale and on-demand resource allocation. Option C correctly identifies this shared, provider-owned model.

Governance in Azure refers to the framework of policies, roles, and controls that enforce compliance with organizational standards. This is implemented through tools like Azure Policy, which applies rules to resources, and Azure Blueprints, which packages governance artifacts. It ensures that resources are provisioned and managed according to regulatory and business requirements, not just technically managed.

In the shared responsibility model for Azure SQL Database, Microsoft is responsible for the underlying infrastructure, including the operating system that hosts the database engine. Azure SQL Database is a Platform as a Service (PaaS) offering, where Microsoft manages the host OS, applies security patches, and ensures the physical and virtual environment is secure. The customer is only responsible for data, access management, and database-level configurations.

Vertical scaling (scaling up) increases the power of an existing resource by upgrading its size or capacity. In this scenario, changing the virtual machine from Standard_D2s_v3 (2 vCPUs) to Standard_D8s_v3 (8 vCPUs) adds more CPU cores to the same VM, which is a classic example of scaling up. This approach improves performance without adding additional VM instances.

Under the shared responsibility model for IaaS like Azure VMs, Microsoft secures the physical datacenter, host OS, and network infrastructure, while the customer is responsible for securing the guest OS (e.g., applying patches, configuring firewalls) and any applications running on the VM. This division is explicit in Azure's documentation, where the customer retains control over the OS and software stack.

For a startup with limited capital, the public cloud model eliminates the need for large upfront hardware purchases. Instead, it uses a consumption-based pricing model where you pay only for the compute, storage, and network resources you actually use, typically billed per second or per hour. This operational expenditure (OpEx) model directly addresses the capital expenditure (CapEx) constraints of a new company.

The hybrid cloud model combines on-premises infrastructure (private cloud) with public cloud services, enabling workload bursting during peak demand. This approach uses technologies like Azure ExpressRoute or VPN gateways to create a seamless network, allowing organizations to scale capacity on-demand without permanently migrating all resources.

Horizontal scaling (scale out) involves increasing the number of virtual machines (VMs) in a pool to distribute load, as seen when the team adds five VMs to go from three to eight. This approach improves capacity by adding more instances, rather than increasing the size of existing ones. In Azure, this is commonly achieved using Virtual Machine Scale Sets or Azure Load Balancer to distribute traffic across the expanded pool.

Vertical scaling (scaling up) increases the capacity of a single resource, such as adding more RAM, CPU, or disk space to a virtual machine. Horizontal scaling (scaling out) adds more instances of a resource, distributing the load across multiple machines. This distinction is fundamental in cloud computing, where Azure Virtual Machine Scale Sets exemplify horizontal scaling by automatically adding VM instances, while resizing a VM to a larger SKU represents vertical scaling.

Vertical scaling (scaling up) increases the capacity of a single resource, such as adding more RAM or CPU to a virtual machine, but it typically requires downtime to apply the changes. Cloud elasticity, on the other hand, automatically adds or removes instances (horizontal scaling) based on demand, often without downtime, enabling the system to handle variable workloads seamlessly. Option B correctly captures this distinction by contrasting the resizing of one resource with the automated, no-downtime addition or removal of instances.

This configuration demonstrates high availability because it uses Azure Traffic Manager to route traffic across two Azure regions, ensuring the application remains accessible even if an entire datacenter fails. High availability focuses on minimizing downtime by eliminating single points of failure, which is exactly what deploying VMs in multiple regions with traffic routing achieves.

Elasticity is the correct answer because it refers to the ability of a cloud system to automatically provision and de-provision resources (such as compute instances, storage, or bandwidth) in real time to match fluctuating demand. During a viral marketing campaign, traffic spikes can be handled by scaling out resources dynamically, ensuring consistent performance without manual intervention or service degradation.

The scenario describes the ability to rapidly provision and decommission Azure resources like virtual machines and databases in minutes, use them for a few hours, and then delete them. This directly supports cloud agility, which is the cloud computing benefit that enables organizations to quickly adapt to changing requirements by deploying and releasing resources on demand. Agility is about speed and flexibility in resource management, not just scaling or metering.

A private cloud deployment model is correct because it provides dedicated physical servers and ensures that no other tenant shares the same hardware. In a private cloud, the infrastructure is provisioned for exclusive use by a single organization, offering predictable performance and complete isolation from other tenants. This model can be hosted on-premises or by a third-party provider, but the key requirement of dedicated hardware is met.

Elasticity is the ability of a cloud system to dynamically scale resources up or down based on demand. In this scenario, the virtual machine scale set automatically adds three VM instances when CPU utilization exceeds 75% for five minutes and removes them when utilization drops below 30%, demonstrating rapid, automated scaling to match workload changes.

Cloud computing shifts the burden of hardware procurement, maintenance, power, cooling, and physical security from the organization to the cloud provider. This operational overhead elimination allows IT teams to redirect their efforts toward application development, data analytics, and business innovation rather than racking servers or patching firmware. The core value proposition is the transfer of undifferentiated heavy lifting to the provider.

Cloud computing supports disaster recovery by enabling geographic redundancy and automated failover across multiple Azure regions at a fraction of the cost of building and maintaining a secondary on-premises data center. Services like Azure Site Recovery and Azure Traffic Manager allow organizations to replicate workloads and automatically redirect traffic to a secondary region during an outage, reducing both recovery time objective (RTO) and recovery point objective (RPO) without the capital expenditure of a dedicated DR site.

The SLA percentage for an Azure service is determined by factors such as redundancy, fault tolerance, and resource configuration, not by the number of concurrent users. Microsoft's SLAs are based on uptime guarantees tied to architectural choices like availability zones, disk types, and availability sets, while user load is managed through scaling and is not a factor in the SLA calculation.

The scenario describes a division of security responsibilities: the hospital encrypts data (customer responsibility) and the cloud provider secures the physical datacenter (provider responsibility). This is the core definition of the shared responsibility model, where security obligations are split based on the cloud service model (IaaS, PaaS, SaaS) and the customer's control over the data and configurations.

Reserved Instances (RIs) provide a significant discount (up to 72% compared to pay-as-you-go) in exchange for a one- or three-year commitment. Since the application requires a fixed number of VMs running 24/7 for exactly three years, RIs align perfectly with this predictable, steady-state workload, minimizing total cost of ownership.

Load balancer setup includes resource creation, IP/pool config, health probes, rules, and VM association.

In a SaaS model, the provider manages the application, runtime, and infrastructure, including patching the OS and physical security. The customer retains responsibility for what they bring into the cloud: their data and user identities. Option C is correct because safeguarding customer data and managing user identities (e.g., via Azure AD) is solely the company's responsibility under the shared responsibility model.

Elasticity is the Azure cloud benefit that allows a company to automatically scale compute resources up or down based on real-time demand, eliminating the need to predict capacity months in advance. With Azure Virtual Machine Scale Sets or Azure App Service auto-scale, resources can be added or removed dynamically, ensuring you only pay for what you use. This contrasts with traditional on-premises capacity planning, where over-provisioning or under-provisioning is common.

This scenario describes a shift from Capital Expenditure (CapEx) to Operational Expenditure (OpEx). CapEx involves upfront, long-term investments in physical assets like servers, while OpEx is a pay-as-you-go model where costs are incurred based on actual usage. Azure's subscription model eliminates the need for large initial capital outlays, aligning costs with consumption.

This scenario describes a shift from Capital Expenditure (CapEx), where the company made large upfront investments in hardware every three years, to Operational Expenditure (OpEx), where they pay a monthly subscription for Azure virtual machines based on actual usage with no long-term commitment. This is a core benefit of cloud computing, converting fixed, upfront costs into variable, ongoing expenses that align with consumption.

Cloud computing follows an operational expenditure (OpEx) model where you pay only for the resources you actually consume, such as compute hours, storage GB-months, or data transfer, on a recurring basis. This eliminates the need for large upfront capital investments and allows you to scale costs with usage, aligning with the pay-as-you-go pricing model central to Azure and other cloud providers.

The scenario describes users provisioning virtual machines directly from the Azure portal without IT intervention. This aligns with on-demand self-service, a core cloud characteristic defined by NIST SP 800-145, where a consumer can unilaterally provision computing capabilities as needed automatically without requiring human interaction with each service provider.

Microsoft guarantees a 99.95% SLA for two or more virtual machines deployed in the same Availability Set because the set distributes VMs across separate fault domains and update domains, ensuring that at least one VM remains available during planned maintenance or hardware failures. The SLA applies only when all VMs are in the same Availability Set and all disks are managed disks, as per the Azure Compute SLA terms.

Disaster recovery (DR) in cloud computing focuses on restoring systems, applications, and data after a catastrophic event (e.g., natural disaster, cyberattack) to meet Recovery Time Objective (RTO) and Recovery Point Objective (RPO) targets. Azure Site Recovery orchestrates replication, failover, and failback of workloads between primary and secondary regions, ensuring minimal downtime and data loss. This is distinct from high availability, which prevents outages, or auto-scaling, which handles demand fluctuations.

In the shared responsibility model, physical security of the datacenter—including access controls, surveillance, and environmental controls—is always the sole responsibility of the cloud provider (e.g., Microsoft Azure). The customer never manages or is responsible for the physical infrastructure, regardless of the service model (IaaS, PaaS, SaaS). This is because the customer has no physical access to the datacenter and cannot implement or control physical security measures.

In the shared responsibility model for IaaS, the cloud provider is responsible for the physical infrastructure, including the datacenter, host hardware, network, and storage. This is because the customer has no physical access to these components and cannot manage them. The provider ensures the underlying hardware is maintained, secured, and operational.

A private cloud is dedicated to a single organization, providing complete control over infrastructure and ensuring no resource sharing with other tenants. This model meets regulatory requirements that mandate data isolation and compliance, as the organization can configure security policies, network segmentation, and access controls without multi-tenant risks.

Cloud computing inherently relies on internet connectivity to access resources and services. While some hybrid or private cloud setups may use dedicated connections like Azure ExpressRoute, the elimination of all internet dependencies is not a benefit—in fact, cloud services require network connectivity, and any claim of removing that dependency is false.

The scenario demonstrates measured service and consumption-based pricing because Azure charges for VM compute costs only when the VM is in the 'Running' state. Deallocating the VM releases the reserved compute resources, stopping billing for the VM's vCPU and RAM while retaining the disk and other resources. By scheduling deallocation outside business hours, the company pays only for the hours the VMs are actually running, directly reducing costs based on usage.

The scenario describes the development team provisioning a virtual machine directly through the Azure portal without any manual approval or intervention from IT operations. This is the essence of on-demand self-service, a core cloud computing characteristic defined by NIST SP 800-145, where a consumer can unilaterally provision computing capabilities as needed automatically without requiring human interaction with each service provider.

Elasticity is the cloud characteristic that enables automatic scaling of resources up or down in real-time to match demand. In this scenario, the e-commerce application needs to add compute resources during holiday spikes and remove them when demand drops, avoiding paying for idle resources. This aligns directly with elasticity, which is often implemented via auto-scaling groups and load balancers that adjust capacity based on metrics like CPU utilization or request count.

High availability in cloud computing refers to a system's ability to remain operational and accessible with minimal downtime, typically measured in terms of uptime percentage (e.g., 99.99% availability). This is achieved through redundant infrastructure, failover mechanisms, and service-level agreements (SLAs) that guarantee a certain level of continuity. Option B directly captures this core definition, distinguishing it from other cloud concepts like scalability or geo-replication.

Durability is the cloud characteristic that guarantees data remains intact and readable over extended periods, even in the face of hardware failures or bit rot. Cloud providers achieve this through data replication (e.g., Azure Storage's Locally Redundant Storage (LRS) or Geo-Redundant Storage (GRS)) and erasure coding, ensuring that stored objects survive individual disk or node failures. This is distinct from availability, which focuses on uptime and access, not long-term data integrity.

High availability ensures that the application remains accessible even if an entire data center fails, typically through redundant infrastructure across multiple availability zones. This is achieved by deploying the application in a load-balanced, multi-AZ configuration that automatically fails over to healthy instances, maintaining uptime despite a complete data center outage.

The scenario emphasizes deploying identical application instances in multiple Azure regions across Europe, Asia, and North America to serve customers geographically close to each region, which directly illustrates the global reach benefit of cloud computing. Azure Resource Manager (ARM) templates enable rapid, consistent deployment to any region, allowing the company to expand its global footprint and reduce latency by leveraging Azure's distributed infrastructure.

Predictable costs in cloud computing refer to the ability to forecast and control spending through consumption-based pricing models (pay-as-you-go) and tools like Azure Cost Management + Billing. This allows organizations to estimate costs based on usage patterns, set budgets, and receive alerts, making financial planning more accurate compared to unpredictable capital expenses.

Reliability is the cloud concept that ensures a system can recover quickly from failures, such as hardware crashes or network outages, without noticeable impact on end users. This is achieved through redundancy, fault tolerance, and automated failover mechanisms, which maintain service continuity and uptime as defined in SLAs.

Multi-tenancy is the cloud characteristic where a single instance of physical hardware (or software) serves multiple customers (tenants), isolating their data and configurations while sharing underlying resources. This sharing enables the provider to achieve economies of scale, reducing per-customer costs and allowing low prices. The scenario explicitly describes sharing physical hardware with other customers, which is the core definition of multi-tenancy.

Azure SLAs define Microsoft's formal commitments regarding service availability (uptime) and connectivity. They specify the guaranteed uptime percentage (e.g., 99.9% for most virtual machines) and outline the service credits (remedies) customers receive if Microsoft fails to meet those commitments. This is not a guarantee of zero downtime but a contractual promise with financial recourse.

A hybrid cloud model combines on-premises infrastructure (private cloud) with public cloud services, allowing the bank to keep sensitive customer data on-premises to meet regulatory requirements while using the public cloud for less sensitive workloads. This approach provides a unified management plane and secure connectivity (e.g., VPN or Azure ExpressRoute) between the two environments, ensuring compliance and flexibility.

The hybrid cloud model is correct because it allows the financial institution to keep sensitive customer data on-premises for regulatory compliance while leveraging Azure's public cloud for compute-intensive analytics on anonymized datasets. This approach combines the security and control of a private cloud (on-premises) with the scalability and managed services of a public cloud, without requiring the organization to manage physical servers for the analytics workload.

Broad network access means cloud resources can be accessed over standard network protocols (like HTTPS) from a wide range of devices (smartphones, laptops, tablets) and locations without requiring a private connection such as a VPN. In this scenario, the mobile app uses HTTPS to reach the Azure backend API from any internet-connected location, which directly matches the NIST definition of broad network access.

Data sovereignty is the concept that data is subject to the laws and governance structures of the country where it is physically stored. For a company with legal requirements to keep data within a specific country, this concept directly dictates where cloud providers must locate their data centers and how they handle data residency. Azure, for example, offers region pairs and data residency commitments through its Trust Center to help customers meet such compliance obligations.

Economies of scale in cloud computing refers to the cost advantage that cloud providers achieve through massive purchasing power—buying hardware, bandwidth, and power in bulk at discounted rates. They then pass these savings on to customers in the form of lower per-unit costs for compute, storage, and networking services. This is a fundamental economic principle that makes public cloud more cost-effective than running your own data center.

Under the shared responsibility model, the customer is always responsible for managing access to data and enforcing data classification policies, regardless of whether the workload runs on IaaS, PaaS, or SaaS. This is because data ownership and the associated governance obligations (such as who can read, write, or modify sensitive customer data) remain with the customer. Microsoft secures the underlying infrastructure, but the customer must control who accesses the application data and how it is classified.

Platform as a Service (PaaS) is the correct model because it abstracts the underlying infrastructure, including servers, operating systems, and scaling, allowing developers to focus solely on writing code and deploying features. Azure App Service is a prime example of PaaS, providing built-in load balancing, auto-scaling, and patching without developer intervention.

Elasticity is the cloud computing characteristic that allows resources to automatically scale out (add virtual machines) during demand spikes like seasonal sales and scale in (remove VMs) when demand drops, aligning with the pay-per-use model. This scenario directly matches elasticity because the company wants to dynamically adjust compute and storage resources in response to predictable traffic surges, paying only for what is consumed.

(Pay-as-you-go) is correct because it is the Azure pricing model that charges customers only for the resources they consume, with no upfront commitment or termination fees. This model provides maximum flexibility, allowing the company to scale usage up or down as needed without financial penalties, directly addressing the CFO's requirement for a usage-based cost structure.

Elasticity is the cloud characteristic that enables automatic scaling of compute resources up or down in response to real-time demand. This startup's requirement to add or remove resources without manual intervention directly matches the definition of elasticity, which is a core benefit of cloud computing.

The hybrid cloud model is correct because it allows the company to keep PII on-premises (private cloud) to satisfy data residency regulations while running compute-intensive analytics in Azure (public cloud). Azure Arc provides a consistent set of management tools to govern resources across both environments, enabling unified policy, compliance, and monitoring.

The consumption-based pricing model in Azure means you pay only for the resources you actually use, such as compute hours, storage GB, or data transfer, with no upfront costs or commitments. This model provides flexibility and cost efficiency because you can scale resources up or down based on demand and only incur charges for what you consume. It is a core principle of cloud computing that aligns costs directly with usage, enabling organizations to avoid over-provisioning and reduce waste.

This guarantee is a Service Level Agreement (SLA) because it is a formal, published commitment from Microsoft regarding the uptime percentage (99.95%) for a specific Azure service (Virtual Machines in an Availability Set), and it includes a financial remedy (service credits) if the commitment is not met. SLAs are contractual agreements that define the level of service a customer can expect and the compensation for failures.

The scenario describes the company spinning up GPU-optimized VMs only when needed and deleting them after use, paying solely for the compute time consumed. This directly illustrates consumption-based pricing (also known as pay-as-you-go), a core cloud benefit where customers pay only for the resources they actually use, avoiding large upfront capital expenditures. The ability to scale down to zero when not in use is a hallmark of this model, enabling cost efficiency for intermittent workloads.

Infrastructure as a Service (IaaS) provides virtualized computing resources over the internet, giving the startup full control over the operating system, storage, and deployed applications without managing the underlying physical hardware. This model is ideal for a startup that wants to avoid hardware maintenance while retaining the flexibility to configure and manage their own OS and application stack.

'going global in minutes' refers to the ability to deploy applications and services across multiple Azure regions worldwide with minimal effort and rapid provisioning. Azure's global infrastructure, combined with tools like Azure Resource Manager and Traffic Manager, allows you to replicate resources across regions in minutes, enabling low-latency access and disaster recovery without physical hardware shipping.

In the shared responsibility model for IaaS, the customer retains control over the guest operating system, applications, and data. Microsoft manages the physical host, hypervisor, and underlying Azure infrastructure, but the customer must install and maintain security updates on the guest OS of their Azure VMs. This is because the customer has full administrative access to the VM and is responsible for its configuration and patch management.

The private cloud model provides the greatest degree of control over the underlying infrastructure because it is dedicated to a single organization, allowing full customization of hardware, virtualization layers, networking, and security configurations. In contrast, public clouds abstract infrastructure management away from the customer, limiting control to the application and data layers only.

Environmental sustainability is the Azure benefit that directly addresses the company's goal of reducing its carbon footprint by using a cloud provider that invests in renewable energy and operates energy-efficient datacenters. Microsoft has committed to being carbon negative by 2030 and powers its Azure datacenters with 100% renewable energy, making this the most relevant benefit for the stated objective.

A region pair consists of two Azure regions within the same geography, at least 300 miles apart, that are directly connected via high-speed fiber and are used for disaster recovery and planned maintenance isolation. This design ensures that only one region in a pair is updated at a time, reducing the risk of simultaneous failures across both regions.

Platform as a Service (PaaS) is the correct model because it provides a fully managed hosting environment where the startup can deploy their web application code without needing to provision or manage underlying servers, operating systems, or runtime infrastructure. Azure App Service is a prime example of PaaS that handles automatic scaling, load balancing, and patching, allowing developers to focus solely on code.

The composite SLA for dependent services is calculated by multiplying their individual SLAs. Here, 99.9% (0.999) multiplied by 99.99% (0.9999) equals approximately 0.9989, or 99.89%. This reflects the overall availability when both the ERP application and the Azure SQL Database must be operational for the system to function.

Azure Backup requires a vault, policy, enablement, initial backup, and monitoring.

The pay-as-you-go model (also called consumption-based pricing) allows a company to pay only for the compute resources they actually consume, with no upfront costs or long-term commitments. This model provides the flexibility to scale resources up or down based on real-time demand, aligning costs directly with usage. It is the standard pricing model for most cloud services, including Azure virtual machines and App Service plans, when no reservation or spot discount is applied.

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

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

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

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

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