Exam AZ-204 All QuestionsBrowse all questions from this exam
Go to Exam
Question 186

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.

    Correct Answer: C, D

    To meet the requirements, the solution must handle inserting and updating operations in Azure Cosmos DB, process changes across all partitions immediately, and allow parallel processing. Using an Azure Function with a Cosmos DB trigger allows for immediate reaction to changes in the database and leverages the change feed processor to parallelize processing across partitions (C). Additionally, using an Azure Function with a FeedIterator object and a FeedRange object offers fine control over processing the change feed by pulling changes and parallelizing across multiple functions (D). Both options provide the required capabilities for processing changes immediately and in parallel.

Discussion
ZulhinOptions: CD

Answer C & D. "What are two possible ways to achieve this goal?"

Chiboy

C is the correct answer. Each answer has two possible ways that in combination, gives the solution. Moreover, because of the requirement to "Process changes to all partitions immediately", D cannot be the answer or part of it since it "processes the change feed by using the pull model on the container"

Baskman

Agree with C & D "NOTE: Each correct selection is worth one point."

ProtossOR89144

D is good - https://learn.microsoft.com/en-us/azure/cosmos-db/nosql/read-change-feed - it says: "However, there are some scenarios where you might want the additional low level control of the pull model. These include: Reading changes from a particular partition key"

aradiceOptions: CD

c and d ? https://docs.microsoft.com/en-us/azure/cosmos-db/read-change-feed#azure-functions https://docs.microsoft.com/en-us/azure/cosmos-db/change-feed-pull-model#using-feedrange-for-parallelization

Jurgen1234

I agree

adilkhanOptions: CD

CD (36%) D (21%) A (21%) Other ...OMG :D

giuliohome

It's C and D, you can exclude A because it's sequential but in the question it's required to allow parallelization instead.

adilkhanOptions: CD

C,D chatGPT

Ciupaz

In my case chatGPT response is A and C.

Ciupaz

Bard, instead, returns: A - D

OPT_001122Options: CD

c and d

MunwalinwaliOptions: CD

Answer C & D.

carlosfaria82Options: CD

C: "Because Azure Functions uses the change feed processor behind the scenes, it automatically parallelizes change processing across your container's partitions." D: "You can use the change feed pull model to consume the Azure Cosmos DB change feed at your own pace. Similar to the change feed processor, you can use the change feed pull model to parallelize the processing of changes across multiple change feed consumers."

raymond_abcdOptions: CD

Answer C and D C you need to implement the lease container in the function for dynamic scaling and works with multiple partitions. See: https://learn.microsoft.com/en-us/azure/cosmos-db/nosql/change-feed-functions. D is also correct as it is described here: https://learn.microsoft.com/en-us/azure/cosmos-db/nosql/read-change-feed

FeriAZOptions: CD

C. Azure Function with Cosmos DB Trigger Azure Functions can be triggered by changes in Cosmos DB, allowing for immediate processing of inserts and updates. D. Azure Function with FeedIterator and FeedRange for Change Feed This method manually handles the change feed processing, allowing for detailed control over parallelization and processing logic.

manopeydakonOptions: BD

Both options B and D can be used to process Azure Cosmos DB operations efficiently: B. Create a background job in an Azure Kubernetes Service and implement the change feed feature of the SDK.This option involves creating a background job using Azure Kubernetes Service (AKS) and implementing the change feed feature of the Azure Cosmos DB SDK. AKS provides scalability, and you can parallelize the processing by distributing work across multiple pods in the AKS cluster.D. Create an Azure Function that uses a FeedIterator object that processes the change feed by using the pull model on the container. Use a FeedRange object to parallelize the processing of the change feed across multiple functions. This option involves using Azure Functions with the change feed trigger for Azure Cosmos DB. By using the FeedIterator and FeedRange objects, you can parallelize the processing of the change feed across multiple Azure Functions.

lednariOptions: BC

B and C for me. AKS containers can scale and job just runs in background. Funcs can scale and trigger on cosmos. A is an api so whats it triggering on? D also doesnt mention what it would trigger on

DianahuOptions: CD

isn't the change feed estimator only for monitoring? it is the change feed processor who does the work https://learn.microsoft.com/en-us/azure/cosmos-db/nosql/how-to-use-change-feed-estimator?tabs=dotnet so it is C&D

mabdo

similar was on 2/23

alexein74Options: CD

I agree with Zulhin.

ldenouterOptions: CD

I agree with Zulhin.

rotimislawOptions: AC

A & C - simplicity is your best friend

AB1453Options: AC

A and C