AZ-900 Objective 2.1: Describe the Core Architectural Components of Azure

•29 min read•Microsoft Azure Fundamentals

AZ-900 Exam Focus: This objective covers the fundamental architectural components that make up the Azure cloud platform. You need to understand how Azure organizes its global infrastructure through regions, availability zones, and data centers, as well as how resources are organized through resource groups, subscriptions, and management groups. This knowledge is essential for understanding Azure's global reach, reliability, and organizational structure.

Understanding Azure's Global Architecture

Azure's global architecture is designed to provide reliable, scalable, and secure cloud services to customers worldwide through a sophisticated network of data centers, regions, and availability zones. This distributed architecture enables Azure to deliver high availability, low latency, and compliance with local regulations while providing customers with the flexibility to deploy applications and data in locations that meet their specific requirements. Understanding this architecture is crucial for making informed decisions about where to deploy Azure resources and how to design applications for optimal performance and reliability.

Azure's architectural components work together to create a comprehensive cloud platform that spans the globe, with each component serving specific purposes in the overall infrastructure. These components include physical data centers, logical regions, availability zones for redundancy, and organizational structures for managing resources and access. This hierarchical organization enables both technical capabilities like high availability and disaster recovery, as well as business capabilities like cost management and governance.

Azure Regions

Definition and Purpose of Azure Regions

Azure regions are geographic areas that contain one or more data centers and are connected through a dedicated low-latency network. Each region is designed to be independent and self-contained, providing customers with the ability to deploy applications and data in specific geographic locations to meet compliance, performance, and data residency requirements. Regions serve as the primary building blocks of Azure's global infrastructure, enabling customers to choose where their data and applications are located based on their specific needs and requirements.

Azure regions are strategically distributed around the world to provide global coverage while minimizing latency and ensuring compliance with local regulations. Each region contains multiple data centers and is connected to other regions through Azure's global network backbone, which provides high-speed, reliable connectivity between regions. This global distribution enables customers to deploy applications close to their users for optimal performance while maintaining the ability to replicate data and applications across regions for disaster recovery and high availability.

Key Characteristics of Azure Regions

Primary Features of Azure Regions:

  • Geographic distribution: Azure regions are distributed across multiple continents and countries to provide global coverage and enable customers to deploy resources close to their users. This geographic distribution helps minimize latency and ensures compliance with data residency requirements in different jurisdictions.
  • Independent infrastructure: Each Azure region operates independently with its own power, cooling, and networking infrastructure to ensure that issues in one region do not affect other regions. This independence provides isolation and enables customers to design applications that can survive regional outages.
  • Low-latency connectivity: Regions are connected through Azure's global network backbone, which provides high-speed, low-latency connectivity between regions. This connectivity enables customers to replicate data and applications across regions while maintaining performance.
  • Compliance and data residency: Azure regions are designed to meet local compliance requirements and enable customers to keep their data within specific geographic boundaries. This capability is essential for organizations that must comply with data protection regulations and data residency requirements.
  • Service availability: Different Azure services may be available in different regions, and new services are typically rolled out to regions over time. Customers can check service availability in specific regions to ensure that the services they need are available in their chosen deployment locations.

Selecting the Right Azure Region

⚠️ Key Factors for Region Selection:

  • Latency requirements: Choose regions that are geographically close to your users to minimize latency and improve application performance. Consider the network connectivity between your users and the Azure region to ensure optimal performance.
  • Compliance requirements: Select regions that meet your compliance and data residency requirements, especially for regulated industries or organizations with specific data protection needs. Some regions are designed specifically for compliance with certain regulations.
  • Service availability: Ensure that the Azure services you need are available in your chosen region, as not all services are available in all regions. Check the Azure services by region documentation to verify service availability.
  • Cost considerations: Azure pricing can vary by region, so consider the cost implications of deploying resources in different regions. Some regions may offer lower costs for certain services or resource types.
  • Disaster recovery planning: Consider deploying resources across multiple regions to ensure business continuity and disaster recovery capabilities. This approach provides redundancy and enables rapid recovery from regional outages.

Azure Region Pairs

Understanding Region Pairs

