Cloud Concepts practice questions

Ensuring the physical security of AWS data centers

Why wrong: Physical security of data centers is the responsibility of AWS. This includes controlled access, surveillance, and environmental controls. Customers do not have physical access to data centers and do not manage physical security.

Patching the hypervisor layer that runs Amazon EC2 instances

Why wrong: The hypervisor, which abstracts the underlying hardware for Amazon EC2 instances, is managed and patched by AWS. Customers are responsible only for patching the guest operating system and applications running on their instances.

Replacing defective hardware components in the AWS global infrastructure

Why wrong: AWS is responsible for the maintenance and replacement of all hardware components in its data centers, including servers, storage devices, and networking equipment. Customers do not perform hardware replacements.

Scalability

Why wrong: Scalability generally refers to the ability to increase or decrease resources, but it can be manual or automated. The question specifies 'automatically adjust resources without manual intervention,' which is the defining feature of elasticity, not scalability alone.

High availability

Why wrong: High availability focuses on ensuring system uptime by eliminating single points of failure, often through redundant components. It does not directly address automatic resource adjustment in response to demand spikes.

Durability

Why wrong: Durability refers to the long-term protection of data against loss or corruption. It is a storage characteristic, not related to compute resource adjustment.

Elasticity

Why wrong: Elasticity is the ability to automatically scale computing resources up or down based on demand. This concept is about matching capacity to workload, not about surviving an Availability Zone failure.

Scalability

Why wrong: Scalability is the ability to handle increasing loads by adding resources. While related to growth, it does not inherently ensure continuous operation when a whole data center fails.

Resource pooling

Why wrong: Resource pooling is a characteristic of cloud computing where the provider's computing resources are pooled to serve multiple customers (multi-tenancy). It does not directly address failure recovery across data centers.

On-demand self-service

Why wrong: On-demand self-service refers to a user's ability to provision computing capabilities automatically without requiring human interaction with each service provider. It does not describe the shared hardware model.

Measured service

Why wrong: Measured service means cloud systems automatically control and optimize resource use by leveraging a metering capability at some level of abstraction. It relates to billing and usage monitoring, not the sharing of physical infrastructure.

Broad network access

Why wrong: Broad network access means resources are available over the network and accessed through standard mechanisms (e.g., mobile phones, laptops). It does not describe the multi-tenant sharing of hardware.

Availability Zones

Why wrong: Availability Zones are physically separate data centers within an AWS Region. While they provide high availability, they do not offer a way to choose a different country or legal jurisdiction; they are part of the Region you select. Therefore, they are not the primary element to evaluate for data residency.

Edge Locations

Why wrong: Edge Locations are endpoints used by AWS services like Amazon CloudFront to cache content closer to users. They do not run customer workloads or store primary data, so they are not suitable for meeting data residency requirements for compute and storage.

Local Zones

Why wrong: Local Zones extend an existing AWS Region and are designed for low-latency applications. They are still within the same country as the parent Region, so they do not provide an additional option for changing data location. The Region selection is the primary factor for data residency.

Elasticity

Why wrong: Elasticity is the ability to automatically scale resources up or down based on demand. While it can affect costs, it does not directly describe the shift from upfront hardware purchases to pay-as-you-go consumption.

Economies of scale

Why wrong: Economies of scale refer to the cost advantages that AWS passes on to customers due to its massive infrastructure. This is a benefit of AWS pricing, but it does not specifically describe eliminating upfront capital investment in favor of variable monthly payments.

High availability

Why wrong: High availability focuses on ensuring systems remain operational and accessible despite failures. It is not related to the cost structure change from capital expenditure to operational expenditure.

On-demand self-service

Why wrong: On-demand self-service enables users to provision computing capabilities automatically without requiring human interaction with the service provider. This does not specifically address the ability to access resources from various device types.

Resource pooling

Why wrong: Resource pooling refers to the provider's computing resources being pooled to serve multiple customers using a multi-tenant model, with physical and virtual resources dynamically assigned according to consumer demand. It does not relate to device accessibility.

Measured service

Why wrong: Measured service means that cloud systems automatically control and optimize resource use by leveraging a metering capability at some level of abstraction appropriate to the type of service. It is about monitoring and billing, not about multi-device access.

Scalability

Why wrong: Incorrect. While scalability involves the ability to increase capacity to handle growth, it does not inherently require automatic scaling down. The scenario specifically requires automatic removal of resources when traffic decreases, which is a key aspect of elasticity rather than scalability alone.

