Microsoft Azure Fundamentals

❌ Incorrect. Review the explanation below.

❌ Incorrect. Review the explanation below.

Why the correct answer is right:
Azure Blueprints is a declarative orchestration service that enables cloud architects to define a repeatable set of Azure resources — including role assignments, policy assignments, ARM templates, and resource groups — and deploy them consistently across environments. It ensures governance standards are enforced at deployment time, making it perfect for this requirement.

→ Why the other options are wrong:

Option A – No: This is incorrect. Azure Blueprints is explicitly designed as a declarative deployment tool that supports role assignments and policy assignments as first-class artifacts.

Quick Memory Tip 🧠
→ "Azure Blueprints = Declarative deployment package (Roles + Policies + ARM templates + Resource Groups). Blueprint = Complete governance package!"

❌ Incorrect. Review the explanation below.

Why the correct answer is right:
Microsoft Office 365 (Microsoft 365) is a classic example of SaaS — you simply log in and use fully ready applications (Word, Excel, Teams, Outlook) over the internet. Microsoft manages everything: the infrastructure, platform, application updates, and security. The user only manages their data and account settings.

→ Why the other options are wrong:

Option A – Azure Virtual Machine service: VMs are IaaS — you manage the OS, middleware, and applications. You have full infrastructure control.

Option C – Azure App Service: App Service is PaaS — Microsoft manages the platform and infrastructure, but you manage your application code and data.

Option D – Azure Content Delivery Network Service: CDN is a PaaS/networking service — Microsoft manages the CDN infrastructure, and you configure content delivery rules. It is not a ready-to-use end-user application.

Quick Memory Tip 🧠
→ "SaaS = Just use the app (Office 365, Dynamics). PaaS = Build on the platform. IaaS = Manage the infrastructure."

Yes, this would give a cost breakdown for the resources being used in Azure.
An example is given below where you go to the Cost Analysis section in Cost Management.
For more information on Azure Cost Management, please visit the below URL

https://docs.microsoft.com/en-us/azure/cost-management/overview

→ Why Option C is right:
Each service serves a specific connectivity scenario. Service Endpoints extend VNet identity to Azure services. P2S is for individual remote users. S2S connects an entire on-premises network to Azure. ExpressRoute is the premium private, high-speed link that bypasses the public internet entirely.

→ Why the other options are wrong:

Options A, C, D: All incorrectly swap definitions — most commonly mixing up ExpressRoute with S2S VPN, and P2S with Service Endpoints.

Quick Memory Tip 🧠
→ P2S = One person, one computer | S2S = Office to Azure | ExpressRoute = Private highway, no internet | Service Endpoints = Azure-to-Azure secure access

Why the correct answer is right:
Azure DevTest Labs is purpose-built for this exact scenario. It allows teams to rapidly deploy VMs using ARM templates with pre-defined configurations and then automatically deprovision them on a schedule (auto-shutdown policies). It minimizes administrative effort by enabling self-service VM deployment with governance controls — ideal for weekly dev/test cycles.

→ Why the other options are wrong:

Option A – Azure Reserved VM Instances: Reserved Instances are a billing discount for committing to 1 or 3 years of VM usage. They reduce cost but do not help with automated provisioning or deprovisioning of VMs.

Option C – Azure Virtual Machine Scale Sets: Scale Sets are for auto-scaling identical VMs based on load. They are designed for production workloads — not for weekly deploy/remove dev/test cycles.

Option D – Microsoft Managed Desktop: Microsoft Managed Desktop is a managed Windows 10/11 desktop service for end users — not for developer VM lifecycle management.

Quick Memory Tip 🧠
→ "Deploy + Remove VMs regularly = Azure DevTest Labs. ARM templates + Auto-shutdown = Minimal admin effort!"

Why General Availability (GA) is right:
General Availability (GA) means a feature has completed evaluation, testing, and is now officially released for all Azure customers with full Microsoft support, SLAs, and production-readiness. It's the final stage in the Azure release cycle.

→ Why the other options are wrong:

Option A: Public Preview is still in the testing/evaluation phase — available to all customers, but NOT fully supported and NOT recommended for production workloads.

Option B: Private Preview is only for a limited, selected group of customers — it's the earliest, most restricted testing phase.

Option D: "General Preview" is not a valid Azure release stage — it doesn't exist in Microsoft's official release lifecycle.

Azure Release Cycle Summary:

Private Preview → Public Preview → General Availability (GA)
Limited users → All users (evaluation) → All users (production-ready ✅)

