Choosing a Cosmos DB API by familiarity
The wrong answers pick a Cosmos DB API by habit, often API for NoSQL as the native default, when the scenario names an existing protocol or data model. Cassandra tooling with CQL drivers points to API for Apache Cassandra, Azure Table Storage client code points to API for Table, an established document codebase points to API for MongoDB, and relationship traversal points to API for Gremlin. API for NoSQL is the answer only for a new build with no driver investment.
See it in a sample questionReaching for Strong consistency by default
The wrong answers choose Strong consistency whenever a requirement sounds demanding, when a weaker level meets it. Strong reads cost 2x the request units, and Strong adds write latency the workload does not need. A single-region app where each user must see their own writes fits Session, whose reads cost the same as Eventual. A service with one write region whose reads may lag by at most 100 versions or 5 seconds fits Bounded staleness, the near-strong choice.
See it in a sample questionPairing Archive with zone redundancy
The wrong answers combine the Archive access tier with zone-redundant storage because the scenario asks for resilience. Archive supports only LRS, GRS, and RA-GRS, so ZRS, GZRS, and RA-GZRS are all invalid with it. When a workload wants the lowest storage cost and a rehydrate of up to 15 hours is acceptable, the answer is Archive on LRS, or on GRS or RA-GRS where geo-replication is required.
See it in a sample questionTreating geo-replication and failover groups as one feature
The wrong answers swap active geo-replication and failover groups. Active geo-replication has no stable listener, so the connection string changes after failover because the new primary lives on a different logical server. A failover group adds the read-write listener, and its customer-managed policy keeps the failover decision with people. Chaining a geo-replica is an active geo-replication technique that failover groups with multiple secondaries do not allow.
See it in a sample questionConfusing Data Factory, Synapse, and Databricks
The wrong answers swap Azure Data Factory, Azure Synapse Analytics, and Azure Databricks. Data Factory is code-free orchestration with 90-plus connectors and no analytics workspace. Synapse combines dedicated and serverless SQL, Spark pools, and the T-SQL PREDICT function in one workspace. Databricks is where MLflow, Delta Lake, and Unity Catalog live, while Synapse governance is Synapse RBAC. Synapse embeds the same Data Factory engine, but only Synapse adds SQL and Spark pools.
See it in a sample question