High availability

Why wrong: Incorrect. High availability focuses on ensuring that applications remain operational and accessible despite component failures (e.g., distributing across multiple Availability Zones). It does not directly address dynamic capacity adjustments based on load changes.

Fault tolerance

Why wrong: Incorrect. Fault tolerance is the ability of a system to continue operating even when one or more of its components fail. The scenario does not describe failure recovery, but rather the scaling of resources to match fluctuating demand.

High availability

Why wrong: High availability refers to systems that are designed to remain operational even when individual components fail, typically through redundancy across multiple Availability Zones. While AWS offers high availability, the scenario specifically highlights cost advantages from large-scale purchasing, not system uptime.

Elasticity

Why wrong: Elasticity is the ability to automatically scale resources up or down based on demand. Although AWS provides elasticity, the scenario focuses on the cost reduction arising from AWS's large-scale operations, not on the ability to adjust resource capacity dynamically.

Fault tolerance

Why wrong: Fault tolerance is the ability of a system to continue operating without interruption when one or more components fail. While AWS provides fault-tolerant services, the scenario does not discuss system resilience or failure handling; it centers on cost advantages from scale.

Elasticity

Why wrong: Elasticity is the ability to automatically scale resources up or down based on demand. While important, this scenario focuses on surviving an Availability Zone failure, not on scaling to handle changes in load.

Scalability

Why wrong: Scalability is the capability to increase capacity to handle growing demand. The scenario does not describe adding or removing resources to match load, but rather maintaining operation during a failure.

Fault tolerance

Why wrong: Fault tolerance implies the system continues operating correctly even when components fail, often with no noticeable impact. While related, the AWS Cloud Practitioner exam typically uses 'high availability' for Multi-AZ designs that may have minimal interruption during failover. Fault tolerance is a stricter requirement, and the term is less commonly used in this context.

Public cloud

Why wrong: A public cloud deployment means all infrastructure is hosted by a third-party provider (like AWS) and accessible over the internet. In this scenario, the company retains data on-premises, so it is not a purely public cloud model.

Private cloud

Why wrong: A private cloud deployment means infrastructure is used exclusively by a single organization, typically on-premises or in a dedicated hosted environment. Here, the company uses AWS services, so it is not entirely private cloud.

Community cloud

Why wrong: A community cloud is shared by several organizations with similar compliance or security concerns, often managed by a third party. This scenario involves only one company using a mix of on-premises and public cloud, not a shared community infrastructure.

Resource pooling

Why wrong: Resource pooling describes how the provider's resources are shared across multiple customers, providing location independence and economies of scale. The scenario does not involve multi-tenancy or location independence; it focuses on the developer's ability to provision resources without human intervention.

Measured service

Why wrong: Measured service means that cloud systems automatically control and optimize resource use by leveraging a metering capability (e.g., pay-per-use billing). While AWS does provide measured service, this scenario is about the initial provisioning, not about usage tracking or billing.

Rapid elasticity

Why wrong: Rapid elasticity is the ability to scale resources up and down quickly in response to demand. The scenario describes a one-time provisioning of a test environment, not scaling based on fluctuating demand, so it does not best fit rapid elasticity.

Elasticity

Why wrong: Elasticity refers to the ability to automatically scale computing resources up or down based on demand. While the platform may also be elastic, the core requirement described is about surviving a failure with zero interruption, not about scaling.

High availability

Why wrong: High availability typically involves redundant components and automatic failover, but it generally allows for a short period of downtime (seconds or minutes) during the failover process. The scenario explicitly states 'zero downtime,' which is a more stringent requirement that aligns with fault tolerance.

Durability

Why wrong: Durability refers to the long-term protection of data from loss or corruption, often associated with storage services like Amazon S3 (e.g., 99.999999999% durability). It is not related to application uptime or continued processing during an infrastructure failure.

Scalability

Why wrong: Scalability is the ability to adjust resources to meet demand, but the scenario focuses on the change in payment structure from upfront to monthly usage-based billing, not on scaling up or down.

Elasticity

Why wrong: Elasticity refers to automatically provisioning and de-provisioning resources in response to load changes. While AWS offers elasticity, the primary benefit described in the scenario is the elimination of large upfront capital purchases in favor of variable monthly payments.

Economies of scale

Why wrong: Economies of scale means AWS can achieve lower per-unit costs by aggregating usage across many customers and passing those savings along. The scenario does not mention cost savings from AWS’s scale; instead, it highlights the change in how costs are incurred (upfront vs. monthly).