Quick Memory Tip 🧠
→ GA = "Graduation day — fully supported, production-ready, open to everyone!" 🎓

Why Update Domain is right:
Update Domains are part of an Availability Set configuration. They ensure that when Azure performs planned maintenance (OS patching, hardware updates), VMs are updated in sequence — not all at once. Each Update Domain is updated one at a time, preventing simultaneous downtime across your application.

→ Why the other options are wrong:

Option A: Fault Domains protect against unplanned hardware failures — like a rack power failure or a network switch going down. They separate VMs by physical rack, not by update sequence.

Option B: Availability Zones are physically separate datacenters within a region — they protect against full datacenter failures but don't manage update sequencing.

Option C: Load Balancing distributes incoming traffic across healthy instances — it doesn't control how or when Azure applies updates.

Key Distinction:

Quick Memory Tip 🧠
→ Update Domain = "Azure's update schedule — one group at a time, no full outage!" 🔄

Why "No change needed" is right:
During Public Preview, an Azure feature or service is made available to all Azure customers for evaluation. Anyone with an Azure subscription can test it. This is exactly what the statement describes — so the answer is correct as written, and no change is needed.

→ Why the other options are wrong:

• Option A: Enterprise Agreement (EA) subscription is a billing/purchasing model — it doesn't control which preview stage a service is in.
• Option B: Private Preview is available to only a limited, invited set of customers — not all Azure users. This would make the statement wrong.
• Option C: "Development" is not a valid Azure service release stage at all.

Azure Release Cycle:

Private Preview (limited users) → Public Preview (all customers) → General Availability / GA (fully supported, production-ready)

Quick Memory Tip 🧠
→ Available to ALL customers = Public Preview | Limited users only = Private Preview | Fully released = GA 🚀

Geo-Replication is an Azure SQL database feature that allows you to create a readable secondary database in the same region or cross-region. … Geo-replication uses the Always-on feature to replicate committed transactions to the secondary database asynchronously.
For more info : https://docs.microsoft.com/en-us/azure/sql-database/sql-database-active-geo-replication

Why the correct answer is right:
An Azure Subscription is the billing and access boundary that must exist before any resource can be deployed. Every Azure resource — VMs, storage, networks — must belong to a subscription so that billing can be processed. Without a subscription, you cannot create resource groups, virtual networks, or any other Azure service. It is always the first step.

→ Why the other options are wrong:

Option B – Resource Group: A Resource Group is a logical container for resources, but it must be created inside a subscription. You cannot have a Resource Group without a subscription first.

Option C – Virtual Network: A Virtual Network is a networking resource that requires both a subscription and a resource group to exist before it can be created.

Option D – Management Group: Management Groups are used to organize multiple subscriptions. You still need a subscription first — Management Groups sit above subscriptions in the hierarchy.

Quick Memory Tip 🧠
→ "Azure hierarchy: Management Group → Subscription → Resource Group → Resource. Subscription is ALWAYS step one!"

Why these three are right:

• Azure Portal is a web-based interface accessible from any browser on any device — including iPhones.
• Azure Cloud Shell is a browser-based command-line environment built into the Azure Portal — you can run CLI or PowerShell commands directly from a browser on your iPhone.
• Azure Mobile App is Microsoft's dedicated iOS and Android app for managing Azure resources — purpose-built for mobile management.

→ Why the other options are wrong:

• Option A: Azure CLI is a command-line tool that requires installation on a desktop OS (Windows, Linux, macOS) — it cannot run natively on an iPhone.
• Option D: Windows PowerShell requires a Windows operating system or PowerShell Core installed on a desktop/laptop — it cannot run on a mobile phone.

Quick Memory Tip 🧠
→ iPhone + Azure = Portal (browser) + Cloud Shell (browser terminal) + Mobile App (iOS app)
→ "If it needs a desktop install — it won't work on your phone!" 📱

Why A and C are right:
Azure App Service is a fully managed PaaS platform for hosting web and mobile apps. Azure SQL Database is a fully managed PaaS relational database. Azure Storage Accounts are also PaaS — Microsoft manages the underlying infrastructure. All three are valid PaaS services that meet the migration requirement.

→ Why the other options are wrong:

Option B: Azure Virtual Machines are IaaS — you manage the OS and runtime. This violates the PaaS-only requirement.

Option D: Azure Virtual Machines with SQL Server installed = IaaS again. Even though App Service is PaaS, the VM component disqualifies this option.