Azure region pairs are two regions within the same geography that are paired together for disaster recovery and high availability purposes. These pairs are carefully selected to ensure that they are far enough apart to avoid being affected by the same natural disasters or large-scale outages, while being close enough to provide reasonable latency for replication and failover scenarios. Region pairs are automatically assigned by Microsoft and cannot be changed by customers, ensuring optimal pairing based on geographic and infrastructure considerations.

Region pairs provide several important benefits for disaster recovery and high availability scenarios. They enable automatic replication of certain Azure services, provide coordinated updates to minimize downtime, and ensure that at least one region in each pair is prioritized for recovery during major outages. This pairing system is designed to provide customers with reliable disaster recovery capabilities without requiring them to manually select and configure paired regions.

Benefits of Region Pairs

Key Advantages of Azure Region Pairs:

  • Automatic replication: Certain Azure services automatically replicate data between region pairs to provide built-in disaster recovery capabilities. This automatic replication ensures that data is protected without requiring manual configuration or management.
  • Coordinated updates: Microsoft coordinates updates between region pairs to ensure that at least one region in each pair remains available during planned maintenance. This coordination minimizes downtime and ensures continuous service availability.
  • Priority recovery: During major outages, Microsoft prioritizes recovery of one region in each pair to ensure that customers have access to at least one region for their critical workloads. This priority system helps ensure rapid recovery and business continuity.
  • Geographic separation: Region pairs are selected to ensure sufficient geographic separation to avoid being affected by the same natural disasters or large-scale outages. This separation provides protection against regional disasters and ensures reliable disaster recovery.
  • Compliance support: Region pairs are designed to support compliance requirements by ensuring that data can be replicated within the same geography or compliance boundary. This capability helps organizations meet data residency and compliance requirements.

Azure Sovereign Regions

Definition and Purpose of Sovereign Regions

Azure sovereign regions are specialized Azure regions that are designed to meet specific compliance, security, and data residency requirements for government entities and organizations in regulated industries. These regions operate under different legal and regulatory frameworks and are isolated from the commercial Azure regions to ensure compliance with government requirements and data sovereignty laws. Sovereign regions provide the same Azure services and capabilities as commercial regions but with additional controls and compliance features.

Sovereign regions are typically operated by local entities or government agencies in partnership with Microsoft, ensuring that data and services remain under local control and jurisdiction. These regions are designed to meet the highest security and compliance standards required by government organizations and regulated industries, providing isolation from commercial Azure services and ensuring that data remains within specific geographic and legal boundaries.

Types of Sovereign Regions

Primary Sovereign Region Types:

  • Azure Government: Azure Government regions are designed specifically for US government agencies and their partners, providing services that meet US government compliance requirements including FedRAMP, ITAR, and other federal standards. These regions are operated by US persons and provide additional security controls and compliance features.
  • Azure China: Azure China regions are operated by 21Vianet in partnership with Microsoft, providing Azure services that comply with Chinese regulations and data residency requirements. These regions are designed to meet Chinese government requirements and provide services to customers in China.
  • Azure Germany: Azure Germany regions were designed to meet German data protection requirements and were operated by a German data trustee. These regions provided additional data protection and compliance features for German customers and organizations with German data residency requirements.
  • Other sovereign clouds: Microsoft continues to work with governments and organizations worldwide to provide sovereign cloud solutions that meet specific regional compliance and data residency requirements. These solutions are tailored to meet the unique needs of different countries and regulatory environments.

Azure Availability Zones

Understanding Availability Zones

Azure Availability Zones are unique physical locations within an Azure region that are designed to provide high availability and fault tolerance for applications and data. Each availability zone consists of one or more data centers equipped with independent power, cooling, and networking infrastructure, ensuring that failures in one zone do not affect other zones within the same region. Availability Zones enable customers to design applications that can survive data center failures and provide high availability for critical workloads.

Availability Zones are connected through high-speed, low-latency networking to enable synchronous replication and rapid failover between zones. This connectivity allows applications to be deployed across multiple zones for redundancy while maintaining performance and data consistency. The availability zone architecture is designed to provide protection against data center failures, power outages, and other infrastructure issues that could affect application availability.

