From the course: Microsoft Azure Cosmos DB Developer Specialty (DP-420) Cert Prep by Microsoft Press

Unlock this course with a free trial

Join today to access over 24,800 courses taught by industry experts.

Evaluate response status code and failure metrics

Evaluate response status code and failure metrics

From the course: Microsoft Azure Cosmos DB Developer Specialty (DP-420) Cert Prep by Microsoft Press

Start my 1-month free trial Buy for my team

Evaluate response status code and failure metrics

“

- [Instructor] Let's take a look at this table of common Cosmos DB status codes. Now, do you have to memorize these for your DP420 exam? No, because the exam's not going to test your fact recall. It's going to test your ability to analyze and synthesize data and apply your Cosmos skills. But that having been said, you'll probably find in practice that if you see these often enough, they will become intuitively clear. 200 of course, is our preferred HTTP status code. There, it's an okay operation, operation with successful. If you have an issue with your JSON, you can expect to see a 400 bad request. If you're calling an item that may have been deleted, not found, 404 error. You know, you see that on the worldwide web, the resource no longer exists. 408 is a request timeout. Remember that when we're doing server side codes, stored procedures, user-defined functions and triggers, there's that bounded execution context. 408's…

Contents