Quick Memory Tip 🧠
→ PaaS services = App Service + Azure SQL Database + Storage Accounts
→ "If it has a VM — it's IaaS, not PaaS!" ❌🖥️

Azure Time Series Insights Preview is an end-to-end platform-as-a-service (PaaS) offering. You can use it to collect, process, store, analyze, and query data at Internet of Things (IoT) scale–data that’s highly contextualized and optimized for time series.
Time Series Insights is designed for ad hoc data exploration and operational analysis. It’s an extensible and customized service offering that meets the broad needs of industrial IoT deployments.
Since this is clearly mentioned in the documentation, all other options are incorrect.
For more information on Azure Time Series Insights, please visit the below URL
https://docs.microsoft.com/en-us/azure/time-series-insights/time-series-insights-update-overview

What is the Azure Hybrid Benefit?
The Azure Hybrid Benefit is a pricing offer that helps you maximise the value of your existing on-premises Windows Server and/or SQL Server licence investment while you are migrating to Azure. With it, eligible customers pay a reduced rate on Azure Virtual Machines (infrastructure as a service or IaaS) and a reduced rate on Azure SQL Database (platform as a service or PaaS) and SQL Server on Azure Virtual Machines (IaaS).
*Actual savings may vary based on region, instance type or usage.
Which products are eligible for the Azure Hybrid Benefit?
Windows Server Standard Edition with Software Assurance
Windows Server Datacenter edition with Software Assurance
SQL Server Enterprise Core with Software Assurance
SQL Server Enterprise Core with Software Assurance
Azure SQL Database
Note: Customers eligible for Azure Hybrid Benefit can use this benefit in Azure Dedicated Host (more details in Windows Server and SQL Server sections)
Who is eligible for this offer?
Azure Hybrid Benefit is available to customers who own eligible SQL Server and/or Windows Server licenses with active Software Assurance or the equivalent qualifying subscription licenses.
The offer is available in all Azure cloud regions.
For more info : https://azure.microsoft.com/en-in/pricing/hybrid-benefit/faq/

❌ Incorrect. Review the explanation below.

Why the correct answer is right:
Azure Firewall is a fully managed, stateful network security service that can be deployed centrally in a hub VNet and filter traffic across multiple spoke VNets and subscriptions via hub-spoke topology. You can create, enforce, and log application and network connectivity policies centrally — making it the ideal solution for enterprise-wide traffic filtering across multiple subscriptions.

→ Why the other options are wrong:

Option B – Application Security Group (ASG): ASGs allow you to group VMs logically and define NSG rules based on those groups. They operate within a single VNet and cannot span multiple subscriptions.

Option C – Azure DDoS Protection: DDoS Protection defends against large-scale volumetric attacks. It does not filter or control regular application or network traffic flows.

Option D – Network Security Group (NSG): NSGs apply allow/deny rules at the subnet or NIC level within a single VNet. They cannot centrally manage traffic filtering across multiple subscriptions and VNets.

Quick Memory Tip 🧠
→ "Azure Firewall = Central filtering across multiple VNets + subscriptions. NSG = Single VNet only. DDoS = Attack protection only."

Why 99.95% is right:
For Virtual Machines deployed across two or more instances in an Availability Set, Microsoft guarantees 99.95% uptime. Availability Sets protect against hardware failures and planned maintenance within a single datacenter by using Fault Domains and Update Domains.

→ Why the other options are wrong:

Option A: 99.99% = This is the SLA for VMs deployed across two or more Availability Zones in the same region — a higher SLA due to greater physical separation.

Option C: 99.90% = This is the SLA for a single VM using Premium SSD or Ultra Disk — lower than Availability Set.

Option D: 99.94% = This is an example of a Composite SLA result (Availability Set + SQL Database) — not a standalone VM SLA tier.

Azure VM SLA Cheat Sheet:

Quick Memory Tip 🧠
→ Availability Set = 99.95% | Availability Zones = 99.99%
→ "More separation = higher SLA!" 📶

Why the correct answer is right:
Azure CDN caches large static content — including video files — at edge locations (Points of Presence) worldwide. When a user requests a video, it's served from the nearest edge server rather than the origin server, dramatically reducing latency and buffering. This provides the best video playback experience for global users.

→ Why the other options are wrong:

Option A – Network interface: A network interface enables a VM to communicate with networks. It plays no role in delivering web content or improving video playback for end users.

