Azure Services practice questions

Availability sets

Why wrong: Availability sets protect against failures within a single datacenter, not across entire regions.

Availability zones

Why wrong: Availability zones protect against datacenter failures within a region, not a full regional outage.

Load balancer

Why wrong: Load balancer distributes traffic but does not provide cross-region failover.

A) Scalability

Why wrong: Scalability is about handling increased load, not regional disaster recovery.

B) Elasticity

Why wrong: Elasticity allows dynamic scaling, not specifically for disasters.

C) High availability

Why wrong: High availability typically covers failures within a datacenter or region, not a full regional outage.

Azure VPN Gateway

Why wrong: Azure VPN Gateway creates an encrypted tunnel over the public internet. While it provides a secure connection, it does not offer a private connection that bypasses the public internet, and bandwidth and latency are typically lower and less consistent than ExpressRoute.

Azure Firewall

Why wrong: Azure Firewall is a managed network security service that helps protect Azure virtual network resources. It does not provide a connectivity service between on-premises and Azure.

Azure Front Door

Why wrong: Azure Front Door is a global load balancer and content delivery network that operates over the public internet. It is designed for web applications and does not provide a private dedicated connection between an on-premises network and Azure.

Public cloud

Why wrong: Incorrect because a public cloud deployment model uses only cloud resources hosted by a third-party provider. The firm also uses an on-premises data center, so it is not purely public cloud.

Private cloud

Why wrong: Incorrect because a private cloud deployment model is dedicated to a single organization and usually resides on-premises or in a hosted private environment. The firm also uses public cloud services, so it is not purely private cloud.

Community cloud

Why wrong: Incorrect because a community cloud is a collaborative deployment model shared among several organizations with common regulatory or compliance needs. This scenario involves only one firm, not a community.

Azure Reserved Instances

Why wrong: Reserved Instances are a billing and pricing model that offers discounted rates in exchange for a one- or three-year commitment. They do not provide any physical server isolation; VMs purchased under Reserved Instances may still run on shared physical hardware.

Azure Virtual Machine Scale Sets

Why wrong: Virtual Machine Scale Sets allow you to deploy and manage a group of identical, load-balanced VMs that can scale in or out automatically. They do not guarantee that the VMs are placed on a dedicated physical host; the underlying hardware may be shared with other tenants.

Azure Confidential Computing

Why wrong: Confidential computing protects data in use by using hardware-based trusted execution environments (e.g., Intel SGX). While this provides strong data encryption during processing, it does not ensure that the entire physical server is dedicated to a single customer. Multiple tenants' VMs using confidential computing can still reside on the same physical host.

Public cloud

Why wrong: Incorrect. A public cloud would host all resources in Azure, which would place sensitive customer data on Microsoft's infrastructure, likely violating regulatory mandates. The institution specifically needs on-premises control for that data.

Private cloud

Why wrong: Incorrect. A private cloud is dedicated to a single organization, but if it remains entirely on-premises, the institution cannot use Azure's scalable analytics services without building a separate on-premises cloud, which defeats the purpose of leveraging Azure's PaaS/IaaS.

Community cloud

Why wrong: Incorrect. A community cloud is shared by several organizations with common concerns (e.g., compliance, security). While it could be used, it does not inherently address the need to keep data on-premises while using Azure separately. The hybrid model is the standard approach for such scenarios.

Azure IoT Hub

Why wrong: IoT Hub manages cloud-to-device communication; IoT Edge runs workloads on edge devices themselves.

Azure Stack Edge

Why wrong: Azure Stack Edge is a hardware device for edge computing; IoT Edge is the software platform for IoT edge deployment.

Azure Arc for IoT

Why wrong: Azure Arc manages non-Azure resources; IoT Edge specifically deploys Azure workloads to IoT edge devices.

Azure Monitor

Why wrong: Azure Monitor is for monitoring performance and health of your own resources, not for Azure platform service issues.

Azure Advisor

Why wrong: Azure Advisor provides recommendations to optimize your environment, not alerts about service outages.

Azure Resource Health

Why wrong: Resource Health shows the health of your individual resources, not Azure service-wide outages.

Azure Container Instances (ACI)

Why wrong: ACI runs individual containers quickly but does not provide orchestration features like automatic scaling, service discovery, or rolling updates.

Azure App Service

Why wrong: App Service can host web apps and APIs but is not designed for container orchestration; it uses a container runtime but lacks native Kubernetes capabilities.

Azure Functions

Why wrong: Functions is for event-driven, serverless code snippets, not for managing a set of microservices with orchestration requirements.

Azure Policy

Why wrong: Azure Policy is used to enforce compliance rules on existing resources (e.g., requiring tags or encryption). It cannot deploy new infrastructure, assign roles, or package multiple components into a single deployable artifact. While policies can be included in a blueprint, Azure Policy alone does not meet the full requirement.

Azure Resource Manager (ARM) templates

Why wrong: ARM templates are infrastructure-as-code files that deploy Azure resources. However, they do not natively include role assignments or policy assignments in a governance-focused way. You can embed those using nested templates and custom scripts, but ARM templates lack built-in versioning for governance artifacts and are not designed specifically as a governance packaging tool.

