A harbor oyster-bed permit desk is building a new Azure app for permit documents as JSON items. Which storage path matches the native AZ-204 Cosmos DB SDK skill for this workload?
Select an answer to reveal the explanation.
Short Explanation
Think of Cosmos for NoSQL as the native JSON filing cabinet Azure already built for this exam. Wire the Cosmos SDK to containers and items—not SQL tables, Table entities, or file shares. That is the Domain 2 path when the app is new on Azure, not a Mongo port.
Full Explanation
For a new harbor oyster-bed permit desk that stores permit documents as JSON items, Azure Cosmos DB for NoSQL with the Cosmos DB SDK is the Domain 2 path AZ-204 expects. The SDK works against databases, containers, and items: you create a container with a partition key, then create, read, replace, upsert, or delete documents that are already JSON-shaped. That matches a greenfield Azure app whose primary model is document items rather than relational rows or file bytes.
Azure SQL Database with T-SQL and Microsoft.Data.SqlClient is a strong relational choice, but it forces you into tables, schemas, and a SQL client stack instead of the Cosmos container/item APIs this skill measures. Azure Table Storage entities with the legacy Table client store property bags under partition and row keys; they are not the Cosmos SDK model and lack Cosmos’s richer querying and consistency ladder. Azure Files SMB shares plus System.IO treat permits as filesystem paths—useful for documents-as-files, not for native JSON item operations in Cosmos.
Exam caveat: Cosmos also offers MongoDB, Cassandra, Gremlin, and Table APIs for migration scenarios; for brand-new JSON workloads on this blueprint, the NoSQL API and Cosmos SDK remain the targeted answer unless the stem explicitly names a compatibility API.
Operational check: after provisioning, confirm the app’s connection string or Microsoft Entra identity can reach the account, create a container with an intentional partition key (for example permitId or municipalityCode), and verify a round-trip CreateItem/ReadItem before wiring the full permit desk UI.