Option B – Azure Traffic Manager: Traffic Manager uses DNS-based routing to direct users to the best-performing region. It can reduce latency but would require hosting your app in multiple regions — much more complex and costly than CDN.

Option C – Application Gateway: Application Gateway is a Layer 7 load balancer with WAF. It improves application availability and security but does not cache or distribute video content globally.

Quick Memory Tip 🧠
→ "Global users + Big video files = CDN. Cache content at the edge. Less distance = Faster playback!"

Why the correct answer is right:
Each Azure DevOps tool has a distinct purpose: Repos = source code management (like GitHub). Boards = work item and sprint tracking (like Jira). Artifacts = package management for build outputs (like NuGet/npm feeds). Test Plans = manual and automated testing in CI/CD pipelines. Together they form a complete DevOps toolchain.

→ Why the other options are wrong:

Option A: Incorrectly maps Repos to "agile PM" (that's Boards) and Boards to "source code" (that's Repos) — swapped definitions.

Option C: Incorrectly assigns Artifacts to "source-code repository" — Artifacts hosts build packages, not raw source code.

Option D: Assigns Repos to "automated test tool" — that belongs to Test Plans.

Quick Memory Tip 🧠
→ "Repos = Code. Boards = Tasks. Artifacts = Packages. Test Plans = Testing. Remember: R-B-A-T!"

Creating polished Azure Automation runbook solutions to automate your Cloud OS processes can take time to perfect, and may feel a bit intimidating at first. Now the time it takes to create functional, polished runbooks is a little faster thanks to the new Azure Automation Runbook Gallery. The Runbook Gallery is a new feature for Azure Automation that puts existing Automation sample, utility, and scenario runbooks right at your fingertips to help you get up and running quickly with your automation tasks. The Runbook Gallery allows you to browse and import runbooks to your Automation account without having to leave the Azure Management Portal. While our product team has created some samples to get you started, the best part of the Runbook Gallery is that the community can contribute content and have it automatically show up in the Gallery. It’s likely that if you have a problem, someone out there has faced a similar issue and has developed an Automation solution that you can build on.
For more info : https://azure.microsoft.com/en-in/blog/introducing-the-azure-automation-runbook-gallery/

Azure monitor is not a global service. Please check below URL for more details-
https://docs.microsoft.com/en-us/windows-server/storage/storage-spaces/configure-azure-monitor

Why the correct answer is right:
Azure Files provides fully managed cloud file shares accessible via the SMB (Server Message Block) protocol — the same protocol used by Windows for network drives. Multiple Windows 10 computers can map the Azure file share as a network drive simultaneously, with both read and write access, just like a traditional on-premises file server.

→ Why the other options are wrong:

Option A – Blobs service: Azure Blob storage is for unstructured data (images, videos, backups) accessed via REST API or HTTP/HTTPS. It cannot be mapped as a network drive.

Option B – Azure SQL database: SQL Database is a relational database for structured data. It cannot function as a file share or network drive.

Option C – Virtual Machine Data disk: A VM data disk is a managed disk that can only be attached to one VM at a time. It cannot be shared across multiple Windows 10 computers as a network drive.

Quick Memory Tip 🧠
→ "Map a network drive = Azure Files (SMB). Multiple computers, shared access. Blob = API access only!"

You can easily search for custom solutions in the Azure Marketplace and even deploy these solutions onto Azure.
You can visit the Azure Marketplace via the following URL
https://azuremarketplace.microsoft.com/en-us/marketplace/
Option A is incorrect since there is no mention of the need of a scalable solution.
Option B is incorrect since this used to categorize resources.
Option D is incorrect since this used as a Platform as a service solution for web applications.

Apache Hadoop was the original open-source framework for distributed processing and analysis of big data sets on clusters. The Hadoop ecosystem includes related software and utilities, including Apache Hive, Apache HBase, Spark, Kafka, and many others.
Azure HDInsight is a fully managed, full-spectrum, open-source analytics service in the cloud for enterprises. The Apache Hadoop cluster type in Azure HDInsight allows you to use HDFS, YARN resource management, and a simple MapReduce programming model to process and analyze batch data in parallel.
To see available Hadoop technology stack components on HDInsight, see Components and versions available with HDInsight. To read more about Hadoop in HDInsight, see the Azure features page for HDInsight.
For more info : https://docs.microsoft.com/en-us/azure/hdinsight/hadoop/apache-hadoop-introduction

❌ Incorrect. Review the explanation below.

