Bash, the Crucial Exams Chat Bot
AI Bot
AZ-900 Scalability, Resiliency, and Performance Flashcards
| Front | Back |
| Auto-scaling in Azure | Automatically adjust compute resources based on demand |
| Availability Sets | Enable redundancy for VMs by spreading them across multiple fault and update domains |
| Availability Zones | Physically separate datacenter locations within an Azure region for enhanced resiliency |
| Azure Application Gateway | Layer 7 load balancing service that provides TLS termination and web traffic distribution |
| Azure Backup | Integrated service for backing up and recovering data in Azure |
| Azure Cache for Redis | In-memory data store that improves application performance and scalability |
| Azure ExpressRoute | Private connection between on-premises infrastructure and Azure datacenters for greater reliability |
| Azure Front Door | Global service for web acceleration and application security with Dynamic Site Acceleration |
| Azure Resource Health | Reports on the health of individual Azure resources and recommends actions |
| Azure Service Health | Personalized alerting and guidance when Azure service issues affect you |
| Azure Traffic Manager | DNS-based load balancing across multiple service endpoints or regions |
| Content Delivery Network (CDN) | Distributed network that caches content closer to end users for better performance |
| Cosmos DB Multi-Region Writes | Global distribution feature allowing write operations in multiple regions |
| Fault Domains | Physical groupings of hardware to limit the impact of potential failures |
| Load Balancing | Distributes incoming network traffic across multiple healthy targets |
| Multi-region Deployment | Hosting services in more than one Azure region for high availability and low latency |
| Premium SSD v2 | High-performance storage option for Azure VMs with submillisecond latency |
| Read-Access Geo-Redundant Storage (RA-GRS) | Storage replication that provides read access to data in a secondary region |
| Recovery Point Objective (RPO) | Maximum acceptable data loss measured in time before a disaster |
| Recovery Time Objective (RTO) | Maximum acceptable time to restore a system after a disaster |
| Resiliency Design Patterns | Strategies like Circuit Breaker, Bulkhead, and Retry that improve application reliability |
| Scaling vertically vs horizontally | Vertical scaling adds power to existing servers while horizontal scaling adds more servers |
| Site Recovery | Orchestrates disaster recovery to secondary Azure regions or on-premises sites |
| SLA (Service Level Agreement) | Microsoft's commitment to uptime and connectivity for specific Azure services |
| Storage Redundancy Options | LRS/ZRS/GRS/RA-GRS options that protect data against failures |
| Transient Fault Handling | Techniques for managing temporary failures in cloud services including retry logic |
| Update Domains | Logical groupings that allow Azure to roll out updates with minimal downtime |
| Virtual Machine Scale Sets | Create and manage a group of identical VMs that can automatically increase or decrease |
| VM Proximity Placement Groups | Feature that minimizes the physical distance between VMs to reduce network latency |
| Zone-Redundant Storage (ZRS) | Replicates data synchronously across three storage clusters in different availability zones |
Front
Storage Redundancy Options
Click the card to flip
Back
LRS/ZRS/GRS/RA-GRS options that protect data against failures
Front
Virtual Machine Scale Sets
Back
Create and manage a group of identical VMs that can automatically increase or decrease
Front
Scaling vertically vs horizontally
Back
Vertical scaling adds power to existing servers while horizontal scaling adds more servers
Front
Azure Backup
Back
Integrated service for backing up and recovering data in Azure
Front
Recovery Point Objective (RPO)
Back
Maximum acceptable data loss measured in time before a disaster
Front
VM Proximity Placement Groups
Back
Feature that minimizes the physical distance between VMs to reduce network latency
Front
Resiliency Design Patterns
Back
Strategies like Circuit Breaker, Bulkhead, and Retry that improve application reliability
Front
Premium SSD v2
Back
High-performance storage option for Azure VMs with submillisecond latency
Front
Zone-Redundant Storage (ZRS)
Back
Replicates data synchronously across three storage clusters in different availability zones
Front
Azure Service Health
Back
Personalized alerting and guidance when Azure service issues affect you
Front
Azure ExpressRoute
Back
Private connection between on-premises infrastructure and Azure datacenters for greater reliability
Front
Transient Fault Handling
Back
Techniques for managing temporary failures in cloud services including retry logic
Front
Multi-region Deployment
Back
Hosting services in more than one Azure region for high availability and low latency
Front
Auto-scaling in Azure
Back
Automatically adjust compute resources based on demand
Front
Load Balancing
Back
Distributes incoming network traffic across multiple healthy targets
Front
SLA (Service Level Agreement)
Back
Microsoft's commitment to uptime and connectivity for specific Azure services
Front
Cosmos DB Multi-Region Writes
Back
Global distribution feature allowing write operations in multiple regions
Front
Azure Resource Health
Back
Reports on the health of individual Azure resources and recommends actions
Front
Azure Front Door
Back
Global service for web acceleration and application security with Dynamic Site Acceleration
Front
Recovery Time Objective (RTO)
Back
Maximum acceptable time to restore a system after a disaster
Front
Read-Access Geo-Redundant Storage (RA-GRS)
Back
Storage replication that provides read access to data in a secondary region
Front
Azure Traffic Manager
Back
DNS-based load balancing across multiple service endpoints or regions
Front
Azure Application Gateway
Back
Layer 7 load balancing service that provides TLS termination and web traffic distribution
Front
Update Domains
Back
Logical groupings that allow Azure to roll out updates with minimal downtime
Front
Availability Sets
Back
Enable redundancy for VMs by spreading them across multiple fault and update domains
Front
Azure Cache for Redis
Back
In-memory data store that improves application performance and scalability
Front
Content Delivery Network (CDN)
Back
Distributed network that caches content closer to end users for better performance
Front
Fault Domains
Back
Physical groupings of hardware to limit the impact of potential failures
Front
Availability Zones
Back
Physically separate datacenter locations within an Azure region for enhanced resiliency
Front
Site Recovery
Back
Orchestrates disaster recovery to secondary Azure regions or on-premises sites
1/30
This deck addresses Azure's scalability options, high availability solutions, fault tolerance, and performance optimization practices for building resilient applications in the cloud.