Describe cloud concepts practice questions

Software as a Service (SaaS)

Why wrong: SaaS delivers complete applications managed by the provider, not infrastructure control.

Platform as a Service (PaaS)

Why wrong: PaaS provides a platform to develop and deploy applications without managing underlying infrastructure.

Private Cloud

Why wrong: Private Cloud is a deployment model, not a service model; it can host any service model.

Rapid elasticity

Why wrong: Rapid elasticity is the ability to scale quickly, not automatic provisioning without interaction.

Resource pooling

Why wrong: Resource pooling means multiple customers share the same physical resources, not automated provisioning.

Measured service

Why wrong: Measured service refers to metering and billing for usage, not provisioning.

Public cloud

Why wrong: Public cloud would mean moving entirely to the cloud, not extending on-premises.

Private cloud

Why wrong: Private cloud is solely on-premises, not using public cloud for burst.

Multi-cloud

Why wrong: Multi-cloud uses multiple public cloud providers, not necessarily connecting to on-premises.

On-demand self-service

Why wrong: On-demand self-service allows users to provision resources automatically without human interaction, but it is not specifically about billing. Measured service is the characteristic that enables pay-per-use.

Broad network access

Why wrong: Broad network access means resources are accessible over the network via standard protocols. It does not relate to the billing model. The pay-per-use model is measured service.

Resource pooling

Why wrong: Resource pooling enables the provider to serve multiple customers using shared resources, which helps reduce costs but does not directly result in a pay-per-use billing model. Measured service is the correct characteristic.

Infrastructure as a Service (IaaS)

Why wrong: IaaS provides virtualized hardware resources like VMs and storage, but the user must manage the operating system and middleware, so it doesn't fully eliminate server management.

Software as a Service (SaaS)

Why wrong: SaaS delivers fully functional applications to end users, not a development platform for custom code.

On-premises deployment

Why wrong: On-premises requires the company to own and manage all hardware and software, which is the opposite of the desired approach.

Measured service

Why wrong: Measured service refers to the monitoring and billing of resource usage, not the dynamic scaling of resources.

Resource pooling

Why wrong: Resource pooling is about serving multiple customers from a shared pool of physical resources, not automatic scaling.

On-demand self-service

Why wrong: On-demand self-service allows users to provision resources without human interaction, but the scenario specifically describes scaling based on load, which is elasticity.

Public cloud

Why wrong: Public cloud does not offer dedicated hardware and may not meet compliance requirements for fixed dedicated resources.

Private cloud

Why wrong: Private cloud would still require the company to manage its own hardware, not reducing costs.

Community cloud

Why wrong: Community cloud is shared among multiple organizations with common compliance concerns, not a combination of private and public.

Public cloud

Why wrong: In public cloud, resources are shared across many tenants, reducing control over hardware and configuration.

Hybrid cloud

Why wrong: Hybrid cloud combines public and private, so control is shared between the two.

Community cloud

Why wrong: Community cloud is shared among several organizations with common concerns, still less control than a private cloud.

Patching the operating system of the database server

Why wrong: The cloud provider patches the underlying OS in PaaS.

Maintaining the physical infrastructure

Why wrong: The cloud provider is responsible for physical hardware.

Managing the virtualization layer

Why wrong: The cloud provider manages the virtualization layer.

PaaS (Platform as a Service)

Why wrong: PaaS provides a managed platform where the provider handles the OS, runtime, and middleware, so customers do not manage the OS.

SaaS (Software as a Service)

Why wrong: SaaS delivers fully managed applications that the customer accesses via a browser; the provider manages everything, including the application itself.

FaaS (Function as a Service)

Why wrong: FaaS, a serverless model, executes individual functions in response to events without provisioning VMs or managing OS.

Infrastructure as a Service (IaaS)

Why wrong: With IaaS, the customer would be responsible for managing the operating system, database engine, and patching.

Software as a Service (SaaS)

Why wrong: SaaS delivers a complete application managed by the provider. The customer would not manage the database schema directly; they use the application interface.