❌ Incorrect. Review the explanation below.

Why the correct answer is right:
Azure CDN (Content Delivery Network) is a service for caching and delivering web content (like images, videos, and static files) from edge locations closer to users. It is a networking/content delivery service — not a compute or serverless platform. It cannot execute scripts or run application code. The correct serverless service for running scripts is Azure Functions.

→ Why the other options are wrong:

Option A – Yes: This is incorrect. CDN has no capability to execute code or run scripts. It purely serves cached content to end users.

Quick Memory Tip 🧠
→ "CDN = Deliver content fast, NOT run code. Serverless code execution = Azure Functions only!"

Why the correct answer is right:
Azure Cosmos DB is a fully managed, globally distributed NoSQL database — Microsoft handles all infrastructure management including patching, scaling, backups, and replication. It also provides single-digit millisecond latency for reads and writes worldwide. Cosmos DB includes a Table API that supports Azure Table Storage-compatible workloads, making it perfect for hosting tables with zero administration and low latency.

→ Why the other options are wrong:

Option B – No: This is incorrect. Cosmos DB is a fully managed service (zero administration) with guaranteed low latency — it meets both requirements perfectly.

Quick Memory Tip 🧠
→ "Cosmos DB = Fully managed + Low latency + Global distribution. Tables, JSON, graphs — all supported. Zero admin!"

Why Multiplying is right:
A Composite SLA is calculated by multiplying the individual SLAs together. For example:

• App Service: 99.95%
• Azure SQL Database: 99.99%
• Composite SLA = 99.95% × 99.99% ≈ 99.94%

The result is always lower than either individual SLA because any single failure brings the whole application down.

→ Why the other options are wrong:

Option A: Taking the lowest SLA would underestimate reliability — it ignores the probability calculation.

Option B: Taking the highest SLA would overestimate reliability — it's mathematically incorrect for dependent services.

Option C: Averaging the SLAs is also incorrect and not how Microsoft calculates Composite SLA.

Composite SLA Formula:

Composite SLA = SLA₁ × SLA₂ × SLA₃ …
"The more services you add, the lower your composite SLA becomes!"

Quick Memory Tip 🧠
→ Composite SLA = Multiply all individual SLAs = "More services = more risk = lower combined SLA!" 📉

❌ Incorrect. Review the explanation below.

❌ Incorrect. Review the explanation below.

❌ Incorrect. Review the explanation below.

Why Access control (IAM) is right:
Access control (IAM) is the Azure portal blade used to assign RBAC roles to users, groups, or service principals for specific resources. You can assign the Virtual Machine Contributor role (or a custom role) to grant specific users only the ability to stop the VM — without giving them broader access.

→ Why the other options are wrong:

Option A: Tags are metadata labels for organizing and categorizing resources (e.g., Environment = Production) — they have no role in access control.

Option B: Networking controls how traffic flows to and from the VM — it does not manage user permissions.

Option C: Security in the Azure portal context covers threat protection settings — it does not grant or restrict user access to VM operations.

Quick Memory Tip 🧠
→ Grant/Restrict user access on a resource = Access control (IAM) = "IAM = Identity and Access Management!" 🔑

Why the correct answer is right:
In Private Preview, an Azure feature is available to select customers only for evaluation purposes. You must apply to Microsoft (usually via a nomination or sign-up form) and be approved before gaining access. This is different from Public Preview where anyone can use the feature freely.

→ Why the other options are wrong:

Option A – You must agree to terms of use first: Agreeing to terms of use is part of Public Preview access — not the defining characteristic of Private Preview. Private Preview requires an application and approval.

Option C – Available in the marketplace: Features in the marketplace are generally available (GA) or Public Preview. Private Preview features are not publicly listed in the marketplace.

Option D – You cannot use private preview services: This is false. You CAN use Private Preview services — but only after being accepted through the application process.

Quick Memory Tip 🧠
→ "Private Preview = Apply first, wait for approval. Public Preview = Available to everyone. GA = Fully released!"

