Prepare and test your skills

Prepare and test your skills

Free sample question, answered and explained below. The AZ-900 Microsoft Azure Fundamentals Exam practice bank has 688 more like it. Try 10 free: instant score, no account.
An organization is migrating an on-premises enterprise application to Azure Virtual Machines. The application requires a centralized shared file system that multiple virtual machines can access simultaneously with read and write permissions using standard file-sharing protocols such as Server Message Block (SMB) or Network File System (NFS).
Which Azure storage service should the organization implement?
Azure Blob Storage is Microsoft's massively scalable object storage solution designed for unstructured data such as text, media, documents, backups, and log files.
While Blob Storage is optimized for storing vast amounts of data accessible via HTTP/HTTPS, it is an object store rather than a traditional hierarchical file system. It does not provide standard SMB file shares for legacy application file system integration, nor is it designed to replace a multi-VM mapped network drive without specialized application modification or specific configurations.
The organization needed to serve images or videos directly to web browsers, store unstructured telemetry and backup archives, or stream media globally.
Azure Blob Storage is commonly paired with compute services for massive data lake analytics and static content distribution, but it is not the primary service for standard SMB file sharing across multiple virtual machines.
Azure Queue Storage is a messaging service used for storing and retrieving large volumes of messages to enable reliable asynchronous communication between decoupled application components.
Queue Storage is strictly designed for application messaging workflows and cannot store files, host directories, or provide SMB/NFS network shares. It provides temporary storage for individual messages rather than durable file storage for virtual machines.
The organization needed an asynchronous messaging queue to buffer work orders or coordinate tasks between frontend web tiers and backend worker processes.
Queue Storage is an essential tool for decoupling cloud architectures to build resilient, scalable microservices, but it serves an entirely different function than file storage.
Azure Table Storage is a NoSQL key-value datastore that provides schemaless storage for large volumes of non-relational, structured datasets.
Table Storage is designed to store structured entities (rows with properties and attributes) in tabular formats. It does not store binary application files or present a mountable file share for virtual machines over network protocols like SMB or NFS.
The organization needed a low-cost, high-scale NoSQL database to store flexible user profile attributes or device metadata that does not require complex relational joins.
For advanced NoSQL tabular scenarios requiring guaranteed millisecond latency and global distribution, Microsoft offers Azure Cosmos DB for Table as a premium alternative to standard Azure Table Storage.
Azure Files is a fully managed cloud service that provides serverless, cloud-based network file shares. It enables applications and virtual machines to access file systems using industry-standard protocols without managing physical file servers.
Azure Files satisfies all scenario needs through native support for:
Unlike object or database storage solutions, Azure Files natively implements file system semantics such as directory hierarchies, file locking, and standard file-sharing protocols, making it the ideal choice for multi-VM shared file storage.
Answer them yourself and get your score the moment you finish. No account needed.
Full access includes
Keep the momentum going with these hand-picked practice scenarios
Last updated Validated