Microsoft Exam AZ-204 Topic 16 Question 80 Discussion

Actual exam question for Microsoft's AZ-204 exam

Question #: 80
Topic #: 16

You are developing a solution that will use a multi-partitioned Azure Cosmos DB database. You plan to use the latest Azure Cosmos DB SDK for development.

The solution must meet the following requirements:

Send insert and update operations to an Azure Blob storage account.

Process changes to all partitions immediately.

Allow parallelization of change processing.

You need to process the Azure Cosmos DB operations.

What are two possible ways to achieve this goal? Each correct answer presents a complete solution.

NOTE: Each correct selection is worth one point.

ACreate an Azure App Service API and implement the change feed estimator of the SDK. Scale the API by using multiple Azure App Service instances.

BCreate a background job in an Azure Kubernetes Service and implement the change feed feature of the SDK.

CCreate an Azure Function to use a trigger for Azure Cosmos DB. Configure the trigger to connect to the container.

DCreate an Azure Function that uses a Feedlterator object that processes the change feed by using the pull model on the container. Use a FeedRange objext to parallelize the processing of the change feed across multiple functions.

Show Suggested Answer

Suggested Answer: A

by Peggie at Aug 29, 2023, 04:28 PM

Limited Time Offer

25%

Off

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

Contribute your Thoughts:

Submit Cancel

Lizbeth

2 months ago

Ah, the joys of Cosmos DB. I bet the developers at Microsoft spent months debating whether to call it 'change feed' or 'feed change'. Either way, it sounds like a delicious breakfast option.

upvoted 0 times

Lezlie

28 days ago

A) Create an Azure App Service API and implement the change feed estimator of the SDK. Scale the API by using multiple Azure App Service instances.

upvoted 0 times

...

Annelle

2 months ago

Wait, we have to choose two options? I thought this was a single-select question. *scratches head* Well, I guess I'll go with options C and D then. Double the points, double the fun!

upvoted 0 times

...

Golda

2 months ago

Option B with Azure Kubernetes Service sounds interesting, but I'm not sure if it's overkill for this use case. Seems like a lot of overhead just to process Cosmos DB changes.

upvoted 0 times

Shoshana

24 days ago

Option B might be overkill for this scenario. Maybe consider a simpler solution like option A.

upvoted 0 times

...

Shawn

27 days ago

B) Create a background job in an Azure Kubernetes Service and implement the change feed feature of the SDK.

upvoted 0 times

...

Annabelle

29 days ago

A) Create an Azure App Service API and implement the change feed estimator of the SDK. Scale the API by using multiple Azure App Service instances.

upvoted 0 times

...

Mabel

2 months ago

I like the idea of using Azure Functions in option D. The ability to parallelize the change feed processing across multiple functions is really appealing.

upvoted 0 times

Merlyn

25 days ago

I agree, Azure Functions in option D seem to be the best way to achieve the goal. It allows for parallel processing of the change feed.

upvoted 0 times

...

Lavelle

27 days ago

Option D sounds like a good choice. Using Azure Functions to parallelize the change feed processing is efficient.

upvoted 0 times

...

Erasmo

1 months ago

I agree, Option D seems like the most efficient way to handle the Azure Cosmos DB operations with parallelization.

upvoted 0 times

...

Kristeen

2 months ago

Option D sounds like a great choice. It allows for parallel processing of the change feed using multiple functions.

upvoted 0 times

...

Denny

2 months ago

Option C seems like the simplest and most straightforward way to achieve the requirements. Azure Functions with a Cosmos DB trigger will handle the change processing automatically.

upvoted 0 times

Leanna

21 days ago

Azure Functions with a Cosmos DB trigger definitely seems like the way to go for processing the operations efficiently.

upvoted 0 times

...

Dong

25 days ago

Creating an Azure Function with a trigger for Cosmos DB sounds efficient and easy to implement.

upvoted 0 times

...

Florinda

2 months ago

I agree, using Azure Functions with a Cosmos DB trigger simplifies the process and automates the change processing.

upvoted 0 times

...

Roselle

2 months ago

Option C seems like the simplest and most straightforward way to achieve the requirements. Azure Functions with a Cosmos DB trigger will handle the change processing automatically.

upvoted 0 times

...