Azure Fundamentals Databases: Complete Study Guide

Azure SQL Database is a fully managed relational database based on SQL Server. It's designed for structured data with complex relationships and requires ACID compliance. It excels with traditional business applications and complex queries.

Azure Cosmos DB is a NoSQL database providing multi-model support. It supports documents, key-value pairs, graphs, and columnar data. It's globally distributed by default and guarantees low latency worldwide.

Choose SQL Database when you need strong consistency and complex relationships. Choose Cosmos DB when you need global distribution and horizontal scalability for massive datasets. Both are fully managed, removing administrative burden, but they serve fundamentally different architectural needs.

Azure databases automatically perform backups without requiring any configuration.

Azure SQL Database maintains full backups weekly, differential backups daily, and transaction log backups every five to ten minutes. This enables point-in-time recovery up to thirty-five days.

Geo-replication creates replicas across regions, providing disaster recovery if entire regions fail. Automatic failover redirects connections to healthy replicas without application changes.

Recovery objectives depend on configuration. Recovery Time Objective (RTO) indicates how quickly services restore after failure. Recovery Point Objective (RPO) specifies acceptable data loss.

Azure provides different SLA levels based on redundancy configuration. Local redundancy costs less but offers no regional protection. Geo-redundant backups protect against regional outages. Understanding these mechanisms is crucial because Azure Fundamentals questions test disaster recovery planning knowledge.

Azure Cosmos DB offers five consistency levels balancing consistency, availability, and latency.

Strong consistency guarantees all readers see latest writes immediately. It increases latency and may reduce availability.

Bounded staleness allows slight data delays up to specified versions or time intervals.

Session consistency is the default and ensures consistency within user sessions while allowing eventual consistency for other clients.

Consistent prefix guarantees ordered writes appear in order globally.

Eventual consistency provides highest availability and lowest latency but allows temporary data staleness.

Applications must choose appropriate consistency based on requirements. Financial systems need strong consistency. Social media feeds tolerate eventual consistency.

Consistency directly impacts performance and cost because stronger consistency requires more synchronization between regions. Understanding these trade-offs demonstrates comprehension of distributed system challenges critical for Azure Fundamentals.

Azure provides specialized services for unstructured data like images, videos, documents, and logs.

Azure Blob Storage excels at storing massive quantities of unstructured data cost-effectively. It supports objects up to 4.75 terabytes and is ideal for media content, backups, and data lakes.

Azure Data Lake Storage combines hierarchical file system organization with Blob Storage. It optimizes specifically for analytics workloads.

For semi-structured data requiring document storage, Azure Cosmos DB's document model provides NoSQL capabilities with flexible schemas.

Azure Table Storage offers cost-effective options for massive key-value datasets.

Azure Files provides managed file shares accessible via SMB protocol.

Selection depends on access patterns and processing needs. Choose Data Lake Storage if you need to analyze data. Choose Cosmos DB if you need document queries. Choose Blob Storage for simple storage and retrieval at lowest cost.

Flashcards optimize learning through active recall and spaced repetition, both proven cognitive science techniques. Instead of passively reading about services, flashcards force you to retrieve information from memory. This strengthens neural pathways.

Spaced repetition reviews difficult cards more frequently than easy cards. This maximizes retention efficiency.

For Azure databases specifically, flashcards work excellently for learning service names, capabilities, consistency models, and appropriate use cases. Creating flashcards yourself deepens understanding as you identify key concepts.

Scenario-based flashcards where front sides present business problems and reverse sides identify appropriate Azure services are particularly effective. This mirrors real exam questions.

Flashcards are portable, allowing study during commutes. They're ideal for this topic because databases involve many distinct services with overlapping capabilities that students easily confuse.

Digital flashcard apps track your progress, showing which concepts need reinforcement. Combining flashcards with hands-on Azure account exploration creates comprehensive understanding.