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?
Select an answer to reveal the explanation.
Short Explanation
You already have the id and the partition key—that’s a point read, the express lane. Don’t drag a SELECT * fishing net across the whole marsh for one bird.
Full Explanation
Cosmos DB point reads retrieve a single item using id and partition key and typically consume fewer request units than queries. Broad cross-partition queries, migration-tool exports, and change-feed replays are inappropriate for a known-key single-item load. Recognizing point operations versus queries is the AZ-204 SDK skill here.