Free guides, interview Q&As, and job responsibility breakdowns — curated by industry veterans to help you crack MNC interviews
Definition: Azure Files is a fully managed cloud file storage service that lets you create file shares accessible over the network using the SMB (Server Message Block) and NFS (Network File System) protocols. It works like a normal shared folder, except it lives in the cloud instead of on a physical server. Multiple computers — Windows, Linux, macOS, or even on-premises servers — can connect to the same file share at the same time. Because Microsoft manages the backend hardware, patching, and availability, you don't need to buy or maintain any physical file server.
Azure Files Microsoft Azure की एक cloud-based file server service है। इसकी मदद से आप Windows shared folder की तरह file share बना सकते हैं। Server और storage को Microsoft manage करता है, इसलिए कई users और computers एक ही files को आसानी से access कर सकते हैं.
Real-Life Example: It's like a shared Google Drive folder that your whole office team can open directly as a mapped network drive (like 'Z:') instead of manually uploading and downloading files.
Definition: Azure Files removes the need to buy, maintain, and patch physical file servers, since Microsoft manages the entire infrastructure. It provides built-in high availability, cross-platform support (Windows, Linux, macOS), and integrates with Azure Backup for automatic snapshots. It also supports Azure File Sync, which caches frequently used files on a local Windows Server for faster access while keeping the master copy in the cloud. Data is encrypted both at rest and in transit, helping organizations meet security and compliance requirements.
इसका सबसे बड़ा लाभ यह है कि hardware खरीदने या maintain करने की आवश्यकता नहीं होती, क्योंकि Microsoft सब कुछ manage करता है। Backup और security अपने आप मिलते हैं, जिससे समय और लागत दोनों बचते हैं.
Real-Life Example: Similar to renting a fully-serviced storage locker where the facility handles security, maintenance, and climate control — you simply bring your items and use them.
Definition: SMB (Server Message Block) is a network protocol used to share files, printers, and other resources over a network. Azure Files supports SMB 2.1, SMB 3.0, and SMB 3.1.1. SMB 3.x versions are strongly recommended because they support encryption in transit (using AES-256-GCM) and deliver better performance than SMB 2.1, which sends data without encryption. Picking the right SMB version affects both security and application compatibility, which is frequently tested in the AZ-104 exam.
SMB एक protocol है जो computers के बीच file sharing के लिए उपयोग होता है। SMB 3.x अधिक secure होता है क्योंकि यह data को encrypt करके भेजता है, इसलिए production environment में इसे अधिक prefer किया जाता है.
Real-Life Example: Think of SMB versions like generations of a courier service — older versions deliver packages without extra security checks, while newer versions add tamper-proof sealed packaging (encryption).
Comparison of SMB Versions
| SMB Version | Encryption in Transit | Recommended For |
|---|---|---|
| SMB 2.1 | No | Legacy compatibility only |
| SMB 3.0 | Yes (AES-128) | General cloud + on-prem access |
| SMB 3.1.1 | Yes (AES-256-GCM) | Latest, most secure, internet-facing access |
Definition: Azure File Shares are commonly used for lift-and-shift migration of legacy applications that depend on a mapped network drive, centralized storage of shared configuration and diagnostic files, and as a full replacement for on-premises file servers. They are also used to provide shared storage across multiple VMs when a common dataset needs to be accessed simultaneously, and in hybrid scenarios through Azure File Sync where local caching improves performance for branch offices.
Real-Life Example: A company running a legacy accounting application that reads settings from a network drive can move that drive to Azure Files without changing a single line of application code.
Definition: Every Azure File Share must be created inside a Storage Account, which acts as the top-level management and billing boundary. The storage account decides the region, redundancy, performance tier, and access keys used by the file share. Without a storage account, no file share (or any other storage service) can exist, because the storage account provides the unique namespace under which all storage resources are organized.
Azure File Share बनाने से पहले Storage Account बनाना आवश्यक है, क्योंकि file share उसी के अंदर store होता है। Storage Account file shares के लिए parent container की तरह काम करता है.
Real-Life Example: Just like you need a bank account before you can rent a locker at that bank, you need a Storage Account before you can create a File Share.
💡 Memory Trick
Remember Azure Files with 'S-C-U-S': Shared access, Cloud-hosted, Uses SMB/NFS, Storage-Account-dependent.
⭐ Important Exam Points
⚠ Common Mistakes to Avoid
Definition: An Azure Storage Account is a top-level resource that provides a unique namespace for storing data objects such as blobs, files, queues, tables, and disks. It defines global settings like redundancy, performance tier, and networking rules that apply to all data stored within it. Every object in Azure Storage is accessed via a URL that includes the globally unique storage account name.
Storage Account Azure का मुख्य container है, जिसमें files, blobs, tables, और queues जैसे data को store किया जाता है। यह तय करता है कि data कहाँ store होगा और कितना सुरक्षित रहेगा.
Real-Life Example: Think of a Storage Account like a large warehouse — inside it you have sections for boxes (Blobs), folders (files), record cards (Tables), and message slips (Queues), but the whole building has one address.
Definition: A Storage Account is required because it is the mandatory administrative and billing boundary for all Azure Storage services — no blob, file share, queue, or table can exist independently of one. It centralizes security configuration such as access keys, Shared Access Signatures (SAS), firewall rules, and encryption settings.
Real-Life Example: Similar to a company registering itself before it can open individual departments — registration (storage account) must exist first.
Definition: Every storage account can host four core services: Blob Storage for unstructured data, Azure Files for SMB/NFS shares, Table Storage for NoSQL key-value data, and Queue Storage for asynchronous messaging. Each is optimized for a specific data pattern, and knowing which service fits which scenario is a key AZ-104 exam skill.
एक Storage Account में चार services होती हैं — Blob, Files, Table, और Queue। हर service अलग प्रकार के data और उसके specific use case के लिए बनाई गई है.
Storage Services at a Glance
| Service | Data Type | Access Method | Typical Use |
|---|---|---|---|
| Blob Storage | Unstructured (images, video, docs) | HTTP/HTTPS, REST API | Media, backups, big data |
| Azure Files | File shares | SMB / NFS | Shared drives, lift-and-shift |
| Table Storage | NoSQL key-value | REST API | Metadata, logs, IoT data |
| Queue Storage | Messages | REST API (HTTP/HTTPS) | Async messaging between apps |
Definition: Creating a Storage Account involves choosing the subscription, resource group, unique account name, region, performance tier (Standard or Premium), and redundancy option (LRS, ZRS, GRS, RA-GRS). Advanced settings include enabling hierarchical namespace for Data Lake, requiring secure transfer, and configuring network access rules.
Step-by-Step:
Real-Life Example: Similar to registering a new business — you choose a name, location, and plan type before you can start operating.
Definition: Storage Management covers ongoing administration tasks like monitoring usage metrics, configuring access via Azure RBAC or SAS tokens, setting lifecycle policies to automatically move or delete old data, and creating alerts for capacity or performance thresholds. Tools used include the Azure Portal, Azure CLI, PowerShell, and Azure Storage Explorer.
Storage Management का अर्थ है Storage Account की monitoring करना, security settings लागू करना, और storage cost को control करना.
Real-Life Example: Like managing a warehouse where you regularly check stock levels, control who has keys, and move old stock to cheaper long-term storage.
Definition: Blob Storage is Azure's object storage solution for massive amounts of unstructured data such as text, images, videos, and backups, accessed via REST APIs over HTTP/HTTPS. It supports tiered access, lifecycle policies, versioning, and soft delete for data protection.
Real-Life Example: Comparable to a giant digital photo album that can store any type of file.
Definition: As a storage service, Azure Files provides managed file shares accessible via SMB and NFS, functioning like a traditional network share but hosted in the cloud, with support for concurrent multi-client access and hybrid caching via Azure File Sync.
Real-Life Example: Functions like a shared network drive in an office that every employee's computer can map.
Definition: Table Storage is a NoSQL key-value store for structured, non-relational data with fast, low-cost access. It uses a schema-less design, so each entity (row) can have different properties, making it flexible for evolving data models.
Real-Life Example: Similar to a giant spreadsheet where each row can have slightly different columns.
Definition: Queue Storage enables asynchronous communication between application components by storing messages that can be retrieved via authenticated HTTP/HTTPS calls. It decouples senders and receivers so they don't need to operate at the same time.
Queue Storage एक waiting line की तरह काम करता है, जहाँ messages तब तक store रहते हैं जब तक कोई application या service उन्हें process नहीं करती.
Real-Life Example: Works like a restaurant order queue — orders are placed in line and the kitchen processes them one by one.
💡 Memory Trick
Remember the 4 services with 'B-F-T-Q': Blob, Files, Table, Queue — 'Big Files Take Queues'.
⭐ Important Exam Points
⚠ Common Mistakes to Avoid
Definition: Azure Blob Storage is a massively scalable object storage service for unstructured data such as documents, media files, log files, and backups. Blobs live inside containers within a storage account and are accessible globally over HTTP/HTTPS using a unique URL. It supports tiered access, lifecycle policies, versioning, and soft delete.
Blob Storage का उपयोग cloud में photos, videos, और documents जैसी files को store करने के लिए किया जाता है। Data को containers के अंदर store किया जाता है.
Real-Life Example: Similar to a massive digital storage room where you can drop any type of file without worrying about space.
Definition: Azure Blob Storage supports three blob types, each optimized for a different workload: Block Blobs for discrete large files, Append Blobs for append-only logging, and Page Blobs for random read/write access used by VM disks.
Blob के तीन प्रकार होते हैं: Block Blob सामान्य files के लिए, Append Blob logs के लिए, और Page Blob Virtual Machine disks के लिए उपयोग होता है। प्रत्येक प्रकार एक विशेष कार्य के लिए optimize किया गया है.
Blob Types Comparison
| Blob Type | Best For | Structure | Example Use |
|---|---|---|---|
| Block Blob | Large discrete files | Composed of blocks, committed together | Images, videos, documents |
| Append Blob | Append-only writes | New blocks added only at the end | Application/log files |
| Page Blob | Random read/write | 512-byte addressable pages | VM virtual hard disks (VHD) |
Definition: Block Blobs are the most common blob type, storing text and binary data by breaking large files into blocks that can be uploaded independently and then committed as one blob. This enables efficient parallel and resumable uploads for large files.
Real-Life Example: Comparable to assembling a jigsaw puzzle where pieces (blocks) are uploaded separately and then combined.
Definition: Append Blobs allow data to be added only at the end; existing content cannot be modified. This makes them ideal for scenarios like application logging where new entries are continuously written without altering history.
Real-Life Example: Similar to a visitor log book where new entries are always added at the bottom and old entries are never erased.
Definition: Page Blobs are optimized for frequent random read/write operations, organized into 512-byte addressable pages. They are the underlying format for Azure VM disks (VHDs), where the OS constantly reads and writes to random disk sectors.
Page Blob का उपयोग मुख्य रूप से Virtual Machine की hard disks (VHD files) के लिए किया जाता है। इसमें file के किसी भी random हिस्से को सीधे पढ़ा या update किया जा सकता है.
Real-Life Example: Works like a physical hard drive where the computer jumps to any specific sector to read/write data.
Definition: A Blob Container is a logical grouping for related blobs, similar to a folder. Every blob must live inside a container, and containers can have access-level settings such as private, blob-level public, or full container public access.
Container एक folder की तरह होता है, जिसमें Azure Blob Storage के blobs (files) store किए जाते हैं.
Real-Life Example: Similar to a labeled folder on your desktop where you organize related documents together.
Definition: Blob Storage is used to serve images/documents to browsers, stream video/audio, store backup and archival data, and provide data for analytics through services like Azure Data Lake and Databricks. Its tiered pricing makes it suitable for both hot and cold data.
Real-Life Example: A media streaming website storing thousands of videos in Blob Storage for global playback.
Definition: Access Tiers balance storage cost against access cost based on how frequently data is used: Hot, Cool, Cold, and Archive, each offering lower storage costs but higher retrieval costs/latency. Blobs can move between tiers manually or automatically via lifecycle policies.
Access Tiers यह बताते हैं कि data कितनी बार उपयोग होगा। बार-बार उपयोग होने वाला data Hot में, कभी-कभी उपयोग होने वाला data Cool या Cold में, और बहुत कम उपयोग होने वाला data Archive में रखा जाता है.
Access Tiers Comparison
| Tier | Access Frequency | Storage Cost | Retrieval Time | Min. Storage Duration |
|---|---|---|---|---|
| Hot | Frequent | Highest | Instant | None |
| Cool | Infrequent (<1/month) | Lower | Instant | 30 days |
| Cold | Rare | Lower than Cool | Instant | ~90 days |
| Archive | Very rare | Lowest | Hours (rehydration) | ~180 days |
💡 Memory Trick
Remember blob types with 'BAP': Block (big files), Append (add-only logs), Page (VM disks, random access).
⭐ Important Exam Points
⚠ Common Mistakes to Avoid
Definition: An Azure File Share is an individual, fully managed file system created within a storage account's Azure Files service, functioning like a shared network folder that multiple users or systems can access at once. Each storage account can host multiple file shares, each with its own quota and billing.
Real-Life Example: Comparable to a shared company drive where employees across departments open, edit, and save files together.
Definition: A File Share consists of the storage account hosting it, the share itself (root of the file system), directories/folders for organization, and individual files. Configurable properties include quota (max size), tier (Transaction Optimized, Hot, Cool, Premium), and protocol (SMB or NFS).
File Share के अंदर directories और files होती हैं, बिल्कुल सामान्य computer folder structure की तरह.
Real-Life Example: Similar to a physical filing cabinet (the share) with labeled drawers (directories) holding paper files (files).
Definition: SMB file sharing lets a file share be mounted directly as a network drive on Windows, Linux, and macOS clients using standard OS tools. Authentication can use storage account keys, Azure AD Domain Services, or on-premises AD DS. SMB 3.0+ connections are encrypted in transit.
Real-Life Example: Works exactly like mapping a network drive letter in Windows File Explorer, except the folder is hosted in Azure.
Definition: File Shares commonly replace on-premises file servers, host shared application configuration files accessed by multiple VMs, store centralized diagnostic/log data, and support lift-and-shift migrations for legacy applications. They also pair with Azure File Sync for hybrid caching.
Real-Life Example: A dev team storing shared build artifacts on a File Share accessible from all their build servers.
💡 Memory Trick
'Share = Storage + Hierarchy + Access' — a File Share always sits inside a Storage Account and has a folder hierarchy accessed via SMB/NFS.
⭐ Important Exam Points
⚠ Common Mistakes to Avoid
Definition: Azure Table Storage is a NoSQL key-value store for large volumes of structured, non-relational data at low cost. Unlike relational databases, it does not enforce a fixed schema, so each row can have a different set of properties. It is designed for fast lookups using a partition key and row key.
Table Storage एक simple NoSQL database है, जिसमें data बिना fixed structure के store किया जा सकता है। हर row में अलग-अलग properties हो सकती हैं.
Real-Life Example: Similar to a flexible address book where some contacts have just a phone number while others also have email and company name.
Definition: A Table is a collection of entities; an Entity is like a row in a relational database, made up of properties plus a mandatory PartitionKey and RowKey that together uniquely identify it. The PartitionKey groups related entities for efficient querying, while the RowKey uniquely identifies an entity within its partition.
Table के अंदर entities होती हैं, जो rows की तरह होती हैं। PartitionKey और RowKey मिलकर प्रत्येक entity की unique identity बनाते हैं.
Real-Life Example: Comparable to a library catalog where PartitionKey is the genre section ('Fiction') and RowKey is the book's catalog number within that section.
Definition: Table Storage suits large-scale structured data that doesn't need complex joins or transactions, such as user profiles, IoT device data, application logs, and metadata. It's cost-effective for fast, simple read/write operations at massive scale.
Real-Life Example: An IoT application storing temperature readings from thousands of sensors as simple entities.
💡 Memory Trick
'PK + RK = Unique' — PartitionKey groups data, RowKey makes each row unique within that group.
⭐ Important Exam Points
⚠ Common Mistakes to Avoid
Definition: Azure Queue Storage is a cloud messaging service that stores large numbers of small messages accessible asynchronously via authenticated HTTP/HTTPS calls. It decouples application components, letting producers and consumers operate independently and at different rates, improving reliability and scalability. Each message can be up to 64 KB, and a queue can hold millions of messages.
Queue Storage messages को तब तक store रखता है जब तक कोई दूसरा application उन्हें process नहीं करता। इससे दो systems बिना एक-दूसरे का इंतज़ार किए काम कर सकते हैं.
Real-Life Example: Similar to a ticket counter's token system — customers take a number and wait while staff serve tokens one at a time.
Definition: A Queue is a named container holding messages; a Message is the individual data unit placed into it, usually containing task instructions or event notifications. Messages stay in the queue until retrieved and deleted by a consumer. Azure guarantees at-least-once delivery, so applications must handle possible duplicate processing.
Queue एक container है जिसमें messages store होते हैं। Message process होने के बाद उसे delete करना आवश्यक है, वरना वह फिर से queue में दिखाई दे सकता है.
Real-Life Example: Like a to-do list sticky-note pad — each note (message) is added, and once done, it's removed.
Definition: Queue Storage is used to build resilient, decoupled architectures such as triggering background processing, distributing work across multiple workers, and buffering between a front-end web app and backend service to handle traffic spikes gracefully.
Real-Life Example: An e-commerce site placing new orders into a queue so a backend service can process payments without slowing the website.
💡 Memory Trick
'Queue = Decouple + Deliver' — it decouples sender/receiver and guarantees at-least-once delivery.
⭐ Important Exam Points
⚠ Common Mistakes to Avoid
Definition: Azure File Sync centralizes an organization's file shares in Azure Files while retaining the performance and compatibility of an on-premises Windows Server file server through local caching. An agent installed on the Windows Server synchronizes files between on-premises and the Azure File Share. Cloud tiering keeps infrequently used files only in Azure, represented locally as pointers, saving on-prem storage space.
Azure File Sync on-premises server और Azure File Share के बीच data को synchronized रखता है। पुरानी files अपने आप cloud में चली जाती हैं, जिससे local storage space बचता है.
Real-Life Example: Similar to how cloud photo apps keep recent photos on your phone but store older ones only in the cloud, downloading on demand.
Definition: Object Replication asynchronously copies block blobs between a source and destination storage account (same or different region) based on a replication policy. It's used to reduce latency for geographically distributed users, improve read performance, and maintain a secondary copy for compliance or disaster recovery. It requires blob versioning and change feed enabled on the source account.
Real-Life Example: Comparable to a global retail chain keeping duplicate stock in warehouses across different countries.
Definition: Storage Data Replication defines how many copies of data are kept and where, to protect against hardware failure, datacenter outage, or regional disaster. Options: LRS (3 copies, 1 datacenter), ZRS (spread across availability zones), GRS (replicated to a secondary paired region), RA-GRS (GRS + read access to secondary region).
Data Replication यह तय करता है कि data की कितनी copies store होंगी। LRS data को local region में रखता है, जबकि GRS और RA-GRS दूसरी region में भी copy रखते हैं, जिससे disaster के समय data सुरक्षित रहता है.
Redundancy Options Comparison
| Option | Copies | Scope | Read Access to Secondary |
|---|---|---|---|
| LRS | 3 | Single datacenter | No |
| ZRS | 3 | Multiple availability zones, same region | No |
| GRS | 6 (3+3) | Primary + paired secondary region | No |
| RA-GRS | 6 (3+3) | Primary + paired secondary region | Yes |
Definition: In data management, Access Tiers (Hot, Cool, Cold, Archive) are combined with lifecycle management policies to automatically move blobs between tiers based on age or last access, optimizing cost over the data's lifecycle — for example, moving blobs from Hot to Cool after 30 days of inactivity, and to Archive after 180 days.
Real-Life Example: Similar to an automatic email rule that archives emails older than a year without manual action.
💡 Memory Trick
Remember redundancy order with 'L-Z-G-R': LRS < ZRS < GRS < RA-GRS, increasing protection and cost.
⭐ Important Exam Points
⚠ Common Mistakes to Avoid
Definition: Azure Cosmos DB is a fully managed, globally distributed NoSQL and relational database service built for low-latency, high-availability access at any scale. It supports multiple APIs — SQL (Core), MongoDB, Cassandra, Gremlin, and Table — letting developers use familiar data models. Cosmos DB replicates data across any number of Azure regions with a few clicks, guaranteeing single-digit millisecond latency.
Azure Cosmos DB एक globally distributed database है, जो high speed और high availability प्रदान करता है। यह multiple database models और APIs को support करता है.
Real-Life Example: Comparable to a global chain of 24/7 stores with synchronized inventory, so you get the same fast service anywhere.
Definition: A NoSQL database is a non-relational database designed for data that doesn't fit neatly into rows and columns, offering flexible schemas and horizontal scalability. Types include document, key-value, column-family, and graph databases. Cosmos DB's Core (SQL) API uses a document-based model storing data as JSON.
NoSQL database पारंपरिक table-row-column structure को follow नहीं करता। यह data को JSON जैसे flexible format में store करता है.
Real-Life Example: Similar to a flexible filing system where each folder can hold a different set of documents, unlike a strict spreadsheet.
Definition: Cosmos DB offers guaranteed low latency, elastic scalability of throughput and storage independently, five consistency models to balance performance and accuracy, and a 99.999% availability SLA for multi-region deployments. It also auto-indexes all data without requiring schema management, and supports multiple APIs without vendor lock-in.
Real-Life Example: Like a highly efficient global courier service that delivers within seconds and never fails even during disasters.
Definition: Cosmos DB is used for real-time personalization, IoT/telemetry ingestion at scale, retail/e-commerce catalogs, gaming leaderboards needing instant updates, and globally distributed applications requiring consistent low-latency access worldwide.
Real-Life Example: A global gaming company using Cosmos DB for player profiles so leaderboards update near-instantly worldwide.
Definition: Creating a Cosmos DB account involves selecting the API (Core SQL, MongoDB, Cassandra, etc.), the subscription, resource group, account name, region, capacity mode (provisioned or serverless), and geo-redundancy options.
Step-by-Step:
Real-Life Example: Similar to opening a new bank branch before creating individual customer accounts inside it.
Definition: In a Cosmos DB account, a Database is a logical namespace managing a set of containers, while a Container is the fundamental unit of scalability where items are stored, indexed, and queried. Containers automatically partition data horizontally based on a specified partition key.
Database एक logical group होता है, जिसमें containers होते हैं। वास्तविक data containers के अंदर store किया जाता है.
Real-Life Example: Comparable to a library building (Database) containing multiple aisles (Containers) holding actual books (items).
Definition: Data is inserted and managed as JSON items within a container using the Portal's Data Explorer, SDKs (.NET, Java, Python), or REST APIs. Each item is automatically indexed by default, enabling fast queries without manual index setup. Administrators can perform full CRUD operations and run SQL-like queries against a container.
Real-Life Example: Similar to adding new product listings to an online store's catalog, instantly searchable as soon as added.
Definition: A Partition Key is a property chosen from the data used by Cosmos DB to distribute items across physical partitions, enabling horizontal scalability. Choosing an effective key is critical — a poorly chosen key can cause 'hot partitions' where one partition receives disproportionate traffic, leading to throttling. A good key has high cardinality and distributes reads/writes evenly, such as a customer ID.
Partition Key यह तय करता है कि data को partitions में कैसे बाँटकर store किया जाएगा। गलत key चुनने से hot partitions बन सकते हैं, जिससे performance कम हो जाती है.
Real-Life Example: Similar to organizing a library by author's last name — a good category spreads books evenly, a poor one overloads a few shelves.
💡 Memory Trick
Remember Cosmos DB hierarchy with 'A-D-C-I': Account > Database > Container > Item.
⭐ Important Exam Points
⚠ Common Mistakes to Avoid
What we will learn: This practical teaches how to provision a storage account from the Azure Portal and navigate the different storage services (Blob, File, Table, Queue) available within it.
What we will learn: This practical teaches how to set up an Azure File Share, organize it with folders and files, and connect to it using the SMB protocol like a real network drive.
What we will learn: This practical teaches how to create a blob container, upload files as blobs, and understand how switching between Hot, Cool, Cold, and Archive tiers affects cost and access.
What we will learn: This practical teaches the end-to-end workflow of provisioning Cosmos DB, structuring it with a database and container, inserting JSON data, and understanding the role of a partition key.
