Practice Test #1

bcp (Bulk Copy Program) is a command-line tool for high-performance bulk data import/export between SQL Server/Azure SQL Database and data files. While it can execute a query to define exported rows, its primary purpose is bulk movement of data, not interactive or general-purpose querying. In exam terms, bcp aligns with data loading/unloading rather than querying.

azdata is a command-line tool associated with Azure data services administration scenarios (for example, SQL Managed Instance and Azure Arc-enabled data services) and integrates with some operational workflows. It is not the most common or canonical tool for simply querying Azure SQL Database with T-SQL in DP-900 context, making it a distractor here.

Azure CLI is used to manage Azure resources (provisioning, configuration, networking, identities), such as creating an Azure SQL logical server, configuring firewall rules, or setting policies. It is not a native T-SQL query client for Azure SQL Database. For running SQL queries, you would use tools like sqlcmd or client libraries rather than Azure CLI.

Microsoft SQL Server Management Studio (SSMS) is a primary administration tool for SQL Server and Azure SQL Database, offering query windows, Object Explorer, and management features. However, SSMS does not provide a native SQL notebook interface that combines Markdown documentation with executable cells and embedded results in a single notebook artifact. It’s great for interactive troubleshooting, but not for notebook-style documentation.

Azure CLI is primarily used for provisioning and managing Azure resources (e.g., creating servers, configuring firewall rules, managing identities). While it can execute some database-related commands and automate tasks, it is not designed to author SQL notebooks or embed documentation and query results together. It lacks the integrated notebook UI and rich document experience required by the question.

Azure PowerShell is also focused on automation and management of Azure resources through cmdlets. It can help with operational tasks (e.g., configuring Azure SQL settings, exporting data, managing resource properties), but it is not a notebook authoring tool for embedding documents and query results. Although PowerShell can be used in some notebook platforms, the Microsoft SQL notebook feature referenced here is Azure Data Studio.

Columnar stores (column-family or columnar analytics formats) are optimized for analytical workloads: scanning large datasets, aggregations, and high compression. They are common in data warehouses and OLAP scenarios (for example, Azure Synapse columnstore). They are not typically the best fit for high-volume operational writes of JSON with evolving structure, where low-latency point reads/writes and flexible schema are needed.

Key/value stores excel at very fast reads/writes when access is primarily by a single key (for example, caching, session state, simple lookups). While you can store JSON as a value, querying and indexing inside the JSON is usually limited or absent compared to document databases. For an application that needs to store and query JSON documents with an app-defined schema, document stores are generally the intended model.

Graph databases are optimized for modeling and querying relationships (nodes/edges) and performing traversals such as “friends of friends” or dependency chains. Although graph databases can store properties that look like JSON, the primary value is relationship-centric querying, not high-volume ingestion of JSON documents as the main workload. Use graph when relationships and traversals dominate the access patterns.

Azure Blob storage is object storage accessed via REST APIs (HTTP/HTTPS) and SDKs, optimized for unstructured data like images, logs, and backups. While you can simulate file access using tools or custom code, it is not a native SMB file share and is not intended to be mapped as a Windows drive for applications that require a mapped drive letter.

Azure Cosmos DB is a globally distributed NoSQL database service for low-latency, scalable data workloads (document, key-value, graph, column-family). It stores structured/semi-structured data and is accessed via database APIs, not as a file system. It cannot be mapped as a network drive and does not provide SMB file share functionality.

Azure Table storage (or Azure Tables in Storage accounts) is a NoSQL key-value store for large volumes of structured, non-relational data. It is accessed via REST APIs/SDKs and is designed for entities and properties, not files. It does not provide SMB shares and cannot satisfy a requirement for a Windows mapped drive.

Incorrect. Applying Azure policies for multi-tenant deployments is a governance scenario handled by Azure Policy (and policy initiatives), management groups, and RBAC. ARM templates can deploy policy definitions/assignments as resources, but the purpose described—applying policies for multi-tenant governance—is not what ARM templates are primarily “used for” in exam wording.

Incorrect. Provisioning Azure subscriptions is generally done through Azure billing/tenant processes, subscription creation APIs, or enterprise enrollment workflows, not via standard ARM template deployments. ARM templates deploy resources within an existing subscription (or at management group/tenant scope for certain resource types), but “provision subscriptions” is not the typical ARM template use case.

Incorrect. Controlling which services and features admins/developers can deploy from the Azure portal is primarily achieved with Azure Policy (deny/allowed SKUs/locations), RBAC, and sometimes management group governance. ARM templates can standardize deployments, but they do not directly restrict portal choices; governance controls do.

Zone-redundant storage (ZRS) replicates data synchronously across multiple availability zones within the same Azure region. It improves resiliency against a zonal outage, but it does not replicate to a different region. Therefore, it does not meet the requirement to replicate outside the Azure region automatically. ZRS is a “within-region” redundancy option, not a geo-replication option.

Locally-redundant storage (LRS) replicates data within a single datacenter in a single Azure region (multiple copies, but local only). It protects against local hardware failures but not against datacenter-wide or regional outages. Because it does not replicate to another region, it fails the requirement to replicate outside the Azure region automatically.