Key Benefits of Availability Zones

Primary Advantages of Azure Availability Zones:

  • High availability: Availability Zones provide protection against data center failures by enabling applications to be deployed across multiple independent data centers. This redundancy ensures that applications remain available even when individual data centers experience outages or failures.
  • Fault tolerance: Applications deployed across multiple availability zones can automatically failover to healthy zones when failures occur, providing seamless continuity of service. This fault tolerance is essential for critical applications that require high availability and reliability.
  • Low latency replication: Availability Zones are connected through high-speed networking that enables synchronous replication of data and applications with minimal latency. This low-latency connectivity ensures that failover can occur quickly without significant data loss or performance impact.
  • Independent infrastructure: Each availability zone operates with independent power, cooling, and networking infrastructure to ensure that failures in one zone do not affect other zones. This independence provides isolation and ensures that zone failures are contained.
  • Compliance support: Availability Zones help organizations meet compliance requirements for high availability and disaster recovery by providing built-in redundancy and fault tolerance capabilities. This compliance support is essential for regulated industries and critical applications.

Availability Zone Deployment Strategies

⚠️ Best Practices for Availability Zone Deployment:

  • Multi-zone deployment: Deploy critical applications across multiple availability zones to ensure high availability and fault tolerance. This approach provides protection against zone failures and ensures continuous service availability.
  • Synchronous replication: Use synchronous replication for critical data to ensure that data is consistent across availability zones and that failover can occur without data loss. This approach provides the highest level of data protection and consistency.
  • Load balancing: Implement load balancing across availability zones to distribute traffic and ensure optimal performance. This approach helps prevent any single zone from becoming overloaded and provides better overall application performance.
  • Monitoring and alerting: Implement comprehensive monitoring and alerting to detect zone failures and ensure rapid response to issues. This monitoring helps ensure that problems are identified and resolved quickly to minimize impact on applications.
  • Testing and validation: Regularly test failover procedures and validate that applications can successfully recover from zone failures. This testing ensures that disaster recovery procedures work correctly and that applications can maintain availability during outages.

Azure Data Centers

Physical Infrastructure of Azure Data Centers

Azure data centers are the physical facilities that house the servers, storage systems, and networking equipment that power Azure services. These data centers are designed and operated to meet the highest standards for security, reliability, and environmental sustainability, providing the foundation for Azure's global cloud infrastructure. Each data center is equipped with redundant power systems, advanced cooling technologies, and comprehensive security measures to ensure continuous operation and protection of customer data and applications.

Azure data centers are strategically located around the world to provide global coverage while meeting local requirements for power, connectivity, and environmental conditions. These facilities are designed to be highly efficient and environmentally sustainable, using renewable energy sources and advanced cooling technologies to minimize environmental impact. The data centers are also designed to be secure and resilient, with multiple layers of physical and logical security to protect against unauthorized access and ensure the integrity of customer data.

Data Center Design and Features

Key Features of Azure Data Centers:

  • Redundant power systems: Azure data centers are equipped with redundant power systems including multiple power feeds, backup generators, and uninterruptible power supplies (UPS) to ensure continuous operation even during power outages. This redundancy provides protection against power failures and ensures high availability of services.
  • Advanced cooling systems: Data centers use advanced cooling technologies including air-side economization and liquid cooling to maintain optimal operating temperatures for servers and equipment. These cooling systems are designed to be energy-efficient and environmentally sustainable while ensuring reliable operation.
  • Comprehensive security: Data centers implement multiple layers of security including physical barriers, access controls, surveillance systems, and security personnel to protect against unauthorized access and ensure the security of customer data and applications.
  • Environmental sustainability: Azure data centers are designed to be environmentally sustainable, using renewable energy sources, energy-efficient equipment, and sustainable building practices to minimize environmental impact and support Microsoft's carbon negative commitment.
  • High-speed connectivity: Data centers are connected through high-speed fiber optic networks that provide low-latency connectivity to other Azure regions and the internet. This connectivity enables global reach and ensures optimal performance for customer applications.

Azure Resources and Resource Groups

Understanding Azure Resources

