Describe cloud concepts practice questions

IaaS and SaaS

Why it fails: SaaS is wrong because the company deploys and manages its own serverless microservices rather than consuming a provider-managed application. It is tempting because SaaS and serverless both hide infrastructure, but SaaS would be the correct model only for fully provider-managed software such as Microsoft 365.

PaaS and SaaS

Why it fails: PaaS and SaaS do not match the scenario: the company patches the VM operating system itself, which is IaaS, and serverless microservices are PaaS, not SaaS. It is tempting because PaaS covers serverless, but SaaS would be correct only for provider-managed applications such as Microsoft 365.

IaaS only

Why it fails: IaaS alone omits the serverless microservices component, which is PaaS because the provider manages the runtime while the company deploys code. It is tempting because the VM requirement clearly indicates IaaS, but it would be the correct single answer only if no serverless service were involved.

Microsoft Planner

Why it fails: Planner manages tasks and does not describe this cloud model or benefit.

Data Loss Prevention (DLP)

Why it fails: DLP protects sensitive information from inappropriate sharing, not this cloud concept.

Sensitivity labels

Why it fails: Sensitivity labels classify and protect content, not this cloud concept.

High availability and Disaster recovery

Why it fails: Incorrect. High availability ensures uptime; disaster recovery ensures business continuity. Neither addresses automatic scaling or pay-per-use billing.

Scalability and Fault tolerance

Why it fails: Incorrect. Scalability can be manual or automatic (elasticity is the automatic subset); fault tolerance is about continuing operation despite failures, not scaling or metered billing.

Agility and Resource pooling

Why it fails: Incorrect. Agility refers to speed of deployment; resource pooling refers to multi-tenant resource sharing. Neither describes automatic scaling or consumption-based billing.

The customer is responsible for patching the operating system of Exchange Online servers.

Why it fails: Exchange Online is a multitenant SaaS service, so Microsoft patches and manages the underlying operating systems and application servers on behalf of all customers. If customers had to patch Exchange Online servers, it would be an IaaS responsibility, not a SaaS one. Customers interact only with the Exchange Online endpoint and do not have administrative access to the underlying VM or OS.

Microsoft is responsible for ensuring customer data is backed up in all scenarios.

Why it fails: Microsoft provides some data protection and geo-redundancy by default, but the shared responsibility model does not guarantee backup of customer data in all scenarios. For example, Microsoft may delete data according to lifecycle policies, and customers are responsible for using features like Retention Labels, Legal Hold, and third-party backup tools to meet their own availability and recovery requirements. The customer's responsibility for data is often described as 'data is always yours and you are responsible for protecting it.'

The customer is responsible for physical security of client devices used to access Microsoft 365.

Why it fails: Client devices such as laptops, phones, and tablets used to access Microsoft 365 are owned and physically controlled by the customer. The shared responsibility model distinguishes between Microsoft's physical security of datacenters and the customer's responsibility for the physical security of their endpoints. Microsoft cannot control or enforce physical security of customer-owned devices, but it can apply Conditional Access to require compliant devices, though physical security remains with the customer.

Infrastructure as a Service (IaaS)

Why it fails: Incorrect. Infrastructure as a Service (IaaS) provides virtualized computing resources over the internet. This would require managing the operating system and applications, not just accessing corporate resources from personal devices without management.

Platform as a Service (PaaS)

Why it fails: Incorrect. Platform as a Service (PaaS) provides a platform for developing and deploying custom applications. The scenario describes using existing corporate resources, not developing new applications.

Desktop as a Service (DaaS)

Why it fails: Incorrect. Desktop as a Service (DaaS) delivers virtual desktops to users, which still requires management of the desktop environment. The scenario explicitly states 'without managing the entire device', so DaaS is not the best fit.

Latency

Why it fails: Latency is network delay, not data location.

Data sovereignty

Why it fails: Data sovereignty refers to data being subject to laws of the country where it is stored.

Compliance

Why it fails: Compliance is about adhering to regulations, not geographic storage.

Data sovereignty

Why it fails: Data sovereignty is incorrect because it refers to legal control over data based on geographic location, not a responsibility model for data usage.

Data residency

Why it fails: Data residency is incorrect because it concerns where data is stored physically, not how it is processed under a responsibility model.

Customer data protection

Why it fails: Customer data protection is not a cloud computing responsibility model; it is a policy that governs data usage, but the overarching model is the shared responsibility model.

Self-service

Why it fails: Self-service may not directly save costs.

Global scale

Why it fails: Global scale can increase costs.

Hybrid capabilities

Why it fails: Hybrid capabilities may require additional investment.

Private cloud

Why it fails: Private cloud does not use public cloud.

