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?
Select an answer to reveal the explanation.
Short Explanation
Create-if-not-exists is the polite knock: make the locker if it is missing, leave it alone if it is already there. Deleting on every boot trashes existing photos. Blob uploads do not invent containers for you, and Cosmos is a different database.
Full Explanation
BlobContainerClient CreateIfNotExists (and language equivalents) creates the container when absent and succeeds when it already exists. Destructive delete-then-create risks data loss. The Blob service does not auto-create containers on upload, and Cosmos containers are unrelated to Blob Storage containers.