Azure resources are the individual services and components that customers can create and manage in Azure, such as virtual machines, storage accounts, databases, and web applications. Each resource has specific properties and capabilities that define its functionality and behavior, and resources can be configured and managed independently or as part of larger solutions. Resources are the fundamental building blocks of Azure solutions, and understanding how to create, configure, and manage resources is essential for using Azure effectively.

Azure resources are created and managed through the Azure portal, Azure CLI, Azure PowerShell, or Azure Resource Manager templates, providing customers with multiple options for resource management. Each resource has a unique identifier and can be tagged with metadata to help with organization, billing, and management. Resources can also be associated with specific Azure services and can have dependencies on other resources, creating complex solutions that work together to meet business requirements.

Understanding Resource Groups

Azure Resource Groups are logical containers that hold related Azure resources for an Azure solution, providing a way to organize and manage resources as a single unit. Resource groups serve as the fundamental unit of management in Azure, enabling customers to deploy, update, and delete all resources in a group together, as well as apply access control and policies to all resources in the group. This logical organization simplifies resource management and provides a foundation for governance and cost management.

Resource groups provide several important benefits for resource management and organization. They enable customers to group related resources together for easier management, apply consistent policies and access controls across multiple resources, and simplify billing and cost tracking by organizing resources by project, environment, or business unit. Resource groups also provide a foundation for automation and deployment, enabling customers to deploy entire solutions as a single unit.

Resource Group Best Practices

Key Guidelines for Resource Group Organization:

  • Logical grouping: Group resources that share the same lifecycle, such as resources that are deployed, updated, and deleted together. This approach simplifies management and ensures that related resources are managed as a cohesive unit.
  • Consistent naming: Use consistent naming conventions for resource groups to make them easy to identify and manage. Include information such as environment (dev, test, prod), project name, and resource type in the naming convention.
  • Access control: Apply access control and policies at the resource group level to ensure consistent security and governance across all resources in the group. This approach simplifies security management and ensures that all resources follow the same security policies.
  • Cost management: Use resource groups to organize resources for cost tracking and budgeting, grouping resources by project, department, or cost center. This organization helps with cost allocation and budget management.
  • Deployment automation: Use resource groups as the foundation for automated deployment and management, enabling entire solutions to be deployed and managed as a single unit. This approach simplifies deployment and ensures consistency across environments.

Azure Subscriptions

Definition and Purpose of Subscriptions

Azure subscriptions are logical containers that provide a way to organize and manage Azure resources, billing, and access control. Each subscription is associated with a billing account and provides a boundary for resource management, cost tracking, and access control. Subscriptions serve as the fundamental unit of billing and access management in Azure, enabling customers to organize their Azure usage and control access to resources based on organizational structure and requirements.

Subscriptions provide several important capabilities for Azure resource management and organization. They enable customers to separate billing and cost tracking for different projects, departments, or business units, apply different access controls and policies to different groups of resources, and provide a foundation for governance and compliance management. Subscriptions also serve as the boundary for Azure service limits and quotas, helping customers manage resource usage and costs.

Subscription Types and Features

Primary Azure Subscription Types:

  • Free Account: Azure Free Account provides access to popular Azure services for 12 months, along with a credit to explore Azure services. This subscription type is ideal for learning Azure and experimenting with services without incurring costs.
  • Pay-As-You-Go: Pay-As-You-Go subscriptions provide access to all Azure services with no upfront costs or long-term commitments. Customers pay only for the resources they use, making this subscription type ideal for variable workloads and experimentation.
  • Enterprise Agreement: Enterprise Agreement subscriptions are designed for large organizations and provide volume discounts, centralized billing, and enhanced support options. These subscriptions are ideal for organizations with significant Azure usage and require centralized management.
  • Cloud Solution Provider: Cloud Solution Provider subscriptions are designed for partners who provide Azure services to their customers. These subscriptions provide additional management and billing capabilities for service providers.
  • Student and Academic: Student and Academic subscriptions provide discounted or free access to Azure services for educational purposes. These subscriptions are designed to support learning and research in educational institutions.

Subscription Management Best Practices

