CCNA Describe Azure architecture and services Questions

A resource group is a logical container in Azure that holds related resources for an application or solution, such as VMs, databases, and storage accounts. It enables you to manage those resources collectively, applying lifecycle operations like deployment, updating, and deletion as a unit. Access control is also scoped at the resource group level using Azure RBAC, and you can track costs for the group, though billing aggregates at the subscription. For organizing virtual machines specifically, the resource group is the precise, correct tier.

Azure Container Apps is a serverless container service built on Kubernetes that abstracts away the cluster's control plane, nodes, and maintenance. It provides built-in support for event-driven scaling via KEDA, service-to-service communication, and revision-based versioning, enabling you to deploy microservices and long-running processes without ever managing Kubernetes. This makes it the ideal choice when you need a fully managed platform for microservices orchestration with granular scaling and ingress rules, far beyond what simple container instances or web hosting can offer.

Azure Files provides fully managed cloud file shares that use the Server Message Block (SMB) and Network File System (NFS) protocols, making them directly mountable as network drives on Windows, Linux, and macOS. It supports standard file share features such as file locking, ACLs, and snapshotting, and it works with Azure File Sync to cache on-premises servers. Existing applications that rely on UNC paths or drive mappings can access Azure Files without code changes, offering a seamless lift-and-shift for on-premises file shares. This precisely matches the requirement of a shared network file share.

Azure Traffic Manager operates at the DNS layer, resolving user queries to the optimal regional endpoint based on priority, geographic proximity, or latency. It continuously health-checks endpoints and automatically redirects traffic away from an unavailable region, thereby achieving global failover. Unlike packet-level balancers, it never inspects or forwards packets directly.

An availability set is a logical container that tells the Azure Fabric to place VMs in different fault domains and update domains within the same datacenter. Fault domains isolate VMs onto separate physical racks with independent power and network switches, while update domains ensure planned maintenance does not reboot all VMs at once. This guarantees that a hardware failure in one rack will not affect VMs in other racks, directly satisfying the requirement for protecting a critical internal application against hardware failures.

Azure Computer Vision is a pre-built, general-purpose image analysis service that leverages trained machine learning models to do exactly what the question asks: it detects objects, brands, faces, and colors, extracts text via OCR, and generates human-readable descriptions of the image content. It requires no custom training and works out-of-the-box on a wide variety of images, which is why it is the correct choice for broad image analysis. This service is specifically designed to provide rich, contextual insights from images in a single API call.

Azure SQL Managed Instance is the correct choice because it provides full SQL Server engine compatibility, including SQL Agent and cross-database queries, which supports the vast majority of on-premises database features without requiring application redesign. It also offers native virtual network integration and automated backups, patching, and maintenance, giving the customer the same administrative simplicity as Azure SQL Database while retaining SQL Server's rich feature set. This makes it the ideal lift-and-shift target for migrating an on-premises SQL Server database.

For a single Azure VM, the monthly uptime SLA is 99.9%, provided all OS and data disks use Premium SSD or Ultra Disk storage. This guarantees connectivity but excludes failures due to unplanned maintenance or hardware faults that are outside Microsoft's control, and it does not cover in-guest application issues.

Azure Virtual Network Peering is the correct service because it enables direct, private connectivity between VNet A and VNet B regardless of their Azure regions, including East US and any other region, through Microsoft's backbone network. Global VNet peering uses private IP addresses without needing a gateway, VPN, or public internet, resulting in low-latency and high-bandwidth data transfer at standard networking costs. This approach is operationally simple, requiring only a peering relationship in each VNet, and avoids the added expense and routing complexity of alternate connectivity services.

Deployment slots are separate app service instances with distinct hostnames that share the same production plan. You can deploy a build to a staging slot, run validation tests, and then perform a zero-downtime swap with the production slot. The swap is instant because the two slots' backend instances are swapped, and rollback is immediate by swapping again, making this the only listed feature that directly supports staged release and instant rollback.

Azure Files offers fully managed, cloud-based file shares that support the SMB 3.0 protocol. It integrates with Azure AD DS or on-premises AD DS for authentication and can be mounted simultaneously by multiple Azure VMs. This meets all requirements.

