Bash, the Crucial Exams Chat Bot
AI Bot
AZ-900 Scalability, Resiliency, and Performance Flashcards
Microsoft Azure Fundamentals AZ-900 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 |
This deck addresses Azure's scalability options, high availability solutions, fault tolerance, and performance optimization practices for building resilient applications in the cloud.