⚠️ Key Guidelines for Subscription Management:

  • Organizational alignment: Align subscriptions with your organizational structure, creating separate subscriptions for different departments, projects, or environments. This alignment helps with cost tracking, access control, and governance.
  • Cost management: Use subscriptions to separate costs for different projects or business units, enabling better cost tracking and budget management. This separation helps with financial planning and cost optimization.
  • Access control: Apply different access controls and policies to different subscriptions based on organizational requirements and security policies. This approach ensures that users have appropriate access to resources based on their roles and responsibilities.
  • Governance and compliance: Use subscriptions as boundaries for governance policies and compliance requirements, ensuring that different parts of your organization can meet their specific compliance needs. This approach helps with regulatory compliance and risk management.
  • Resource limits: Consider Azure service limits and quotas when planning subscriptions, ensuring that subscriptions are sized appropriately for expected resource usage. This planning helps avoid service limits and ensures optimal resource utilization.

Azure Management Groups

Understanding Management Groups

Azure Management Groups are containers that help customers organize and manage multiple Azure subscriptions by providing a hierarchical structure for governance, access control, and policy management. Management Groups enable customers to apply policies, access controls, and governance rules to multiple subscriptions at once, simplifying management of large Azure environments and ensuring consistent governance across the organization. This hierarchical organization is essential for enterprises with multiple subscriptions and complex governance requirements.

Management Groups provide a way to organize subscriptions in a tree structure, with up to six levels of hierarchy, enabling customers to create organizational structures that match their business requirements. Policies and access controls applied at the management group level are inherited by all subscriptions and resource groups within that management group, providing a powerful way to ensure consistent governance and security across the entire Azure environment.

Benefits of Management Groups

Key Advantages of Azure Management Groups:

  • Hierarchical organization: Management Groups provide a hierarchical structure for organizing subscriptions that can match your organizational structure, enabling logical grouping of subscriptions by department, project, or business unit. This organization simplifies management and provides clear governance boundaries.
  • Centralized governance: Policies and access controls can be applied at the management group level and inherited by all subscriptions and resource groups within that group, ensuring consistent governance across the organization. This centralized approach simplifies policy management and ensures compliance.
  • Simplified access control: Access control can be applied at the management group level, providing users with access to all subscriptions within the group based on their roles and responsibilities. This approach simplifies access management and ensures consistent security policies.
  • Cost management: Management Groups provide a foundation for cost management and budgeting by enabling cost tracking and allocation across multiple subscriptions. This capability helps with financial planning and cost optimization across the organization.
  • Automation and deployment: Management Groups enable automation and deployment across multiple subscriptions, providing a foundation for consistent deployment and management of resources across the organization. This capability simplifies operations and ensures consistency.

Hierarchy of Resource Groups, Subscriptions, and Management Groups

Understanding the Azure Hierarchy

The Azure hierarchy consists of Management Groups at the top level, followed by Subscriptions, and then Resource Groups, with individual Resources at the bottom level. This hierarchical structure provides a logical organization for Azure resources that enables governance, access control, and management at different levels. Understanding this hierarchy is essential for designing effective Azure governance and management strategies that align with organizational requirements and business objectives.

The hierarchy enables inheritance of policies, access controls, and governance rules from higher levels to lower levels, providing a powerful way to ensure consistent governance across the entire Azure environment. This inheritance model simplifies management by allowing policies to be defined once at the appropriate level and automatically applied to all resources within that scope, reducing administrative overhead and ensuring consistency.

Hierarchy Levels and Responsibilities

Azure Hierarchy Structure and Responsibilities:

  • Management Groups (Top Level): Management Groups provide the highest level of organization and governance, enabling policies and access controls to be applied across multiple subscriptions. They serve as the foundation for enterprise-wide governance and provide a way to organize subscriptions according to organizational structure.
  • Subscriptions (Middle Level): Subscriptions provide the boundary for billing, access control, and resource management, serving as the fundamental unit for organizing Azure resources. They enable separation of costs, access controls, and governance policies for different projects, departments, or business units.
  • Resource Groups (Lower Level): Resource Groups provide logical organization of related resources within a subscription, enabling resources to be managed as a single unit. They serve as the foundation for deployment, management, and governance of individual solutions and applications.
  • Resources (Bottom Level): Individual Azure resources are the actual services and components that provide functionality, such as virtual machines, storage accounts, and databases. Resources are the fundamental building blocks of Azure solutions and are managed within resource groups.