On-demand self-service

Why wrong: On-demand self-service refers to a consumer being able to unilaterally provision computing capabilities, such as server time and network storage, without requiring human interaction with the service provider. While AWS does support on-demand self-service, the scenario focuses on the shared physical infrastructure and lack of knowledge about the underlying server, not on the self-service provisioning process.

Rapid elasticity

Why wrong: Rapid elasticity involves the ability to quickly scale resources up or down in response to demand. The scenario does not describe any scaling activity or dynamic adjustment of capacity; it only addresses the multi-tenant nature of physical hardware. Therefore, rapid elasticity is not the best fit.

Measured service

Why wrong: Measured service means that 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). While AWS does provide measured service, the scenario does not involve metering or pay-per-use aspects; it centers on shared physical infrastructure.

High availability

Why wrong: High availability focuses on ensuring that an application remains operational and accessible during component failures, typically by distributing workloads across multiple Availability Zones. While Auto Scaling can contribute to availability by replacing failed instances, the primary purpose of this scenario is to match capacity to demand, not to maintain uptime during failures.

Fault tolerance

Why wrong: Fault tolerance is the ability of a system to continue operating without interruption when one or more of its components fail. While Auto Scaling can replace failed instances, fault tolerance typically involves redundancy (e.g., multiple servers, databases) so that no single point of failure exists. The scenario emphasizes scaling to handle load changes, not surviving failures.

Disaster recovery

Why wrong: Disaster recovery involves strategies and processes to recover IT infrastructure and data after a catastrophic event, such as a natural disaster or large-scale outage. It often includes backups, replication across Regions, and failover procedures. This scenario is about adjusting capacity in real time, not recovering from a disaster.

On-demand self-service

Why wrong: On-demand self-service means a consumer can provision computing capabilities (e.g., server time, network storage) as needed automatically without requiring human interaction with each service provider. The scenario focuses on post-consumption reporting, not the ability to provision resources without human intervention.

Broad network access

Why wrong: Broad network access means capabilities are available over the network and accessed through standard mechanisms (e.g., mobile phones, tablets, laptops, and workstations). The scenario is about usage tracking and billing transparency, not about how resources are accessed.

Resource pooling

Why wrong: Resource pooling means the provider's computing resources are pooled to serve multiple consumers using a multi-tenant model, with physical and virtual resources dynamically assigned and reassigned according to consumer demand. While AWS uses resource pooling, the detailed billing report is not a direct example of this characteristic; it is an example of measured service.

Elasticity

Why wrong: Incorrect. Elasticity refers to automatically scaling resources up or down based on demand. The scenario focuses on quick provisioning and teardown for experiments, not automatic scaling.

High availability

Why wrong: Incorrect. High availability ensures that applications remain accessible with minimal downtime, often through redundant infrastructure across multiple Availability Zones. The scenario does not address uptime or fault tolerance.

Fault tolerance

Why wrong: Incorrect. Fault tolerance is the ability of a system to continue operating even if some components fail. The scenario is about rapid provisioning for testing, not about surviving failures.

Measured service

Why wrong: Measured service refers to the capability of cloud systems to automatically control and optimize resource usage by metering usage (e.g., storage, processing, bandwidth). This enables pay-as-you-go billing. The scenario does not describe metering or billing, so this is incorrect.

Resource pooling

Why wrong: Resource pooling is the ability to serve multiple customers from the same physical infrastructure, with resources dynamically assigned and reassigned according to demand. The scenario focuses on access from various devices and locations, not on multi-tenancy or infrastructure sharing, so this is incorrect.

Rapid elasticity

Why wrong: Rapid elasticity is the ability to quickly scale resources up or down, often automatically, to match demand. The scenario does not mention scaling or changing capacity; it focuses on access methods and device diversity, so this is incorrect.

Elasticity

Why wrong: Elasticity is the ability to dynamically scale computing resources up and down based on demand. While important for handling traffic changes, it does not directly address maintaining operation during a data center failure.

On-demand self-service

Why wrong: On-demand self-service allows users to provision and configure resources automatically, without requiring human interaction with service providers. This is about instant resource provisioning, not continued operation during failures.

Broad network access

Why wrong: Broad network access means that cloud resources are accessible over the network through standard mechanisms (e.g., internet, VPN). This is about connectivity, not resilience against data center outages.