Azure Cosmos DB is a fully managed NoSQL database that provides turnkey global distribution across multiple Azure regions. Its multi-region writes capability (often called multi-master) allows every region to accept both reads and writes, while guaranteeing single-digit millisecond latencies at the 99th percentile globally. This makes it the only option that natively supports the required multi-master write model with low-latency access worldwide.

Azure AD Domain Services is the correct answer because it provides a Microsoft-managed domain in Azure, exposing LDAP, Kerberos, NTLM, Group Policy, and domain-join capabilities without the operational burden of deploying and patching your own domain controllers. It synchronizes identity objects one-way from Azure AD, and through Azure AD Connect it can also receive on-premises Active Directory identities, which enables existing applications that use legacy authentication protocols to be lifted and shifted into Azure while retaining their directory service dependencies.

Azure Service Bus is an enterprise message broker that fully supports both queues for point-to-point communication and topic subscriptions for publish/subscribe patterns. It includes advanced reliability features such as sessions, transactions, duplicate detection, scheduled delivery, forwarding, and dead-letter queues, making it ideal for complex application integration. This is the correct answer because the question's requirement for a general-purpose message broker with topics and queues matches Service Bus exactly.

Azure Data Lake Storage Gen2 combines the scalability of Azure Blob Storage with a hierarchical namespace, enabling directory-level access control and atomic operations. It supports POSIX-like semantics and is natively integrated with big data analytics frameworks such as Hadoop, Spark, and Azure Synapse, making it the optimal choice for large-scale analytics workloads that require efficient directory management and fine-grained security.

Azure Container Instances (ACI) provides a serverless platform for running containers on demand, meaning you do not have to provision, manage, or scale any underlying virtual machines or orchestration clusters. Each container is directly placed on Azure's infrastructure and starts within seconds, with per-second billing and configurable CPU and memory limits. This makes ACI ideal for simple containerized applications, batch jobs, or ephemeral workloads where you want no infrastructure management. However, you still control the container image and environment variables, but you completely skip host-level patching and node pool administration.

Azure Pipelines is a cloud-hosted CI/CD service within Azure DevOps that automatically builds, tests, and deploys code to any platform or cloud. It supports YAML-based multi-stage pipelines, containers, and integration with GitHub and other repositories. For the vending machine scenario—where developers need a repeatable path to push updates—Pipelines is the correct managed service that executes the build, test, and deployment orchestration.

Azure Language Understanding (LUIS) is purpose-built to interpret natural language in interactive applications: you define intents (like 'OrderCoffee' or 'GetWeather') and entities (like 'size' or 'location'), then train the model with labeled example utterances. It learns to recognize variations, synonyms, and implicit context, and returns a JSON payload with the top-scoring intent and extracted entities for downstream code to act on. That is precisely the type of intelligent understanding needed to drive a dialog bot that can fulfill user requests.

Azure Virtual Machines are an Infrastructure-as-a-Service offering where each VM has its own Linux guest OS running on a Microsoft-managed hypervisor. You have full root/administrator access, letting you install custom kernel modules, use specialized drivers, modify system configuration, and run any long-lived application. This provides the complete OS-level control the scenario requires.

Azure Compute Gallery (formerly Shared Image Gallery) is the correct service because it's built specifically to store, version, and manage custom VM images and VM applications. It supports replication to multiple Azure regions for regional resilience and lets you share images across subscriptions and tenants using RBAC. Unlike the other options, it's designed for private internal sharing of VM images, not for code packages, containers, or public marketplace offerings.

Azure File Sync enables you to centralize file shares in Azure Files while maintaining the flexibility, performance, and compatibility of an on-premises file server. It provides cloud tiering to cache frequently accessed files locally and transparently recalls files from Azure on demand, offering a single namespace.

Azure Database for MySQL is the correct choice because it is a fully managed PaaS offering built on the open-source MySQL community engine. It natively supports the MySQL wire protocol and tools like mysql CLI and MySQL Workbench, making it drop-in compatible for existing MySQL workloads. The service provides built-in high availability, automated backups, and scaling without requiring you to manage infrastructure.

Availability Zones are physically separate datacenters within an Azure region, each with independent power, cooling, and networking. By placing VMs across multiple zones, you ensure that if an entire datacenter fails, the remaining zones continue to serve traffic, providing true datacenter-level redundancy. This architecture supports an SLA of up to 99.99% for VMs deployed across zones, making it the correct choice for a mission-critical application that must remain available during a facility outage.

