Develop for Azure storage
AZ-204 · 57 questions
- A tidal-gauge lab talks about “the Cosmos table” as if one object holds everything. In the Azure Cosmos DB SDK, which resource hierarchy does the application address?
- An alpine-hut booking API has a Cosmos DB account in the portal, but the application still cannot read or write data. What must the developer instantiate first in code?
- A kelp-farm inventory deploy should ensure database kelp-db exists on first run and must not fail when the database is already present on later deploys. Which SDK approach fits?
- A lantern-festival ticketing app’s Cosmos container create fails when the team passes only a container name. What required property must the SDK supply at create time?
- A marsh-bird census API already knows a sighting’s item id and its species partition key and must load that one document as cheaply as possible. Which SDK operation should it use?
- A cider-press co-op must reject inserts when a batch id already exists, while a later nightly sync should insert-or-replace the same items. Which Cosmos SDK pair matches those rules?
- A tramway-maintenance log stores large Cosmos items. Operators must update only the lastInspected field without rewriting the entire document and risking clobbered concurrent edits. Which SDK approach fits best?
- A dune-rescue cache must return every kit whose status is open within one depot partition. The API does not know each kit’s item id in advance. Which Cosmos SDK approach is appropriate?
- An ice-road convoy tracker starts receiving HTTP 429 responses from Cosmos DB after a teammate replaced point reads with broad SELECT scans. What should the developer recognize as Cosmos throughput currency, and what should they prefer?
- Two canal-lock clerks update the same Cosmos lock item a second apart. How should the application prevent the second write from silently overwriting the first?
- A slate-quarry timesheet system has many small Cosmos containers that are idle most of the day and one occasionally busy container. Where can provisioned throughput be set so idle containers can share RU/s?
- 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?
- A municipal foghorn museum catalog stores each artifact as a Cosmos DB for NoSQL item. A curator retires one artifact and the app must remove only that document. Which SDK action should the developer call?
- A county sled-dog relay board treats Cosmos consistency as only “strong or eventual.” Which order lists the five official Cosmos DB consistency levels from strongest to weakest?
- A peat-bog research kiosk writes a sample id to Cosmos DB and must immediately read that same committed value from another region for a printed label. Which consistency level should the developer choose?
- A cliff-rail timetable site needs each clerk to see their own writes while the Cosmos account stays on the service default. Which consistency level should the developer name?
- A brine-works municipal payroll replica may lag behind the write region, but never by more than two minutes or five versions. Which Cosmos consistency level matches that requirement?
- A lichen-survey import writes two related items in one Cosmos transactional batch. Readers must never see the second item without the first. Which consistency level should the developer pick?
- A fjord-ferry cargo board only displays a running “crates scanned” total in Cosmos DB. A slightly outdated number is acceptable and ordering across updates does not matter. Which consistency level fits?
- A windmill bakery Cosmos account defaults to Session, but one dashboard query can tolerate Eventual to save RU. How should the developer apply that weaker setting?
- A glacier-guide booking Cosmos account enables multiple write regions, and an operator still tries to set Strong consistency. What should the developer know about that pairing?
- A salt-marsh nursery wants every insert and update on plant items, in modification order, without polling the Cosmos container. Which Cosmos mechanism should the developer use?
- A copper-roof workshop runs a long-lived worker that must checkpoint Cosmos change-feed progress so a restart does not replay the entire history. Which approach should the developer use?
- A birch-sap bottling line deletes a bad batch item from Cosmos DB, but a latest-version change feed consumer never receives that delete. Why?
- A rope-bridge inspection feed must include deletes and intermediate item versions from Cosmos DB. Which change feed configuration should the developer select?
- A thistle-farm CSA backfill must replay Cosmos change history, while a live packer station should only see new changes from now on. What should the developer configure for each consumer?
- An aurora-watch lodge already runs a Cosmos-triggered Azure Function. A second long-running worker in Azure Container Apps must consume the same container’s changes. Which Domain 2 approach fits the Container App?
- A kelp-drying loft scales three change feed processor workers against one large Cosmos container. How should work be distributed?
- A pebble-beach rental tool wants to page Cosmos changes on demand instead of hosting a continuous processor loop. Which official approach should the developer use?
- A herring-smoke house stores Content-Type and a custom smoker-bay label on the same Azure blob. How should the developer treat those two pieces of information in the Blob SDK?
- A moss-garden festival ticket scan must persist booth=north and day=sat on an image blob without changing the image bytes. Which Blob SDK action should the developer take?
- A spruce-mill inventory download opens in the browser as a generic octet-stream instead of a PDF. Which Blob SDK fix should the developer apply?
- A tide-pool classroom app only needs Last-Modified and the module metadata before deciding whether to fetch a 2 GB clip. Which Blob SDK call should it make first?
- A granite-stair repair photo blob already has metadata crew=a. A later Set Metadata call sends only shift=night, and crew disappears. What should the developer understand?
- A cranberry-bog scale team set season=fall as metadata on the container, but a blob listing does not show that value on each file. Where should the developer read season=fall?
- A lighthouse-keeper log blob is snapshotted, then the live blob’s Content-Type is changed. The app needs the headers from before that change. What should the developer do?
- A willow-basket guild stores finished photos in Blob Storage and wants Find Blobs by Tags plus lifecycle filters on status=ready without putting that key in x-ms-meta user metadata. Which Blob Storage feature should the developer use?
- A snowpack-sensor uploader constructs one Azure Blob SDK object and expects that same object to list every container in the account and also upload a file into one container. Which v12 client choice matches those two scopes?
- A reed-bed filter lab must drop a CSV onto a blob path that may already exist and replace the prior file in place. Which Azure Blob Storage SDK operation should the developer call?
- An amber-workshop order form must pull a finished pattern blob from Azure Blob Storage and save the bytes to local disk for a cutter workstation. Which SDK operation should the developer use?
- A cobble-street market stall app should ensure container stall-photos exists on first boot without failing when the container is already present. Which Blob SDK approach should the developer take?
- A pine-resin still stores jar photos under the virtual folder 2026/aug/ in one blob container and must list only that folder’s blobs. Which approach should the developer use with the Blob SDK?
- A frost-fair stall writes a continuously growing JSON audit log to Blob Storage, while ordinary product photos are stored as discrete files. Which blob type pairing should the developer choose?
- An otter-watch camera archive must duplicate a clip from an ingest container into a review container in the same storage account without pulling the bytes through the application host. Which Blob SDK approach should the developer use?
- A barley-malt silo app deletes a mistyped lot photo with the Blob SDK. Soft delete is enabled on the account. What should the developer expect immediately after a successful delete call?
- Two cairn-trail map builders must not overwrite the same GeoJSON blob at the same time. Which Blob Storage SDK concurrency tool should they use for an exclusive write?
- A driftwood gallery must move last year’s exhibit photos to the Cool access tier immediately without waiting for a lifecycle policy evaluation. Which Blob SDK action should the developer take?
- A heather-honey coop pasted the storage account key into appsettings.json checked into source control. How should the developer construct the Azure Blob Storage v12 client instead?
- A fjord-cabin photo album stores binary images with blob metadata in Azure. A teammate proposes Queue Storage or Azure SQL as the primary store because both are “Azure storage.” Which service selection matches Domain 2 for these objects?
- A nettle-tea factory wants blobs unused for 30 days moved to Cool and blobs unused for 365 days deleted, without writing a timer Function that lists and deletes. What should the developer configure?
- A basalt-column tour archive is rarely read and must map storage cost to how often content is accessed. Which official Blob access tier set should the developer use when planning lifecycle targets?
- A plover-nest watch account stores blobs under raw/ and publish/; only raw/ should move to Archive after inactivity. How should the developer scope the lifecycle rule?
- A flax-mill ledger blob is in the Archive tier. A clerk asks for a lifecycle policy that periodically moves it back to Hot on a calendar. What should the developer tell them?
- A pumice-quarry log blob in the Archive tier fails when the app calls Download. What must the developer do before the content can be read?
- A sedge-meadow hydrology team wants one container-side place to revise expiry for several service SAS tokens without regenerating each signature string from scratch. What should the developer define?
- A wicker-ferry ticket scan is deleted while blob soft delete retention is 14 days, so the object remains recoverable and billable during that window. How should the developer contrast this with a lifecycle delete action?
- A lichen-crust legal archive has a time-based immutability (retention) policy on its blobs. A lifecycle rule tries to delete those objects after 400 days. What happens?