Microsoft AZ-305 Exam - Topic 8 Question 40 Discussion

Actual exam question for Microsoft's AZ-305 exam

Question #: 40
Topic #: 8

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?

APostgreSQL

BNoSQL

CApache Cassandra

DMongoDB

Show Suggested Answer

Suggested Answer: C

by Bobbye at Jul 09, 2023, 07:22 PM

Limited Time Offer

25%

Off

Get Premium AZ-305 Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

Submit Cancel

Gilma

4 months ago

I think MongoDB might be a good option too, but not sure about SQL.

upvoted 0 times

...

Audra

4 months ago

NoSQL won't work for relational data, right?

upvoted 0 times

...

Krissy

4 months ago

Wait, can PostgreSQL really handle geo-replication effectively?

upvoted 0 times

...

Edelmira

4 months ago

Totally agree, it fits all the requirements.

upvoted 0 times

...

Huey

4 months ago

PostgreSQL is the way to go for SQL support!

upvoted 0 times

...

Kenneth

5 months ago

I feel like MongoDB is more for document storage, so it might not be the best option for this scenario.

upvoted 0 times

...

Glory

5 months ago

I’m a bit confused because I know NoSQL is popular, but it doesn’t really fit the relational aspect we need here.

upvoted 0 times

...

Ronna

5 months 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.

upvoted 0 times

...

Alonzo

5 months 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.

upvoted 0 times

...

Elly

5 months 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.

upvoted 0 times

...

Quentin

5 months 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.

upvoted 0 times

...

Carlee

5 months 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.

upvoted 0 times

...

Jessenia

10 months 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.

upvoted 0 times

...

Tawanna

10 months 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!

upvoted 0 times

...

Kenia

10 months ago

Hah, PostgreSQL? Really? That's a relational database, not NoSQL. Definitely going with B) NoSQL.

upvoted 0 times

Louisa

8 months ago

PostgreSQL may be relational, but NoSQL is the better option for this scenario.

upvoted 0 times

...

Youlanda

8 months ago

Definitely, NoSQL is the right API for supporting SQL queries and geo-replication.

upvoted 0 times

...

Nan

9 months ago

I agree, NoSQL is the best choice for storing and accessing data relationally.

upvoted 0 times

...

Dallas

9 months ago

NoSQL is the way to go for this app.

upvoted 0 times

...

Stephanie

10 months ago

I think option D) MongoDB is the best choice here. It meets all the requirements and is a popular NoSQL database choice.

upvoted 0 times

Marica

9 months ago

But MongoDB also supports geo-replication, which is important for this app.

upvoted 0 times

...

Talia

9 months ago

I think PostgreSQL might be a better option since it supports SQL queries.

upvoted 0 times

...

Beatriz

9 months ago

I agree, MongoDB is a great choice for this scenario.

upvoted 0 times

...

Jamey

10 months 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.

upvoted 0 times

Tracey

9 months ago

I agree, NoSQL is the most suitable API for this scenario.

upvoted 0 times

...

Helga

9 months ago

NoSQL is the way to go for supporting SQL queries and geo-replication.

upvoted 0 times

...

Skye

10 months ago

B) NoSQL would be the best option for this app.

upvoted 0 times

...

Dante

11 months 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.

upvoted 0 times

...

Natalie

11 months ago

I disagree, I believe we should recommend MongoDB because it supports geo-replication and can store data relationally as well.

upvoted 0 times

...

Meaghan

11 months ago

I think we should recommend PostgreSQL because it supports SQL queries and can store data relationally.

upvoted 0 times

...

Paris

11 months ago

But MongoDB is a NoSQL database, it may not be the best choice for storing data relationally.

upvoted 0 times

...

Celestina

11 months ago

I disagree, I believe we should recommend MongoDB because it also supports SQL queries and geo-replication.

upvoted 0 times

...

Paris

11 months ago

I think we should recommend PostgreSQL because it supports SQL queries and can store data relationally.

upvoted 0 times

...