Dedicated Host provides a physical server solely for one customer, meeting compliance requirements for hardware isolation.

Availability Zones are physically separate data centers within an Azure region. Deploying VMs across multiple zones ensures that a failure in one entire zone does not affect the others, providing high availability against data center outages.

Availability zones are physically separate datacenters within an Azure region, each with independent power, cooling, and networking. By deploying the critical application's VMs across two or more zones, the application remains online if an entire datacenter building fails, since traffic can be load-balanced to replicas in the surviving zones. This provides the highest level of resilience within a single region and directly satisfies the requirement for datacenter-level isolation.

Azure Spot VMs offer a steep discount (up to 90%) compared to pay-as-you-go by using unused Azure capacity, but Azure can evict them when it needs the capacity back. For a large analytics job that runs only a few hours at a time, eviction risk is manageable if the workload is interruptible and can be resumed. This makes Spot VMs the most cost-effective, appropriate choice for this scenario.

Azure Front Door is a global application delivery network that routes HTTP/HTTPS traffic to the nearest region using latency-based routing. It provides automatic failover across regions and includes a built-in web application firewall (WAF) to protect against common exploits at the network edge, making it the correct choice for the company’s requirements.

RA-GRS replicates data to a paired secondary region and provides read-only access to the secondary endpoint at all times. During a primary region outage, data can still be read from the secondary region without any manual action, meeting the compliance requirement.

Azure Queue Storage is a simple, cost-effective messaging service that stores large numbers of messages accessible via HTTP/HTTPS, designed to integrate applications by passing work between components. In this scenario, a front-end web app can write messages to a queue, and a back-end processor can independently poll and process them, allowing each tier to scale separately. This asynchronous message passing is exactly what decouples the web front-end from the back-end processor, making it the correct choice.

Azure Kubernetes Service (AKS) is a fully managed Kubernetes offering that offloads the control plane—including the API server, etcd, scheduler, and controller manager—to Azure, so you focus on deploying and managing containerized workloads on agent nodes. It provides native Kubernetes capabilities like automated rollouts, horizontal pod autoscaling, service discovery, and self-healing. This makes it the correct answer for a Kubernetes-based container orchestration service.

Azure Container Registry (ACR) is a managed, private Docker registry service built on Docker Registry 2.0, designed specifically for storing and managing container images and OCI artifacts. It supports geo-replication, role-based access control, and integration with AKS and ACI for secure image pulls. This exactly matches the requirement of storing and managing container images, so it is the correct answer.

The Archive tier offers the lowest storage costs and is designed for long-term retention of data that is rarely accessed. Retrieval times are measured in hours (up to 15 hours), which matches the company's acceptable delay. This is the most cost-effective choice.

Azure Virtual Network (VNet) creates a logically isolated segment in the Azure cloud, giving you control over IP address ranges, subnets, route tables, and network security groups. This isolation ensures resources like VMs and App Services can communicate privately within the VNet and securely connect to on-premises networks via VPN or ExpressRoute. Unlike public internet exposure, VNet provides a trusted boundary for your workloads, which is its core purpose.

Scaling out increases the number of VM instances running the App Service plan, allowing Azure's built-in load balancer to distribute incoming requests across all instances. For a predictable doubling of traffic, adding instances provides immediate additional compute capacity and is more cost-effective than scaling up, because you pay per-second for these standard-tier instances and can later scale back in. This manual operation takes effect within seconds to minutes, directly addressing the expected spike now.

ZRS replicates data synchronously across three Azure availability zones within the primary region. Each zone is a physically separate datacenter (or multiple datacenters) with independent power and networking. This protects against the failure of a single datacenter. ZRS is more expensive than LRS but less expensive than geo-redundant options, making it the most cost-effective choice for this requirement.

Azure DevOps is the correct answer because it is Microsoft's comprehensive DevOps platform, providing Azure Pipelines for build and release automation, Azure Repos for source control, Azure Boards for work item tracking, and Azure Artifacts for package management. This integrated suite supports CI/CD across multiple platforms and clouds, making it the first-party service designed to manage the entire application lifecycle and deployment pipeline to Azure.