On-premises

Why wrong: On-premises means the company owns and manages all hardware and software, which is not the case here.

Public cloud

Why wrong: Public cloud resources are shared and managed by a third-party provider, offering less control over hardware and security.

Hybrid cloud

Why wrong: Hybrid combines public and private, but for maximum control, a pure private cloud is more suitable.

Community cloud

Why wrong: Community cloud is shared among multiple organizations with common concerns, but still may not provide the level of control a single organization can achieve with a private cloud.

Software as a Service (SaaS)

Why wrong: In SaaS, the provider manages the entire application stack, and the customer only uses the software; not fitting the scenario.

Platform as a Service (PaaS)

Why wrong: PaaS manages the runtime environment, OS, and middleware, leaving the customer only to deploy code; here the customer manages the OS.

Function as a Service (FaaS)

Why wrong: FaaS is a serverless computing model where code runs in response to events and the provider manages all infrastructure; not applicable here.

Platform as a Service (PaaS)

Why wrong: PaaS abstracts the operating system and middleware; the customer does not manage the OS. This scenario explicitly involves managing the OS, so PaaS does not fit.

Software as a Service (SaaS)

Why wrong: SaaS delivers fully managed applications accessed over the internet; the customer does not manage any infrastructure or the OS.

Desktop as a Service (DaaS)

Why wrong: DaaS is a virtual desktop infrastructure hosted in the cloud, not a general compute model for running applications on VMs.

Public cloud

Why wrong: Public cloud operates on shared infrastructure, which may not meet strict isolation requirements for regulations.

Hybrid cloud

Why wrong: Hybrid cloud combines public and private, but the core requirement is dedicated isolation, best met by private cloud alone.

Community cloud

Why wrong: Community cloud serves a group of organizations with similar needs, but the infrastructure is shared among that community, which may not satisfy strict single-organization isolation.

Infrastructure as a Service (IaaS)

Why wrong: IaaS provides virtualized computing resources like virtual machines and storage, but the customer manages the OS, middleware, and applications. It does not deliver ready-to-use applications.

Platform as a Service (PaaS)

Why wrong: PaaS provides a platform for developing, deploying, and managing applications, but not end-user software like email and office tools.

Desktop as a Service (DaaS)

Why wrong: DaaS delivers virtual desktop environments, enabling users to access a full desktop OS and applications from any device. It is not specifically for providing individual productivity applications as services.

Private cloud

Why wrong: A private cloud provides dedicated resources for a single organization, often on-premises, but does not integrate with public cloud services for analytics.

Public cloud

Why wrong: Using only a public cloud would require storing patient records off-premises, violating data sovereignty regulations.

Community cloud

Why wrong: Community cloud is shared among several organizations with common concerns (e.g., healthcare providers), but it does not inherently provide a split between on-premises and public cloud for data sovereignty.

Managing user passwords and accounts

Why wrong: User management (including passwords and accounts) is the responsibility of the customer, not the provider.

Configuring application settings for the organization

Why wrong: Customers configure their own application settings within the SaaS environment (e.g., tenant settings, user permissions).

Backing up customer data

Why wrong: While many providers offer backup capabilities, the customer is typically responsible for ensuring their data is recoverable, often using provider tools or their own processes.

PaaS (Platform as a Service)

Why wrong: PaaS manages the runtime and OS; the customer only manages applications and data.

SaaS (Software as a Service)

Why wrong: SaaS provides ready-to-use applications; the customer does not manage the underlying infrastructure or OS.

FaaS (Function as a Service)

Why wrong: FaaS is a serverless model where the provider runs code in response to events; the customer does not manage servers.

Elasticity

Why wrong: Elasticity refers to the ability to scale resources up/down based on demand, not the location of data.

High availability

Why wrong: High availability ensures services remain operational, but does not guarantee data is stored in a specific region.

Self-service

Why wrong: Self-service allows users to provision resources without IT intervention, but does not control where data resides.