Is Availability Zone different from Zone?
Yes. Availability Zone is different from Zone.
Zone is a geographical grouping of Azure Regions for billing purpose. Data transfer pricing is based on the Zones. For Zone details, please refer to FAQ below.
Availability Zone is an isolated location inside of an Azure Region, and has its own independent power source, network, and cooling. The physical and logical separation of Availability Zones within an Azure region protects applications and data from zone-level failures. Availability Zone data transfer pricing is based on Availability Zones.
Which regions correspond to Zone 1, Zone 2, Zone 3 and DE Zone 1?
A sub-region is the lowest level geo-location which you may select to deploy your applications and associated data. For data transfers (except CDN), the following regions correspond to Zone 1, Zone 2, Zone 3 and DE Zone 1.
Zone 1—Australia Central, Australia Central 2, Canada Central, Canada East, North Europe, West Europe, France Central, France South, Germany North (Public), Germany West Central (Public), Norway East, Norway West, Switzerland North, Switzerland West, UK South, UK West, Central US, East US, East US 2, North Central US, South Central US, West US, West US 2, West Central US
Zone 2—East Asia, Southeast Asia, Australia East, Australia Southeast, Central India, South India, West India, Japan East, Japan West, Korea Central, Korea
Zone 3—Brazil South, South Africa North, South Africa West, UAE Central, UAE North
DE Zone 1—Germany Central (Sovereign), Germany Northeast (Sovereign)
For more details : https://azure.microsoft.com/en-in/pricing/details/bandwidth/

❌ Incorrect. Review the explanation below.

→ Why Option A is right:
Private Cloud is exclusively for one organization — either on-premises or hosted, but restricted access. Public Cloud is owned by a provider like Azure and open to any paying customer. Hybrid Cloud integrates both, letting data and apps flow between private and public environments.

→ Why the other options are wrong:

Options B and C: Both swap the definitions between cloud types — a classic exam trap. Mixing Private and Hybrid definitions is the most common mistake.

Quick Memory Tip 🧠
→ Private = "Only for us!" | Public = "Open to everyone!" | Hybrid = "Best of both worlds!" 🔒🌐🔀

Why XLS is right:
The Azure Pricing Calculator allows you to download your cost estimates in Excel (.XLS) format. This makes it easy to share estimates with stakeholders, model different scenarios, and refine cost projections using spreadsheet tools.

→ Why the other options are wrong:

Option A: JSON is used for APIs and configuration files — it is not a download format for cost estimates.

Option C: XML is used for data exchange — it is not supported by the Azure Pricing Calculator as a download format.

Option D: CSV is a common data format but is not the format available for downloading Azure cost estimates. Only XLS is supported.

Quick Memory Tip 🧠
→ Azure Pricing Calculator download = XLS (Excel) = "Spreadsheet format — great for sharing with management!" 📊

Why Metadata is right:
Azure Tags store metadata about resources. A tag is a name-value pair — for example, Environment: Production or Department: Finance. This metadata helps with organizing, filtering, and billing analysis across your Azure resources. Tags don't enforce rules or grant permissions — they simply describe and label.

→ Why the other options are wrong:

Option B: Role defines what actions a user can perform on a resource (RBAC) — not what a tag is.

Option C: Permission is the outcome of a role assignment — it grants or denies access to resources.

Option D: Policy enforces rules and standards on resources — it's not what a tag represents.

Quick Memory Tip 🧠
→ Tags = Name + Value = Metadata = "Labels that describe your resources!" 🏷️

The Data Migration Assistant (DMA) helps you upgrade to a modern data platform by detecting compatibility issues that can impact database functionality in your new version of SQL Server or Azure SQL Database. DMA recommends performance and reliability improvements for your target environment and allows you to move your schema, data, and uncontained objects from your source server to your target server.
For more info : https://docs.microsoft.com/en-us/sql/dma/dma-overview?view=sql-server-ver15

References: https://docs.microsoft.com/en-us/azure/information-protection/compliance https://docs.microsoft.com/en-us/azure/information-protection/quickstart-label-dnf-protectedemail

❌ Incorrect. Review the explanation below.

❌ Incorrect. Review the explanation below.

Why Azure Policy is right:
Azure Policy allows you to define rules that automatically enforce compliance across your environment. By creating a policy that specifies allowed VM SKU sizes, Azure will block non-compliant VMs from being deployed at creation time AND evaluate existing VMs. This ensures governance without manual oversight.

→ Why the other options are wrong:

Option A: Manual inspection is reactive, not preventative. It won't stop non-compliant VMs from being deployed — it only catches them after the fact.

Option B: Azure RBAC controls who can perform actions — not what resources they can create. RBAC cannot restrict VM SKU sizes; only Azure Policy can enforce that.

Quick Memory Tip 🧠
→ Enforce resource rules automatically = Azure Policy = "Set the rules, Azure does the enforcement!" 📏

❌ Incorrect. Review the explanation below.