Azure Firewall is a managed, cloud-native network firewall that provides centralized, stateful filtering of both outbound and inbound traffic. It supports FQDN-based rules, network rules based on IP/port/protocol, and integrates with Azure Monitor for logging and analytics. Threat intelligence filters can also block malicious traffic, making it the correct choice for advanced network-layer filtering.

Azure Application Gateway is a Layer 7 load balancer that includes built-in SSL termination (offload), cookie-based session affinity, and HTTP request routing. It is designed to distribute web traffic and maintain user session stickiness, making it the correct choice for this scenario.

Correct. Azure Bastion is a fully managed PaaS service that provides secure, browser-based RDP and SSH connectivity to Azure virtual machines directly from the Azure portal, over TLS. Because it is deployed inside the virtual network, VMs need no public IP addresses, no client software, and no VPN or ExpressRoute connection. Traffic is mediated by the Bastion instance, and you can enforce Azure RBAC and MFA on top of this access, making it the intended tool for securely administering internal VMs.

Azure Blob Storage is purpose-built for unstructured data, meaning any data that does not have a defined relational schema, such as images, videos, logs, and backup archives. It stores data as objects (blobs) within containers, with each blob having its own metadata and a unique URL, enabling efficient access via HTTP/HTTPS and integration with tools like AzCopy and Azure Data Factory. Blob Storage offers tiered storage (hot, cool, cold, archive), lifecycle management, and immutable storage policies, making it the optimal choice for massive-scale, low-cost storage of unstructured data.

Azure App Service can run containerized web applications and supports automatic scaling (horizontal scale) based on metrics like HTTP request rate or CPU utilization, without requiring any administrator to manage underlying VMs or orchestration pieces.

Azure Stack — specifically Azure Stack Hub — is a true hybrid cloud platform that extends Azure's core services (including IaaS and PaaS) into your own data center. It runs on certified hardware in your facility while staying operationally consistent with public Azure, enabling offline or edge scenarios with the same Azure portal, APIs, and tooling. This directly satisfies the requirement for a platform that brings Azure services and capabilities on-premises.

Azure Stream Analytics is a fully managed, real-time stream processing engine that ingests data from sources like Azure Event Hubs, IoT Hub, or Blob storage, and then runs continuous, SQL-like queries to detect patterns, aggregate metrics, or trigger alerts. It delivers sub-second-to-second latency analytics without requiring custom code for event handling, making it the optimal choice for real-time telemetry, sensor data, or financial transaction monitoring.

Azure Database for PostgreSQL is the fully managed Platform-as-a-Service (PaaS) offering for open-source PostgreSQL. It automatically handles high availability, patching, backups, and scaling, with performance tuning features such as intelligent insights. As the standard managed service for PostgreSQL in Azure, it lets developers focus on applications rather than infrastructure operations.

Spot VMs are the cheapest option because they run on unused Azure capacity at a steep discount (often up to 90% compared to pay-as-you-go). Since the described batch job is fault-tolerant and can be interrupted, it can handle the eviction notice Azure gives before reclaiming capacity. This makes Spot VMs the ideal cost-optimization choice despite the risk of eviction, as the job can simply pause and resume later.

Azure Bastion is a fully managed service that provides secure RDP and SSH access to Azure VMs directly from the Azure portal, using TLS over the internet. It is deployed inside the virtual network and does not require public IP addresses on the VMs, perfectly meeting the security policy requirements.

Azure SQL Database Serverless is the correct option because it automatically scales compute based on load and auto-pauses after a period of inactivity, at which point compute billing stops and only storage-related costs remain. It bills per second for the actual compute used, providing cost savings for irregular or bursty workloads. This is exactly the functionality the question describes, distinguishing it from provisioned tiers that run continuously.

Azure Dedicated Host provides physical servers dedicated to one Azure subscription. VMs are isolated at the hardware level, and the customer controls maintenance and scheduling. This fully satisfies the compliance requirement for physical server isolation.

Azure Dedicated HSM provides a single-tenant hardware security module appliance deployed directly into the customer's virtual network, giving them exclusive control over the physical device and full administrative access. It is FIPS 140-2 Level 3 validated, satisfying strict security and compliance requirements for cryptographic key storage and management. The customer manages the HSM themselves, with no shared infrastructure, which makes it the correct choice when an isolated, dedicated HSM is mandated.

