Scaled Score
Exam score adjusted for question difficulty, not a raw percentage.
Getting Started: Your AZ-305 Journey
Free knowledge base
Microsoft Certified: Azure Solutions Architect Expert — key terms, tricks & tips
Everything from the course in one searchable place: 238 entries. Use it to review before a practice test or look up a word you forgot.
238 results
Functional Group
Major sections of the exam objectives, each with a weighting.
Getting Started: Your AZ-305 Journey
Weighting
Percentage indicating the relative importance of an exam domain.
Getting Started: Your AZ-305 Journey
Case Study
Exam question type presenting a scenario with multiple related questions.
Getting Started: Your AZ-305 Journey
Azure Monitor
Unified monitoring solution for collecting, analyzing, and acting on telemetry.
Getting Started: Your AZ-305 Journey
Azure Policy
Service to enforce organizational standards and assess compliance at scale.
Getting Started: Your AZ-305 Journey
Business Continuity
Ability to continue essential business functions during and after a disaster.
Getting Started: Your AZ-305 Journey
Microsoft Entra ID
Cloud-based identity and access management service (formerly Azure AD).
Getting Started: Your AZ-305 Journey
Understanding the AZ-305 Exam Structure and Objectives
To remember the main domains: I-D-B-I. Identity, Data, Business Continuity, Infrastructure. Think 'I Do B-I' (Business Intelligence) to recall the core areas an architect designs.
Getting Started: Your AZ-305 Journey
Understanding the AZ-305 Exam Structure and Objectives
The AZ-305 exam focuses heavily on 'designing' solutions. Look for keywords like 'recommend,' 'propose,' 'evaluate,' and 'implement a design.' Memorize the current functional groups and their approximate weightings from the official Microsoft exam page.
Getting Started: Your AZ-305 Journey
Understanding the AZ-305 Exam Structure and Objectives
Underestimating the importance of case studies, which require careful reading and critical thinking.
Getting Started: Your AZ-305 Journey
Understanding the AZ-305 Exam Structure and Objectives
Focusing too much on memorizing specific commands instead of understanding architectural design principles.
Getting Started: Your AZ-305 Journey
Understanding the AZ-305 Exam Structure and Objectives
Not checking the official Microsoft exam page for the latest objective updates and weighting changes.
Getting Started: Your AZ-305 Journey
Azure Free Account
Microsoft's offering with credits and free services for new users.
Getting Started: Your AZ-305 Journey
Resource Group
A logical container for Azure resources that share a common lifecycle.
Getting Started: Your AZ-305 Journey
Deallocate
To stop a virtual machine, releasing its compute resources to save costs.
Getting Started: Your AZ-305 Journey
Azure Cost Management
Service for monitoring, allocating, and optimizing Azure spending.
Getting Started: Your AZ-305 Journey
Azure Advisor
Provides personalized recommendations for cost, security, reliability, etc.
Getting Started: Your AZ-305 Journey
Tagging
Applying metadata labels to Azure resources for organization and billing.
Getting Started: Your AZ-305 Journey
Setting Up Your Azure Lab Environment
To remember lab best practices: 'C-R-E-A-T-E': Costs monitored, Resource groups, Experiment freely, Always delete, Tag everything, Educate yourself.
Getting Started: Your AZ-305 Journey
Setting Up Your Azure Lab Environment
The AZ-305 exam expects you to know how to design cost-optimized solutions. This includes understanding the cost implications of various services and how to manage them, even in a lab setting. Keywords like 'cost optimization,' 'budget,' and 'resource governance' are common.
Getting Started: Your AZ-305 Journey
Setting Up Your Azure Lab Environment
Forgetting to delete or deallocate resources, leading to unexpected charges on a free or pay-as-you-go account.
Getting Started: Your AZ-305 Journey
Setting Up Your Azure Lab Environment
Not using resource groups, making it difficult to manage and clean up lab resources efficiently.
Getting Started: Your AZ-305 Journey
Setting Up Your Azure Lab Environment
Only reading about services without hands-on practice, which hinders true understanding and exam readiness.
Getting Started: Your AZ-305 Journey
Management Group
Container for subscriptions, applies governance at scale.
Identity, Governance, and Monitoring Fundamentals
Azure Blueprint
Defines a repeatable set of Azure resources, policies, and roles.
Identity, Governance, and Monitoring Fundamentals
Resource Tag
Key-value pair for categorizing resources for management.
Identity, Governance, and Monitoring Fundamentals
Policy Initiative
A collection of Azure Policy definitions grouped together.
Identity, Governance, and Monitoring Fundamentals
Resource Hierarchy
The structured organization of Azure resources from top to bottom.
Identity, Governance, and Monitoring Fundamentals
Cloud Governance
Strategies for managing, monitoring, and auditing cloud resources.
Identity, Governance, and Monitoring Fundamentals
Designing Robust Azure Governance Solutions
Govern with MG-SPART: Management Groups, Subscriptions, Policies, Blueprints, ARM templates, Resource Tags.
Identity, Governance, and Monitoring Fundamentals
Designing Robust Azure Governance Solutions
The exam often tests the scope of Azure Policy assignments. Remember that policies assigned at a higher level (e.g., management group) are inherited by all child scopes (subscriptions, resource groups, resources) unless explicitly overridden by a more specific policy at a lower level.
Identity, Governance, and Monitoring Fundamentals
Designing Robust Azure Governance Solutions
Not designing a proper management group hierarchy before deploying resources, leading to inconsistent policy application.
Identity, Governance, and Monitoring Fundamentals
Designing Robust Azure Governance Solutions
Overlooking the importance of resource tagging, which complicates cost management and resource identification later.
Identity, Governance, and Monitoring Fundamentals
Designing Robust Azure Governance Solutions
Applying policies only at the subscription level when a broader, management group scope is more appropriate for organizational-wide compliance.
Identity, Governance, and Monitoring Fundamentals
Azure Active Directory
Microsoft's cloud-based identity and access management service.
Identity, Governance, and Monitoring Fundamentals
Multi-Factor Authentication
Requires two or more verification factors for user access.
Identity, Governance, and Monitoring Fundamentals
Conditional Access
Azure AD feature to enforce policies based on conditions.
Identity, Governance, and Monitoring Fundamentals
Passwordless Authentication
Sign-in methods removing the need for traditional passwords.
Identity, Governance, and Monitoring Fundamentals
Managed Identities
Azure AD identities for Azure services, auto-managed by Azure.
Identity, Governance, and Monitoring Fundamentals
Service Principal
An identity representing an application in Azure AD.
Identity, Governance, and Monitoring Fundamentals
Implementing Secure Authentication Strategies in Azure
MFA: 'My Favorite Authentication' uses 'More Factors' for 'Maximum Fortification'.
Identity, Governance, and Monitoring Fundamentals
Implementing Secure Authentication Strategies in Azure
The exam frequently tests on the appropriate use of Managed Identities vs. Service Principals for Azure resources, and the role of Conditional Access in enforcing MFA. Look for scenarios where services need to authenticate without explicit credentials.
Identity, Governance, and Monitoring Fundamentals
Implementing Secure Authentication Strategies in Azure
Not enabling MFA for administrative accounts, leaving a major security hole.
Identity, Governance, and Monitoring Fundamentals
Implementing Secure Authentication Strategies in Azure
Hardcoding credentials or secrets within application code instead of using Managed Identities or Azure Key Vault.
Identity, Governance, and Monitoring Fundamentals
Implementing Secure Authentication Strategies in Azure
Over-provisioning permissions for Service Principals, violating the principle of least privilege.
Identity, Governance, and Monitoring Fundamentals
Authorization
Determining what an authenticated user can do.
Identity, Governance, and Monitoring Fundamentals
Azure RBAC
Role-Based Access Control for Azure resources.
Identity, Governance, and Monitoring Fundamentals
Role Definition
A collection of permissions in Azure RBAC.
Identity, Governance, and Monitoring Fundamentals
Scope
The level at which an RBAC assignment applies.
Identity, Governance, and Monitoring Fundamentals
Least Privilege
Granting only necessary permissions.
Identity, Governance, and Monitoring Fundamentals
Azure AD PIM
Just-in-time access for privileged roles.
Identity, Governance, and Monitoring Fundamentals
Custom Role
User-defined RBAC role with specific permissions.
Identity, Governance, and Monitoring Fundamentals
Crafting Effective Authorization Models for Azure Resources
Remember 'RAC' for 'Resource Access Control' – it helps you recall that Azure RBAC is for Azure resources, not Azure AD itself.
Identity, Governance, and Monitoring Fundamentals
Crafting Effective Authorization Models for Azure Resources
For the AZ-305 exam, differentiate clearly between Azure AD roles (for managing Azure AD) and Azure RBAC roles (for managing Azure resources). Keywords like 'manage users in Azure AD' point to Azure AD roles, while 'manage virtual machines' points to Azure RBAC.
Identity, Governance, and Monitoring Fundamentals
Crafting Effective Authorization Models for Azure Resources
Confusing Azure AD roles with Azure RBAC roles, leading to incorrect permission assignments.
Identity, Governance, and Monitoring Fundamentals
Crafting Effective Authorization Models for Azure Resources
Granting 'Owner' or 'Contributor' roles at the subscription level unnecessarily, violating the principle of least privilege.
Identity, Governance, and Monitoring Fundamentals
Crafting Effective Authorization Models for Azure Resources
Not using Azure AD PIM for highly privileged roles, leaving standing access vulnerable to compromise.
Identity, Governance, and Monitoring Fundamentals
Log Analytics
Azure service for storing, querying, and analyzing log data.
Identity, Governance, and Monitoring Fundamentals
Kusto Query Language (KQL)
Powerful query language for analyzing data in Azure Monitor Logs.
Identity, Governance, and Monitoring Fundamentals
Diagnostic Settings
Configures what logs and metrics to send from Azure resources.
Identity, Governance, and Monitoring Fundamentals
Action Group
Collection of notification preferences and actions for alerts.
Identity, Governance, and Monitoring Fundamentals
Azure Monitor Agent (AMA)
Agent for collecting guest OS data from virtual machines.
Identity, Governance, and Monitoring Fundamentals
Workbooks
Interactive reports and dashboards in Azure Monitor.
Identity, Governance, and Monitoring Fundamentals
Building Comprehensive Azure Monitoring Solutions
MALTA: Metrics, Agents, Logs, Tools, Alerts. Remember these five core components of Azure monitoring.
Identity, Governance, and Monitoring Fundamentals
Building Comprehensive Azure Monitoring Solutions
The exam frequently tests your understanding of where different types of monitoring data are stored (Metrics vs. Logs) and the primary tools for analysis (KQL, Workbooks). Pay attention to scenarios asking about troubleshooting application performance (Application Insights) versus infrastructure health (VM Insights, Log Analytics).
Identity, Governance, and Monitoring Fundamentals
Building Comprehensive Azure Monitoring Solutions
Confusing Metrics and Logs: Metrics are numerical time-series data; Logs are structured/unstructured text data.
Identity, Governance, and Monitoring Fundamentals
Building Comprehensive Azure Monitoring Solutions
Ignoring cost implications: Ingesting too much data into Log Analytics can become expensive. Design data collection carefully.
Identity, Governance, and Monitoring Fundamentals
Building Comprehensive Azure Monitoring Solutions
Over-alerting or under-alerting: Balance alert sensitivity to avoid fatigue or missed critical events.
Identity, Governance, and Monitoring Fundamentals
Log Analytics Workspace
Azure service for collecting, indexing, and analyzing log data.
Identity, Governance, and Monitoring Fundamentals
Dynamic Thresholds
Alert thresholds that automatically adjust based on historical data patterns.
Identity, Governance, and Monitoring Fundamentals
Resource Logs
Detailed logs providing insight into operations performed within an Azure resource.
Identity, Governance, and Monitoring Fundamentals
Activity Log
Log of subscription-level events, including resource creation and deletion.
Identity, Governance, and Monitoring Fundamentals
Advanced Monitoring and Alerting for Azure Workloads
KQL: 'Keep Querying Logs!' – it's the key to unlocking insights from your Azure data.
Identity, Governance, and Monitoring Fundamentals
Advanced Monitoring and Alerting for Azure Workloads
Memorize the core components of Azure Monitor (Log Analytics, Application Insights, Metrics, Alerts) and their primary use cases. Understand when to use platform metrics vs. resource logs vs. activity logs for specific monitoring scenarios.
Identity, Governance, and Monitoring Fundamentals
Advanced Monitoring and Alerting for Azure Workloads
Over-alerting: Creating too many basic alerts that lead to 'alert fatigue' and missed critical issues.
Identity, Governance, and Monitoring Fundamentals
Advanced Monitoring and Alerting for Azure Workloads
Ignoring cost: Not considering the cost implications of ingesting and retaining all possible log data.
Identity, Governance, and Monitoring Fundamentals
Advanced Monitoring and Alerting for Azure Workloads
Underutilizing KQL: Relying only on pre-built dashboards instead of writing custom queries for deep diagnostics.
Identity, Governance, and Monitoring Fundamentals
Vertical Scaling
Increasing resources (CPU, RAM) of a single server.
Mastering Azure Data Storage Solutions
Horizontal Scaling
Distributing load across multiple servers/instances.
Mastering Azure Data Storage Solutions
Sharding
Partitioning data across multiple database instances.
Mastering Azure Data Storage Solutions
Read Replica
A copy of the primary database for read-only queries.
Mastering Azure Data Storage Solutions
High Availability (HA)
Ensuring continuous operation within a single region.
Mastering Azure Data Storage Solutions
Disaster Recovery (DR)
Recovering from catastrophic regional outages.
Mastering Azure Data Storage Solutions
RPO (Recovery Point Objective)
Maximum acceptable data loss in a disaster.
Mastering Azure Data Storage Solutions
RTO (Recovery Time Objective)
Maximum acceptable downtime after a disaster.
Mastering Azure Data Storage Solutions
Designing Relational Data Storage for Scalability
To remember scaling types: 'V'ertical is 'V'ery tall (one server grows up), 'H'orizontal is 'H'uge (many servers spread out).
Mastering Azure Data Storage Solutions
Designing Relational Data Storage for Scalability
The exam frequently tests your understanding of when to use Azure SQL Database Hyperscale vs. Elastic Pools, and the differences between geo-replication and active geo-replication for DR. Memorize the core capabilities of each service and their scaling limits.
Mastering Azure Data Storage Solutions
Designing Relational Data Storage for Scalability
Over-provisioning resources initially, leading to unnecessary costs, without considering gradual scaling.
Mastering Azure Data Storage Solutions
Designing Relational Data Storage for Scalability
Ignoring the impact of application architecture on database scalability (e.g., chatty queries, inefficient indexing).
Mastering Azure Data Storage Solutions
Designing Relational Data Storage for Scalability
Confusing high availability (HA) with disaster recovery (DR) and not implementing both where needed.
Mastering Azure Data Storage Solutions
NoSQL
Non-relational databases, flexible schemas, horizontal scalability.
Mastering Azure Data Storage Solutions
Document Database
Stores data in flexible, semi-structured documents (e.g., JSON).
Mastering Azure Data Storage Solutions
Key-Value Store
Simplest NoSQL, stores data as unique key-value pairs.
Mastering Azure Data Storage Solutions
Column-Family Database
Organizes data into rows and dynamic columns for scale.
Mastering Azure Data Storage Solutions
Graph Database
Models data as nodes and edges to represent relationships.
Mastering Azure Data Storage Solutions
Azure Cosmos DB
Microsoft's globally distributed, multi-model NoSQL database service.
Mastering Azure Data Storage Solutions
Azure Table Storage
Low-cost key-value store for massive structured non-relational data.
Mastering Azure Data Storage Solutions
Azure Blob Storage
Object storage for unstructured data like images, videos, backups.
Mastering Azure Data Storage Solutions
Architecting Non-Relational Data Storage Solutions
To remember the main NoSQL types, think 'DOCK': Document, Object (Blob), Column-family, Key-value, Graph. (Object here representing Blob Storage for unstructured data, often grouped with NoSQL discussions).
Mastering Azure Data Storage Solutions
Architecting Non-Relational Data Storage Solutions
The AZ-305 exam frequently tests your ability to choose the correct Azure data service based on specific requirements. Pay close attention to keywords like 'flexible schema', 'high throughput', 'global distribution', 'complex relationships', 'time-series', 'unstructured objects', and 'cost-effective key-value' to guide your service selection.
Mastering Azure Data Storage Solutions
Architecting Non-Relational Data Storage Solutions
Using a relational database for highly unstructured or rapidly evolving data, leading to schema migration headaches and performance bottlenecks.
Mastering Azure Data Storage Solutions
Architecting Non-Relational Data Storage Solutions
Overlooking Azure Table Storage for simple, high-volume key-value data, leading to higher costs with Cosmos DB when not all its advanced features are needed.
Mastering Azure Data Storage Solutions
Architecting Non-Relational Data Storage Solutions
Choosing a single NoSQL solution (e.g., always Cosmos DB) without considering the specific access patterns and cost implications of other Azure services like Blob or Table Storage.
Mastering Azure Data Storage Solutions
Azure Data Factory (ADF)
Cloud ETL service for data movement and transformation.
Mastering Azure Data Storage Solutions
Self-Hosted Integration Runtime (SHIR)
ADF component for connecting to on-premises data sources.
Mastering Azure Data Storage Solutions
Azure Stream Analytics
Real-time, serverless analytics for streaming data.
Mastering Azure Data Storage Solutions
Azure Event Hubs
Highly scalable data streaming platform for event ingestion.
Mastering Azure Data Storage Solutions
Data Flow (ADF)
Visual, code-free data transformation in Azure Data Factory.
Mastering Azure Data Storage Solutions
ETL
Extract, Transform, Load; a data integration process.
Mastering Azure Data Storage Solutions
Orchestration
Managing and sequencing data integration tasks and workflows.
Mastering Azure Data Storage Solutions
Azure Synapse Analytics pipelines
Data integration capabilities within Azure Synapse Analytics.
Mastering Azure Data Storage Solutions
Implementing Advanced Data Integration Strategies
To remember the core ADF components for on-premises integration: 'SHIR' is the 'SHIp' that brings your data from 'IR' (on-premises) to Azure.
Mastering Azure Data Storage Solutions
Implementing Advanced Data Integration Strategies
The AZ-305 exam frequently tests your ability to choose the correct Azure service for specific data integration scenarios. Pay close attention to keywords like 'batch,' 'real-time,' 'on-premises,' 'transformation,' and 'orchestration' to guide your service selection.
Mastering Azure Data Storage Solutions
Implementing Advanced Data Integration Strategies
Using Azure Data Factory for real-time, low-latency processing when Azure Stream Analytics is more appropriate.
Mastering Azure Data Storage Solutions
Implementing Advanced Data Integration Strategies
Forgetting to account for network connectivity (e.g., SHIR, VPN, ExpressRoute) when integrating on-premises data.
Mastering Azure Data Storage Solutions
Implementing Advanced Data Integration Strategies
Underestimating the complexity of data transformation and not leveraging Data Flow capabilities in ADF.
Mastering Azure Data Storage Solutions
Storage Tiers
Different cost/performance levels for storage, e.g., Hot, Cool, Archive for blobs.
Mastering Azure Data Storage Solutions
Lifecycle Management
Automated rules to transition or delete data based on age or access patterns.
Mastering Azure Data Storage Solutions
Caching
Storing frequently accessed data closer to the application for faster retrieval.
Mastering Azure Data Storage Solutions
IOPS
Input/Output Operations Per Second; a measure of disk performance.
Mastering Azure Data Storage Solutions
Throughput
The rate at which data is transferred, typically measured in MB/s.
Mastering Azure Data Storage Solutions
RU/s
Request Units per second; the throughput measure for Azure Cosmos DB.
Mastering Azure Data Storage Solutions
Host Caching
Caching mechanism on Azure VMs for Managed Disks to improve I/O performance.
Mastering Azure Data Storage Solutions
Azure CDN
Content Delivery Network; caches web content at edge locations globally.
Mastering Azure Data Storage Solutions
Optimizing Data Storage for Performance and Cost
HOT data is 'H'ighly accessed, COOL data is 'C'old but accessible, ARCHIVE data is 'A'lmost never touched. H-C-A, like a temperature gauge for your data!
Mastering Azure Data Storage Solutions
Optimizing Data Storage for Performance and Cost
On the AZ-305 exam, pay close attention to scenarios involving data access patterns (frequent, infrequent, archival) and their direct correlation to storage tier selection (Hot, Cool, Archive). Also, know that lifecycle management policies are the primary tool for automating these transitions for cost savings.
Mastering Azure Data Storage Solutions
Optimizing Data Storage for Performance and Cost
Not implementing lifecycle management policies, leading to unnecessary costs for old data.
Mastering Azure Data Storage Solutions
Optimizing Data Storage for Performance and Cost
Using a high-performance storage tier (e.g., Premium SSD) for data that has low I/O requirements.
Mastering Azure Data Storage Solutions
Optimizing Data Storage for Performance and Cost
Overlooking caching opportunities, resulting in slower application performance and higher database load.
Mastering Azure Data Storage Solutions
Optimizing Data Storage for Performance and Cost
Ignoring monitoring metrics, which could reveal performance bottlenecks or cost inefficiencies.
Mastering Azure Data Storage Solutions
Storage Service Encryption (SSE)
Automatic encryption of data at rest in Azure Storage.
Mastering Azure Data Storage Solutions
Customer-Managed Keys (CMK)
Encryption keys stored in Azure Key Vault, managed by the customer.
Mastering Azure Data Storage Solutions
Shared Access Signature (SAS)
Time-limited, delegated access token for Azure Storage resources.
Mastering Azure Data Storage Solutions
Soft Delete
Feature to recover accidentally deleted blobs within a retention period.
Mastering Azure Data Storage Solutions
Immutable Storage
Write-once, read-many (WORM) storage for compliance needs.
Mastering Azure Data Storage Solutions
Private Endpoint
Private IP address for Azure service in your VNet, eliminating public exposure.
Mastering Azure Data Storage Solutions
Geo-Redundant Storage (GRS)
Data replicated to a secondary Azure region for disaster recovery.
Mastering Azure Data Storage Solutions
Securing and Managing Data Across Azure Storage
To remember storage redundancy: 'Lizard' (LRS) stays local, 'Zebra' (ZRS) crosses zones, 'Giraffe' (GRS) reaches other regions, 'Gazelle' (GZRS) spans zones and regions!
Mastering Azure Data Storage Solutions
Securing and Managing Data Across Azure Storage
The exam frequently tests the differences between SAS, Azure AD RBAC, and Access Keys for storage access. Also, know the various redundancy options (LRS, ZRS, GRS, GZRS) and when to use each, especially for disaster recovery scenarios.
Mastering Azure Data Storage Solutions
Securing and Managing Data Across Azure Storage
Using storage account access keys directly in applications instead of SAS or Azure AD for production environments.
Mastering Azure Data Storage Solutions
Securing and Managing Data Across Azure Storage
Not enabling soft delete or versioning for critical data, leading to irreversible data loss from accidental deletions or overwrites.
Mastering Azure Data Storage Solutions
Securing and Managing Data Across Azure Storage
Overlooking network security (firewalls, Private Endpoints) and leaving storage accounts publicly accessible when not required.
Mastering Azure Data Storage Solutions
RPO
Recovery Point Objective: Max acceptable data loss.
Ensuring Business Continuity on Azure
RTO
Recovery Time Objective: Max acceptable downtime.
Ensuring Business Continuity on Azure
Azure Backup
Azure service for data backup and recovery.
Ensuring Business Continuity on Azure
Recovery Services Vault
Azure resource to store backup data and manage backups.
Ensuring Business Continuity on Azure
Azure Site Recovery
Azure service for disaster recovery and workload replication.
Ensuring Business Continuity on Azure
Application-consistent backup
Backup ensuring data integrity across applications.
Ensuring Business Continuity on Azure
MARS Agent
Microsoft Azure Recovery Services agent for on-premises backups.
Ensuring Business Continuity on Azure
Designing Comprehensive Backup and Recovery Strategies
RPO is 'Point' in time (how much data you lose), RTO is 'Time' to get back online (how long you're down).
Ensuring Business Continuity on Azure
Designing Comprehensive Backup and Recovery Strategies
The exam frequently differentiates between Azure Backup and Azure Site Recovery. Remember, Backup is for data protection and recovery (files, VMs, databases), while Site Recovery is for disaster recovery of entire workloads (VMs, physical servers) to a secondary location for business continuity.
Ensuring Business Continuity on Azure
Designing Comprehensive Backup and Recovery Strategies
Confusing Azure Backup with Azure Site Recovery: They serve different, though complementary, purposes.
Ensuring Business Continuity on Azure
Designing Comprehensive Backup and Recovery Strategies
Not aligning RPO/RTO with business requirements: Over-provisioning leads to unnecessary costs, under-provisioning leads to unacceptable downtime/data loss.
Ensuring Business Continuity on Azure
Designing Comprehensive Backup and Recovery Strategies
Forgetting to test recovery plans: A backup strategy is useless if you can't actually recover data when needed.
Ensuring Business Continuity on Azure
Availability Set
Logical grouping of VMs to ensure hardware isolation within a datacenter.
Ensuring Business Continuity on Azure
Availability Zone
Physically separate datacenter within an Azure region with independent power/network.
Ensuring Business Continuity on Azure
Fault Domain
Group of VMs sharing a common power source and network switch.
Ensuring Business Continuity on Azure
Update Domain
Group of VMs that can be rebooted together during planned maintenance.
Ensuring Business Continuity on Azure
Azure Load Balancer
Layer 4 service distributing traffic to healthy backend instances.
Ensuring Business Continuity on Azure
Azure Application Gateway
Layer 7 load balancer with WAF, SSL termination, and URL routing.
Ensuring Business Continuity on Azure
Azure Front Door
Global, scalable entry point for web apps with advanced routing and WAF.
Ensuring Business Continuity on Azure
Implementing High Availability for Azure Applications
Remember 'AZ for Zones, AS for Sets'. AZ protects against entire datacenter failures, AS protects against individual hardware failures within a datacenter.
Ensuring Business Continuity on Azure
Implementing High Availability for Azure Applications
For the AZ-305 exam, distinguish clearly between Availability Sets (within a datacenter, fault/update domains) and Availability Zones (across datacenters, regional resilience). Know which Azure services are zone-redundant or can be deployed across zones. Understand the use cases for Azure Load Balancer, Application Gateway, and Front Door.
Ensuring Business Continuity on Azure
Implementing High Availability for Azure Applications
Confusing Availability Sets with Availability Zones: They serve different purposes and levels of protection. Sets are within a datacenter, Zones are across datacenters.
Ensuring Business Continuity on Azure
Implementing High Availability for Azure Applications
Not configuring health probes for load balancers: Without proper health probes, the load balancer won't know which backend instances are healthy and might send traffic to failed ones.
Ensuring Business Continuity on Azure
Implementing High Availability for Azure Applications
Assuming all Azure services are automatically highly available: While many PaaS services offer built-in HA, IaaS components and some PaaS services require explicit configuration for optimal availability.
Ensuring Business Continuity on Azure
Business Continuity (BC)
Ensuring ongoing operations during and after a disaster.
Ensuring Business Continuity on Azure
Recovery Time Objective (RTO)
Maximum acceptable downtime after a disaster.
Ensuring Business Continuity on Azure
Recovery Point Objective (RPO)
Maximum acceptable data loss after a disaster.
Ensuring Business Continuity on Azure
Azure Site Recovery (ASR)
Azure service for VM replication and failover.
Ensuring Business Continuity on Azure
Failover
Switching to a standby system during an outage.
Ensuring Business Continuity on Azure
Failback
Returning operations to the primary system.
Ensuring Business Continuity on Azure
Disaster Recovery Planning and Implementation
RTO is 'Time' to get back Online. RPO is 'Point' in time for data. Remember the 'T' for Time and 'P' for Point!
Ensuring Business Continuity on Azure
Disaster Recovery Planning and Implementation
The exam frequently tests your understanding of RTO and RPO. Know that RTO is about time to recover, and RPO is about data loss. Be prepared to choose the right Azure service based on specific RTO/RPO requirements for different workloads.
Ensuring Business Continuity on Azure
Disaster Recovery Planning and Implementation
Confusing RTO with RPO, or not understanding that lower values for both are generally more expensive and complex to achieve.
Ensuring Business Continuity on Azure
Disaster Recovery Planning and Implementation
Failing to regularly test the DR plan, leading to unexpected issues during an actual disaster event.
Ensuring Business Continuity on Azure
Disaster Recovery Planning and Implementation
Not involving business stakeholders in defining RTO/RPO, resulting in a DR plan that doesn't meet actual business needs.
Ensuring Business Continuity on Azure
Tabletop Exercise
Verbal walkthrough of a BC plan without actual execution.
Ensuring Business Continuity on Azure
Disaster Recovery Drill
Full-scale simulation of a disaster, executing recovery steps.
Ensuring Business Continuity on Azure
Post-Mortem Analysis
Review after an incident or test to identify lessons learned.
Ensuring Business Continuity on Azure
Testing and Validating Business Continuity Solutions
RTO: 'R'ecovery 'T'ime 'O'ut. RPO: 'R'ecovery 'P'oint, 'O'ld data.
Ensuring Business Continuity on Azure
Testing and Validating Business Continuity Solutions
The exam often tests your understanding of RTO and RPO definitions and how to measure them. Remember that RTO is about 'time to recover' and RPO is about 'data loss acceptable'. Questions might describe a scenario and ask what metric is being validated.
Ensuring Business Continuity on Azure
Testing and Validating Business Continuity Solutions
Not testing regularly, leading to outdated plans.
Ensuring Business Continuity on Azure
Testing and Validating Business Continuity Solutions
Only performing tabletop exercises and never full-scale drills.
Ensuring Business Continuity on Azure
Testing and Validating Business Continuity Solutions
Failing to document test results and implement corrective actions.
Ensuring Business Continuity on Azure
IaaS
Infrastructure as a Service; fundamental compute, storage, networking.
Designing Resilient Azure Infrastructure
PaaS
Platform as a Service; managed environment for app development.
Designing Resilient Azure Infrastructure
Serverless Compute
Executes code in response to events without managing infrastructure.
Designing Resilient Azure Infrastructure
Virtual Machine Scale Sets
Manages a group of identical, load-balanced VMs with auto-scaling.
Designing Resilient Azure Infrastructure
Azure Reservations
Commitment to compute capacity for discounts over pay-as-you-go.
Designing Resilient Azure Infrastructure
Right-sizing
Selecting the appropriate resource size to match workload needs.
Designing Resilient Azure Infrastructure
Azure Hybrid Benefit
Use on-premises Windows/SQL Server licenses on Azure for savings.
Designing Resilient Azure Infrastructure
Designing Scalable and Cost-Effective Compute
To remember cost-saving strategies: R.A.H.S. - Right-sizing, Azure Reservations, Hybrid Benefit, Serverless.
Designing Resilient Azure Infrastructure
Designing Scalable and Cost-Effective Compute
The AZ-305 exam frequently tests your ability to choose the MOST appropriate compute service. Look for keywords like 'web app,' 'containerized,' 'event-driven,' 'full OS control,' 'cost optimization for stable workload,' or 'unpredictable traffic' to guide your choice.
Designing Resilient Azure Infrastructure
Designing Scalable and Cost-Effective Compute
Over-provisioning resources, leading to unnecessary costs, instead of right-sizing or using auto-scaling.
Designing Resilient Azure Infrastructure
Designing Scalable and Cost-Effective Compute
Using Virtual Machines for simple web applications that could be more cost-effectively hosted on Azure App Service or serverless functions.
Designing Resilient Azure Infrastructure
Designing Scalable and Cost-Effective Compute
Failing to leverage Azure Reservations for stable, long-running workloads, missing out on significant discounts.
Designing Resilient Azure Infrastructure
Azure Virtual Network (VNet)
Logically isolated private network in Azure for resources.
Designing Resilient Azure Infrastructure
Network Security Group (NSG)
Filters network traffic to and from Azure resources based on rules.
Designing Resilient Azure Infrastructure
Application Security Group (ASG)
Simplifies NSG rule management by grouping VMs.
Designing Resilient Azure Infrastructure
Azure Traffic Manager
DNS-based traffic load balancer for global service distribution.
Designing Resilient Azure Infrastructure
Azure ExpressRoute
Private, dedicated connection to Azure, bypassing the public internet.
Designing Resilient Azure Infrastructure
Azure VPN Gateway
Connects on-premises networks to Azure VNets over the internet.
Designing Resilient Azure Infrastructure
Architecting Secure and Performant Network Solutions
V-N-S-G: 'Very Nice Security Guard' protects your network. App Gateway is for 'Apps', Front Door is 'Global', Traffic Manager 'Directs' traffic.
Designing Resilient Azure Infrastructure
Architecting Secure and Performant Network Solutions
The AZ-305 exam frequently tests the distinctions between Azure Load Balancer, Application Gateway, Front Door, and Traffic Manager. Pay close attention to their OSI layer, global vs. regional scope, and specific features like WAF or CDN integration.
Designing Resilient Azure Infrastructure
Architecting Secure and Performant Network Solutions
Confusing Azure Load Balancer (Layer 4, regional) with Application Gateway (Layer 7, regional, WAF) or Front Door (Layer 7, global, WAF, CDN).
Designing Resilient Azure Infrastructure
Architecting Secure and Performant Network Solutions
Not segmenting VNets into appropriate subnets and applying NSGs, leading to overly permissive network access.
Designing Resilient Azure Infrastructure
Architecting Secure and Performant Network Solutions
Using VPN Gateway for high-bandwidth, low-latency hybrid connectivity needs when ExpressRoute would be more appropriate.
Designing Resilient Azure Infrastructure
Microservices
Small, independent services for specific business capabilities.
Designing Resilient Azure Infrastructure
Serverless
Running code without managing servers; pay-per-execution.
Designing Resilient Azure Infrastructure
Event-Driven Architecture
Services communicate via events, promoting loose coupling.
Designing Resilient Azure Infrastructure
API-First Design
Designing APIs before implementation for consistency.
Designing Resilient Azure Infrastructure
Polyglot Persistence
Using multiple data stores for different data needs.
Designing Resilient Azure Infrastructure
Loose Coupling
Components operate independently, reducing dependencies.
Designing Resilient Azure Infrastructure
Observability
Ability to understand system's internal state from external outputs.
Designing Resilient Azure Infrastructure
Designing Modern Application Architectures on Azure
Think 'SMART' for Modern Apps: Scalable, Modular, Asynchronous, Resilient, Transparent (Observable).
Designing Resilient Azure Infrastructure
Designing Modern Application Architectures on Azure
For the AZ-305 exam, focus on matching specific Azure services to modern architectural patterns. For example, AKS for container orchestration, Azure Functions for serverless event processing, Event Hubs for high-throughput ingestion, and Cosmos DB for globally distributed NoSQL data. Understand the benefits (scalability, resilience, agility) and trade-offs of each approach.
Designing Resilient Azure Infrastructure
Designing Modern Application Architectures on Azure
Treating microservices like a distributed monolith, leading to tight coupling and complex deployments.
Designing Resilient Azure Infrastructure
Designing Modern Application Architectures on Azure
Over-engineering serverless solutions for long-running, stateful processes where traditional compute might be more cost-effective.
Designing Resilient Azure Infrastructure
Designing Modern Application Architectures on Azure
Neglecting observability in complex distributed systems, making troubleshooting extremely difficult.
Designing Resilient Azure Infrastructure
Azure Migrate
A central hub for discovery, assessment, and migration to Azure.
Designing Resilient Azure Infrastructure
Rehost (Lift-and-Shift)
Migrating applications to Azure VMs with minimal changes.
Designing Resilient Azure Infrastructure
Refactor
Making minor code changes to leverage Azure PaaS services.
Designing Resilient Azure Infrastructure
Azure Data Migration Service
A service for migrating databases to various Azure database platforms.
Designing Resilient Azure Infrastructure
6 Rs of Migration
Framework for migration strategies: Rehost, Refactor, Rearchitect, Rebuild, Replace, Retain.
Designing Resilient Azure Infrastructure
Discovery and Assessment
Process of inventorying and evaluating on-premises environment.
Designing Resilient Azure Infrastructure
Planning and Executing Azure Migration Strategies
Remember the 6 Rs of migration with: 'Really Rad Reptiles Rarely Run Right.' (Rehost, Refactor, Rearchitect, Rebuild, Replace, Retain)
Designing Resilient Azure Infrastructure
Planning and Executing Azure Migration Strategies
The AZ-305 exam frequently tests knowledge of the '6 Rs' of migration strategies and the primary use cases for Azure Migrate, Azure Data Migration Service, and Azure Site Recovery. Pay close attention to which tool is best suited for specific migration scenarios (e.g., database vs. VM).
Designing Resilient Azure Infrastructure
Planning and Executing Azure Migration Strategies
Underestimating the complexity of application dependencies during assessment.
Designing Resilient Azure Infrastructure
Planning and Executing Azure Migration Strategies
Failing to conduct thorough performance and user acceptance testing in Azure before cutover.
Designing Resilient Azure Infrastructure
Planning and Executing Azure Migration Strategies
Not having a clear rollback plan in case of unexpected issues during migration.
Designing Resilient Azure Infrastructure
Optimizing Infrastructure for Performance and Reliability
To remember the Azure load balancers: 'FAT' (Front Door, Application Gateway, Traffic Manager) are for 'global' or 'advanced' Layer 7 needs, while 'LB' (Load Balancer) is for 'local' Layer 4 distribution.
Designing Resilient Azure Infrastructure
Optimizing Infrastructure for Performance and Reliability
For the AZ-305 exam, differentiate clearly between Azure Load Balancer (Layer 4), Application Gateway (Layer 7, WAF), Front Door (Global Layer 7, WAF, CDN), and Traffic Manager (DNS-based global routing). Understand when to use each for HA/DR scenarios.
Designing Resilient Azure Infrastructure
Optimizing Infrastructure for Performance and Reliability
Confusing Availability Sets with Availability Zones; Zones offer better isolation.
Designing Resilient Azure Infrastructure
Optimizing Infrastructure for Performance and Reliability
Not defining clear RPO/RTO targets before designing DR solutions.
Designing Resilient Azure Infrastructure
Optimizing Infrastructure for Performance and Reliability
Using a simple Azure Load Balancer when Layer 7 features (WAF, URL routing) are required.
Designing Resilient Azure Infrastructure
Optimizing Infrastructure for Performance and Reliability
Neglecting monitoring and alerting until an outage occurs, rather than proactively setting them up.
Designing Resilient Azure Infrastructure