A company uses Azure Stream Analytics to process IoT data from thousands of devices. They need to store the results in a way that supports fast querying for historical analysis. Which output sink should they use?
Designed for big data analytics and fast querying.
Why this answer
Azure Data Lake Storage Gen2 (ADLS Gen2) is the correct output sink because it combines a hierarchical namespace with Azure Blob Storage's scalable object storage, enabling fast querying for historical analysis via tools like Azure Synapse Analytics, PolyBase, or Apache Spark. ADLS Gen2 supports high-throughput writes from Stream Analytics and allows efficient directory-level operations and fine-grained access control, which are critical for large-scale IoT data analytics.
Exam trap
The trap here is that candidates often confuse Azure Blob Storage with ADLS Gen2, assuming both are equivalent for analytics, but the key differentiator is the hierarchical namespace and native integration with big data analytics engines that ADLS Gen2 provides.
How to eliminate wrong answers
Option A is wrong because Azure Table Storage is a NoSQL key-value store optimized for fast point lookups and small data volumes, not for complex historical queries or large-scale analytical workloads. Option B is wrong because Azure Blob Storage lacks a hierarchical namespace, making directory-level operations and fast querying for historical analysis less efficient compared to ADLS Gen2, and it does not natively support the same level of integration with analytics engines. Option D is wrong because Azure Event Hubs is a real-time data ingestion service, not a storage sink for historical analysis; it is designed for streaming data capture and event processing, not for long-term storage and querying.