Community cloud

Why it fails: Community cloud may be on-premises or hosted, not necessarily public.

Multi-cloud

Why it fails: Multi-cloud uses multiple public clouds, but the question asks for models that 'involve using public cloud services', and multi-cloud is not a deployment model but an approach.

The user is excluded from the policy.

Why it fails: Only EmergencyAccount is excluded.

The policy requires multi-factor authentication.

Why it fails: The policy does require multi-factor authentication, but that is not the primary issue; modern auth clients could still satisfy MFA. The problem is that the legacy auth client is blocked entirely, regardless of MFA.

The policy does not apply to mobile devices.

Why it fails: The policy applies to all client app types including mobile.

Platform as a Service (PaaS)

Why it fails: PaaS provides a platform for developing and deploying applications without managing underlying infrastructure, but it is not used for migrating file servers to a SaaS solution like Microsoft 365.

Desktop as a Service (DaaS)

Why it fails: DaaS (Desktop as a Service) provides virtual desktop environments, not file server capabilities. It is irrelevant to migrating file servers to Microsoft 365.

Infrastructure as a Service (IaaS)

Why it fails: IaaS provides virtualized computing resources like VMs and storage. While it could host file servers, migrating on-premises file servers to Microsoft 365 specifically moves the workload to a SaaS platform, not IaaS.

Functions as a Service (FaaS)

Why it fails: FaaS is for event-driven functions, not ideal for a full custom application.

Software as a Service (SaaS)

Why it fails: SaaS offers ready-to-use software, not a platform for custom application development.

Infrastructure as a Service (IaaS)

Why it fails: IaaS requires management of VMs and typically involves paying for allocated capacity, not just consumption.

Community cloud

Why it fails: Community cloud is shared by several organizations, which does not guarantee data residency in a specific region for a single hospital.

Hybrid cloud

Why it fails: Hybrid cloud combines public and private cloud, but the public part may store data across regions, not ensuring data stays in one geographic area.

Public cloud

Why it fails: Public cloud may store data across multiple regions, failing to guarantee data residency in a specific geographic location.

Microsoft Viva Sales

Why it fails: Microsoft Viva Sales provides insights and productivity tools for sales, but it does not include AI-powered email drafting based on CRM data.

Dynamics 365 Sales

Why it fails: Dynamics 365 Sales is a comprehensive CRM platform, but it is not an AI tool for drafting emails; it manages customer relationships.

Microsoft Copilot for Microsoft 365

Why it fails: Microsoft Copilot for Microsoft 365 is a general AI assistant across Office apps, but it lacks the specific CRM integration required for drafting emails based on CRM data.

On-demand self-service

Why it fails: On-demand self-service allows users to provision resources without human interaction, but it does not directly enable the shift from capital to operational expense.

Broad network access

Why it fails: Broad network access ensures resources are accessible over the network, but it does not change the expenditure model.

Resource pooling

Why it fails: Resource pooling enables multi-tenancy and economies of scale, but it does not directly convert capital expense to operational expense.

Data classification

Why it fails: Classification labels data sensitivity but doesn't address storage location.

Data sovereignty

Why it fails: Data sovereignty is the legal concept, but the practical evaluation is about data residency.

Data encryption

Why it fails: Encryption protects data but doesn't control its geographic location.

The mailbox will have no retention policy applied

Why it fails: Incorrect. The retention policy is assigned and will be applied once the hold is removed; it is not absent.

The retention policy will be deleted from the mailbox

Why it fails: Incorrect. The retention policy is not deleted; it remains assigned but processing is suspended.

The mailbox will be placed on litigation hold

Why it fails: Incorrect. Litigation hold is a different feature; this command enables a retention hold.

Platform as a Service (PaaS)

Why it fails: PaaS is for developing and deploying custom applications, not for standard Office apps.

Infrastructure as a Service (IaaS)

Why it fails: IaaS would require virtual machines and manual installation of Office, not improving performance directly.

Function as a Service (FaaS)

Why it fails: FaaS runs code in response to events, not relevant to Office performance.

Community cloud

Why it fails: Community cloud is a shared infrastructure among multiple organizations with common concerns. It does not specifically allow an organization to run some workloads on-premises and some in the public cloud; it could be entirely on-premises or entirely in the cloud.

Private cloud

Why it fails: Private cloud is dedicated to a single organization and is typically hosted on-premises or in a colocation facility, not combined with public cloud.

Multi-cloud

Why it fails: Multi-cloud refers to using multiple public cloud services, but it does not include on-premises workloads.

Public cloud

Why it fails: Public cloud is fully hosted by a third-party provider and does not include on-premises infrastructure.