Correct. Availability Zones are unique physical locations within an Azure region, each with independent infrastructure. Deploying VMs across multiple zones provides resiliency against datacenter failures while keeping the VMs in the same region for low latency.

Azure Cache for Redis is a managed, in-memory data cache service based on the Redis engine, delivering extremely low latency (sub-millisecond) and high throughput for frequently accessed data. It is purpose-built for caching workloads such as session state, API responses, and database query results, thereby offloading pressure from databases and improving application performance. This service directly matches the requirement for a dedicated caching solution, making it the correct answer.

Azure Form Recognizer (also known as Azure AI Document Intelligence) is the correct service because it uses machine learning models to extract text, key-value pairs, selection marks, and tables from forms and documents. It offers prebuilt models for invoices, receipts, and IDs, plus the ability to train custom models on domain-specific forms, making it purpose-built for turning unstructured or semi-structured documents into structured JSON output.

Azure region pairs are two Azure regions within the same geography (e.g., East US and West US) that are paired by Microsoft. They offer prioritized disaster recovery (one region is automatically prioritized for recovery) and sequential updates (only one region in the pair is updated during planned maintenance), making them the correct choice.

Synapse Analytics is Azure's integrated analytics platform designed specifically for petabyte-scale data warehousing and big data analytics. It unifies dedicated SQL pools, serverless SQL queries, and Apache Spark under one workspace, enabling large-scale parallel processing and seamless integration with Power BI and Azure Data Factory. This is why it is the correct choice for enterprise-grade analytical workloads.

Correct. When VMs are added to an availability set, Azure automatically distributes them across up to three fault domains and multiple update domains. This distribution ensures that a hardware failure or planned maintenance event affects only one fault domain or update domain at a time, keeping the other VM running.

Zone-Redundant Storage (ZRS) synchronously replicates your data across three distinct availability zones within the same Azure region. Each zone is an isolated location with independent power, cooling, and networking, so ZRS remains available through a single data-center failure. This is the correct answer because it specifically provides redundancy across availability zones, not just within one data center or across a paired region.

Azure Traffic Manager is a DNS-based traffic routing service that can direct users to the closest region using performance or geographic routing methods. It exposes a single DNS name, supports multi-region failover, and does not require SSL offloading or URL routing, making it the correct choice for this scenario.

Microsoft Defender for Cloud is a Cloud Security Posture Management (CSPM) and Cloud Workload Protection Platform (CWPP) that continuously assesses your Azure, on-premises, and multi-cloud resources against security benchmarks. It provides actionable hardening recommendations, detects threats, and integrates with Azure Policy to enforce governance. This makes it the correct service for both security posture management and broad threat protection across Azure and hybrid environments, covering compute, data, storage, and identities.

Azure NAT Gateway is a fully managed, highly resilient cloud-native service that provides outbound internet connectivity for virtual machines in private subnets within a virtual network. It performs source network address translation (SNAT) at scale, automatically handling port exhaustion by mapping multiple private IP addresses to a single public IP address or prefix. As a dedicated NAT service, it requires no manual configuration of rules or security policies, and it scales dynamically to meet outbound traffic demand. This makes it the correct and most appropriate solution for enabling outbound internet access from private resources in Azure.

Azure Blob Storage is a massively scalable object storage service designed to hold petabytes of unstructured data such as images, videos, documents, and backups. It exposes a REST-based HTTP/HTTPS API and SDKs, allowing clients to access blobs directly via URLs, with features like lifecycle management, geo-redundancy, and tiered storage (hot/cool/archive) to optimize cost and durability.

Azure HDInsight is a fully managed cloud service designed specifically for running open-source analytics frameworks, including Apache Spark, Hadoop, Hive, Kafka, and more. It provisions dedicated Spark clusters with built-in monitoring, scaling, and integration with Azure Storage and Data Lake Storage, making it the right choice for big data batch processing on Spark. This is why it is the correct answer among the options, as it directly provides the managed Spark cluster service called for in the question.