Designing an Effective Azure Hierarchy

⚠️ Best Practices for Azure Hierarchy Design:

  • Align with organizational structure: Design the Azure hierarchy to align with your organizational structure, creating management groups and subscriptions that match your business units, departments, or projects. This alignment ensures that governance and access control match your organizational needs.
  • Consider governance requirements: Design the hierarchy to support your governance requirements, ensuring that policies and access controls can be applied at the appropriate levels. This approach ensures that governance is effective and manageable.
  • Plan for growth and change: Design the hierarchy to accommodate future growth and organizational changes, ensuring that the structure remains effective as your organization evolves. This planning helps avoid the need for major restructuring in the future.
  • Simplify management: Design the hierarchy to simplify management and reduce administrative overhead, avoiding overly complex structures that are difficult to manage. This approach ensures that the hierarchy remains practical and effective.
  • Enable automation: Design the hierarchy to support automation and deployment, ensuring that policies and configurations can be applied consistently across the organization. This capability helps with operational efficiency and consistency.

Real-World Implementation Scenarios

Scenario 1: Global Enterprise with Multiple Regions

Situation: A multinational corporation needs to deploy applications globally while meeting data residency requirements and ensuring high availability.

Solution: Deploy applications across multiple Azure regions with availability zones, use management groups to organize subscriptions by geography, and implement region pairs for disaster recovery to ensure global coverage and compliance.

Scenario 2: Startup with Cost Optimization

Situation: A startup needs to deploy applications with minimal cost while maintaining the ability to scale and organize resources effectively.

Solution: Use a single subscription with resource groups organized by environment (dev, test, prod), deploy in a single region with availability zones for high availability, and implement cost management policies to control spending.

Scenario 3: Government Agency with Compliance Requirements

Situation: A government agency needs to deploy applications while meeting strict compliance and data residency requirements.

Solution: Use Azure Government sovereign regions, implement management groups for different departments, and deploy across availability zones within the sovereign region to ensure compliance and high availability.

Scenario 4: Enterprise with Complex Governance

Situation: A large enterprise needs to manage multiple departments with different compliance and access requirements.

Solution: Create management groups for each department, separate subscriptions for different compliance requirements, and use resource groups to organize applications and services within each department.

Best Practices for Azure Architecture

Design and Planning

  • Plan for high availability: Design applications to use availability zones and region pairs to ensure high availability and disaster recovery capabilities
  • Consider compliance requirements: Select appropriate regions and sovereign clouds to meet data residency and compliance requirements
  • Design for cost optimization: Use resource groups and subscriptions to organize resources for effective cost management and optimization
  • Implement governance early: Establish management groups and governance policies early in your Azure adoption to ensure consistent management and compliance
  • Plan for growth: Design your Azure hierarchy to accommodate future growth and organizational changes

Implementation and Management

  • Use consistent naming: Implement consistent naming conventions across all Azure resources and organizational units
  • Implement monitoring: Set up comprehensive monitoring and alerting across all levels of your Azure hierarchy
  • Regular review and optimization: Regularly review and optimize your Azure architecture to ensure it continues to meet your needs
  • Document your architecture: Maintain comprehensive documentation of your Azure architecture and governance policies
  • Train your team: Ensure that your team understands the Azure hierarchy and governance policies

Exam Preparation Tips

Key Concepts to Remember

  • Azure regions and availability zones: Understand how regions and availability zones provide high availability and disaster recovery
  • Resource organization: Know how resource groups, subscriptions, and management groups organize and manage Azure resources
  • Hierarchy and inheritance: Understand how policies and access controls are inherited through the Azure hierarchy
  • Sovereign regions: Know the purpose and characteristics of Azure sovereign regions for compliance requirements
  • Region pairs: Understand how region pairs provide disaster recovery and coordinated updates

Practice Questions

