MENU
You are designing an app that will use Azure Cosmos DB to collate sales data from multiple countries. You need to recommend an API for the app. The solution must meet the following requirements:
* Support SQL queries.
* Support geo-replication.
* Store and access data relationally.
Which API should you recommend?
Suggested Answer: C
Get Premium AZ-305 Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
33 comments · newest first
GI
Gilma
11 months ago
I think MongoDB might be a good option too, but not sure about SQL.
AU
Audra
11 months ago
NoSQL won't work for relational data, right?
KR
Krissy
11 months ago
Wait, can PostgreSQL really handle geo-replication effectively?
ED
Edelmira
11 months ago
Totally agree, it fits all the requirements.
HU
Huey
12 months ago
PostgreSQL is the way to go for SQL support!
KE
Kenneth
12 months ago
I feel like MongoDB is more for document storage, so it might not be the best option for this scenario.
GL
Glory
1 year ago
I’m a bit confused because I know NoSQL is popular, but it doesn’t really fit the relational aspect we need here.
RO
Ronna
1 year ago
I remember practicing a question about Azure Cosmos DB APIs, and I think PostgreSQL could be a good fit for relational data and geo-replication.
AL
Alonzo
1 year ago
I think the SQL API might be the right choice since it supports SQL queries, but I'm not entirely sure if it meets all the requirements.
EL
Elly
1 year ago
I'm a bit confused about the difference between some of these options, like Cache and External Storage. I'll need to review my notes to make sure I understand them properly.
QU
Quentin
1 year ago
Okay, I think I've got this. The question is asking us to identify which statements describe the correct application of the service-orientation principles during the service modeling process.
CA
Carlee
1 year ago
I'm a bit confused on this one. Does the agent's status automatically change when their queue status is updated? Or does it stay the same? I'll have to review the material again to be sure.
JE
Jessenia
1 year ago
As a certified Azure expert, I can confidently say that B) NoSQL is the way to go here. Cosmos DB is the perfect fit for this scenario. *winks* Didn't even need to think twice about it.
TA
Tawanna
1 year ago
Hold on, didn't you say we need to store and access data relationally? In that case, I'd go with A) PostgreSQL. Can't go wrong with a good ol' SQL database!
KE
Kenia
1 year ago
Hah, PostgreSQL? Really? That's a relational database, not NoSQL. Definitely going with B) NoSQL.
LO
Louisa
1 year ago
PostgreSQL may be relational, but NoSQL is the better option for this scenario.
YO
Youlanda
1 year ago
Definitely, NoSQL is the right API for supporting SQL queries and geo-replication.
NA
Nan
1 year ago
I agree, NoSQL is the best choice for storing and accessing data relationally.
DA
Dallas
1 year ago
NoSQL is the way to go for this app.
ST
Stephanie
1 year ago
I think option D) MongoDB is the best choice here. It meets all the requirements and is a popular NoSQL database choice.
MA
Marica
1 year ago
But MongoDB also supports geo-replication, which is important for this app.
TA
Talia
1 year ago
I think PostgreSQL might be a better option since it supports SQL queries.
BE
Beatriz
1 year ago
I agree, MongoDB is a great choice for this scenario.
JA
Jamey
1 year ago
The requirements clearly point to Azure Cosmos DB, so I would recommend option B) NoSQL. It supports SQL queries, geo-replication, and stores data relationally.
TR
Tracey
1 year ago
I agree, NoSQL is the most suitable API for this scenario.
HE
Helga
1 year ago
NoSQL is the way to go for supporting SQL queries and geo-replication.
SK
Skye
1 year ago
B) NoSQL would be the best option for this app.
DA
Dante
1 year ago
I see both points, but I think Apache Cassandra might be the best option as it supports SQL queries, geo-replication, and can store data relationally.
NA
Natalie
2 years ago
I disagree, I believe we should recommend MongoDB because it supports geo-replication and can store data relationally as well.
ME
Meaghan
2 years ago
I think we should recommend PostgreSQL because it supports SQL queries and can store data relationally.
PA
Paris
2 years ago
But MongoDB is a NoSQL database, it may not be the best choice for storing data relationally.
CE
Celestina
2 years ago
I disagree, I believe we should recommend MongoDB because it also supports SQL queries and geo-replication.
PA
Paris
2 years ago
I think we should recommend PostgreSQL because it supports SQL queries and can store data relationally.