This is the correct choice because the Azure Cognitive Service for Language (formerly LUIS) is specifically built for natural language understanding, mapping user utterances to structured intents and entities. It uses machine learning models (e.g., intent classifiers and entity extractors) that are trained on labeled examples to recognize the user's goal (intent) and relevant keywords (entities). This capability directly addresses the requirement to understand natural language input, not just to transcribe or format it. Moreover, LUIS is the Azure service that provides the NLU layer that other services like Bot Service depend on for conversational comprehension.

Azure Key Vault Premium tier and Managed HSM are the only offerings that provide FIPS 140-2 validated HSM-backed key storage for customer-managed keys. Key Vault Premium uses shared HSMs (validated at Level 2) and supports cryptographic operations without keys leaving the HSM boundary. Managed HSM goes further with dedicated, single-tenant HSM partitions validated at Level 3, making it the right choice for the most demanding regulatory or sovereignty requirements. This is why they are correct for HSM-backed key protection.

Azure Cognitive Search is a cloud PaaS search engine that ingests content from Azure SQL, Blob Storage, Cosmos DB, and other sources, then enriches it with AI skills such as OCR, entity recognition, and key-phrase extraction. It creates an inverted index that supports full-text, fuzzy, and semantic search with features like autocomplete, synonyms, and custom scoring profiles. That combination of deep indexing and cognitive enrichment makes it the correct choice for searching business documents.

Azure Virtual Network is the logical, software-defined network that represents your own isolated slice of the Azure cloud. Through the VNet, you define private IP address spaces and carve out subnets for placing virtual machines, load balancers, and other resources, while controlling traffic with route tables and network policies. It is the fundamental building block for Azure networking, much like a traditional VLAN concept on a global scale.

Azure Container Instances (ACI) is the correct answer because it provisions a container directly on Azure infrastructure without any underlying virtual machines, cluster, or orchestrator for you to configure or maintain. Each container group is scheduled as a serverless resource, billed by the second, and starts in seconds, making it ideal for simple containerized workloads, event-driven tasks, or development/testing scenarios where the operational overhead of Kubernetes or VMs is unnecessary.

Azure Virtual Machine Scale Sets (VMSS) are a compute service that allows you to create and manage a group of load-balanced, identical VMs that automatically scale in and out based on performance metrics, such as CPU or memory utilization, or on a defined schedule. They ensure high availability by distributing instances across fault domains and availability zones, while the autoscaling rules dynamically add or remove instances to handle changes in workload demand. This makes VMSS the correct answer because it directly provides the capability to manage and automatically scale a set of identical VMs.

AKS with Cluster Autoscaler is the correct answer because the Cluster Autoscaler automatically adjusts the number of agent nodes in the AKS cluster based on pending pod scheduling requirements. When pods cannot be scheduled due to insufficient node resources, the autoscaler adds new nodes (up to the configured maximum), and when nodes are underutilized and pods can be rescheduled, it removes nodes. This directly scales the underlying infrastructure to match Kubernetes workload demands, unlike other services that scale at a different layer.

Azure Private DNS provides name resolution for resources inside virtual networks by hosting custom domain records that map to private IP addresses. It allows VMs and services to resolve internal hostnames without exposing those records to the public internet. This is the correct purpose: it gives private and reliable DNS within your virtual network, with support for split-horizon behavior and auto-registration.

Azure Data Explorer (ADX) is optimized for real-time analytics on time-series data from IoT and telemetry sources.

Archive tier provides the lowest per-gigabyte storage cost of all Azure Blob access tiers, making it the optimal choice for retaining log files that are rarely accessed. Data remains offline, and rehydration can take up to 15 minutes, but this high-latency access pattern is perfectly acceptable for logs that are only retrieved occasionally. Additionally, Archive has a 180-day minimum retention period, which aligns well with long-term archiving of application logs. This combination of minimal cost and tolerable latency makes Archive the correct tier.

Azure Hybrid Connections, a feature of Azure Relay, lets an Azure App Service securely reach an on-premises resource through an outbound WebSocket connection, avoiding any inbound firewall changes. The on-premises Hybrid Connection Manager (HCM) initiates the connection to the Relay namespace, and the Azure app sends requests via that relay. This works at the application layer and is ideal for connecting to legacy or on-premises systems without exposing them to the public internet.

Azure Bastion is correct because it provides secure, TLS-encrypted RDP/SSH access to Azure VMs directly from the Azure portal without requiring public IPs on the VMs or any client software, meeting all of the company's requirements.