Sample Exam Questions:

  1. What is the primary purpose of Azure Availability Zones?
  2. How do Azure region pairs help with disaster recovery?
  3. What is the difference between Azure regions and sovereign regions?
  4. How do management groups help with governance across multiple subscriptions?
  5. What is the correct hierarchy order for Azure organizational units?

AZ-900 Success Tip: Understanding Azure's core architectural components is fundamental to the AZ-900 exam and your Azure career. Focus on learning how regions, availability zones, and the organizational hierarchy work together to provide a comprehensive cloud platform. Practice identifying which components would be most appropriate for different scenarios, and understand how these components enable high availability, compliance, and effective resource management. This knowledge will help you design effective Azure solutions and serve you well throughout your Azure learning journey.

Practice Lab: Exploring Azure's Core Architecture

Lab Objective

This hands-on lab is designed for AZ-900 exam candidates to explore Azure's core architectural components. You'll examine regions, availability zones, resource groups, subscriptions, and management groups to understand how Azure organizes its global infrastructure and how resources are managed within the Azure hierarchy.

Lab Setup and Prerequisites

For this lab, you'll need a free Azure account (which provides $200 in credits for new users) and a web browser. No prior Azure experience is required, as we'll focus on exploring Azure's architecture rather than complex configurations. The lab is designed to be completed in approximately 2-3 hours and provides hands-on experience with the core architectural components covered in the AZ-900 exam.

Lab Activities

Activity 1: Explore Azure Regions and Availability Zones

  • Examine available regions: Use the Azure portal to explore available regions and understand how regions are organized geographically. Look at service availability in different regions and understand the concept of region pairs.
  • Check availability zones: Explore which regions have availability zones and understand how availability zones provide high availability and fault tolerance. Look at the availability zone options when creating resources.
  • Compare region features: Compare different regions to understand how they differ in terms of service availability, pricing, and compliance features. This helps understand region selection criteria.

Activity 2: Create and Organize Resource Groups

  • Create resource groups: Create multiple resource groups with different naming conventions to understand how resource groups organize and manage Azure resources. Practice organizing resources logically.
  • Deploy resources to resource groups: Create simple resources like storage accounts and deploy them to different resource groups to understand how resources are organized and managed within resource groups.
  • Explore resource group management: Use the Azure portal to explore resource group management features including access control, policies, and cost tracking. Understand how resource groups simplify resource management.

Activity 3: Understand Subscriptions and Billing

  • Examine subscription details: Explore your Azure subscription to understand subscription features, billing information, and service limits. Look at how subscriptions provide boundaries for resource management and cost tracking.
  • Review cost management: Use Azure Cost Management to understand how costs are tracked and organized within subscriptions. Explore cost allocation and budgeting features.
  • Check service limits: Examine Azure service limits and quotas to understand how subscriptions provide boundaries for resource usage. This helps understand subscription planning considerations.

Activity 4: Explore Management Groups and Hierarchy

  • Examine management groups: Explore Azure Management Groups to understand how they provide hierarchical organization of subscriptions and enable centralized governance.
  • Understand hierarchy inheritance: Look at how policies and access controls can be applied at different levels of the Azure hierarchy and understand how inheritance works.
  • Plan organizational structure: Based on your exploration, plan how you would organize an Azure environment for a hypothetical organization with multiple departments and compliance requirements.

Lab Outcomes and Learning Objectives

Upon completing this lab, you should be able to explain how Azure's core architectural components work together to provide a comprehensive cloud platform. You'll understand how regions and availability zones provide high availability, how the organizational hierarchy enables effective resource management, and how to design Azure environments that meet specific requirements. This hands-on experience will help you understand the practical applications of Azure's core architecture covered in the AZ-900 exam.

Cleanup and Cost Management

After completing the lab activities, be sure to delete all created resources to avoid unexpected charges. The lab is designed to use minimal resources, but proper cleanup is essential when working with cloud services. Use Azure Cost Management tools to monitor spending and ensure you stay within your free tier limits.

Previous: Objective 1.3 Describe Cloud Service Types

Next: Objective 2.2 Describe Azure Compute Networking Services