Azure Management Groups

Why wrong: Management Groups provide a hierarchical structure for organizing subscriptions and applying access control (RBAC) and policies at scale. They do not deploy resources or define the composition of an environment. Management Groups are used to organize subscriptions, not to package and deploy a standardized environment.

Scalability

Why wrong: Scalability is the ability to increase or decrease resources to meet demand. While the solution could be scaled, the primary focus is on geographic distribution to reduce latency, not on handling increased traffic volume.

Elasticity

Why wrong: Elasticity is the ability to automatically adjust resources based on real-time demand. The scenario does not mention dynamic scaling; it emphasizes deploying in multiple regions for proximity to users.

High availability

Why wrong: High availability ensures that applications remain operational despite failures. Deploying in multiple regions can improve availability, but the stated goal is to resolve slow load times and timeouts for remote users, which is a latency issue, not primarily an availability concern.

High availability

Why wrong: High availability ensures that services remain accessible during failures, but it does not inherently provide automatic scaling.

Disaster recovery

Why wrong: Disaster recovery focuses on recovering from catastrophic failures, not on scaling resources dynamically.

Fault tolerance

Why wrong: Fault tolerance allows a system to continue operating after component failures, but it does not automatically adjust capacity.

Azure Container Instances

Why wrong: ACI runs individual containers quickly but does not provide orchestration, auto-scaling, or service discovery across multiple containers.

Azure Batch

Why wrong: Azure Batch is for large-scale parallel and batch compute jobs, not for running microservices with continuous scaling.

Azure Virtual Machine Scale Sets

Why wrong: VM scale sets offer auto-scaling for VMs, but you still manage the OS and container hosting; they lack native container orchestration.

Infrastructure as a Service (IaaS)

Why wrong: IaaS provides virtual machines, storage, and networks. The customer is responsible for managing the operating system, middleware, and runtime. This still requires maintenance effort.

Software as a Service (SaaS)

Why wrong: SaaS provides ready-to-use applications like Office 365. The customer does not write code; they use the software. This does not fit building a custom mobile app backend.

Function as a Service (FaaS)

Why wrong: FaaS (e.g., Azure Functions) allows running small pieces of code in response to events. While it abstracts infrastructure, it is typically used for microservices or event-driven scenarios, not for a full backend application that might need a persistent server. The scenario describes a broader mobile app backend, which is better served by PaaS.

Azure Monitor

Why wrong: Azure Monitor collects and analyzes your resource metrics and logs, not Azure service health events.

Azure Advisor

Why wrong: Azure Advisor provides optimization recommendations, not service health notifications.

Azure Status Page

Why wrong: Azure Status is a global page; Service Health provides personalized, region/service-specific notifications.

Azure Cognitive Services

Why wrong: Cognitive Services provides pre-built AI APIs; Azure ML is for training custom models.

Azure Databricks

Why wrong: Databricks is an Apache Spark analytics platform; Azure ML is specifically for machine learning workflows.

Azure Synapse Analytics

Why wrong: Synapse Analytics is for data warehousing and analytics, not primarily ML model training.

Public cloud

Why wrong: In a public cloud, all resources are owned and operated by the cloud provider, which may not meet data residency requirements.

Private cloud

Why wrong: A private cloud is dedicated to a single organization, often on-premises, but it does not leverage public cloud services for less sensitive workloads.

Community cloud

Why wrong: Community cloud is shared by several organizations with common concerns; it is not specific to mixing on-premises and public cloud.

Azure Policy

Why wrong: Incorrect. Azure Policy enforces rules and effects on resources, but does not deploy resource templates or RBAC assignments.

Azure Resource Manager

Why wrong: Incorrect. Azure Resource Manager is the service for managing resources, but it does not package policies and roles as a single deployable unit.

Azure Management Groups

Why wrong: Incorrect. Management Groups organize subscriptions hierarchically for policy and access management, but they do not define the environment contents.

High availability

Why wrong: High availability ensures that applications and data remain accessible despite component failures. While Azure provides availability guarantees, the question focuses on the shift from upfront hardware purchases to monthly consumption-based payments, not on uptime or fault tolerance.

Elasticity

Why wrong: Elasticity is the ability to automatically scale resources up or down based on demand. Although Azure enables elasticity, the scenario specifically describes a change in financial model (upfront cost vs. monthly consumption), not the ability to adjust resource quantity dynamically.

Disaster recovery

Why wrong: Disaster recovery involves replicating data and applications to another region to protect against catastrophic failures. The question does not mention any backup, replication, or recovery requirements; it focuses solely on the financial purchasing model.

Azure Machine Learning

Why wrong: Azure ML is for training custom models; Cognitive Services provides pre-built AI APIs.

Azure Databricks

Why wrong: Databricks is for data engineering and ML engineering with custom development.

Azure Bot Service

Why wrong: Bot Service builds chatbot interfaces; Cognitive Services provides the underlying AI capabilities.