exam questions

Exam AZ-204 All Questions

View all questions & answers for the AZ-204 exam

Exam AZ-204 topic 3 question 25 discussion

Actual exam question from Microsoft's AZ-204
Question #: 25
Topic #: 3
[All AZ-204 Questions]

DRAG DROP -
You are implementing an Azure solution that uses Azure Cosmos DB and the latest Azure Cosmos DB SDK. You add a change feed processor to a new container instance.
You attempt to read a batch of 100 documents. The process fails when reading one of the documents. The solution must monitor the progress of the change feed processor instance on the new container as the change feed is read. You must prevent the change feed processor from retrying the entire batch when one document cannot be read.
You need to implement the change feed processor to read the documents.
Which features should you use? To answer, drag the appropriate features to the cored requirements. Each feature may be used once, more than once, or not at all. You may need to drag the split bar between panes or scroll to view content.
NOTE: Each cored selection is worth one point.
Select and Place:

Show Suggested Answer Hide Answer
Suggested Answer:
Box 1: Change feed estimator -
You can use the change feed estimator to monitor the progress of your change feed processor instances as they read the change feed or use the life cycle notifications to detect underlying failures.

Box 2: Dead-letter queue -
To prevent your change feed processor from getting "stuck" continuously retrying the same batch of changes, you should add logic in your delegate code to write documents, upon exception, to a dead-letter queue. This design ensures that you can keep track of unprocessed changes while still being able to continue to process future changes. The dead-letter queue might be another Cosmos container. The exact data store does not matter, simply that the unprocessed changes are persisted.
Reference:
https://docs.microsoft.com/en-us/azure/cosmos-db/sql/change-feed-processor

Comments

Chosen Answer:
This is a voting comment (?). It is better to Upvote an existing comment if you don't have anything to add.
Switch to a voting comment New
finnishr
Highly Voted 2 years, 3 months ago
The answer is correct.
upvoted 16 times
ns4098
3 months ago
1. Monitor the progress of the change feed processor Feature: Lease container Reason: The Lease container is responsible for tracking the progress of the change feed processor. It maintains state information, ensuring that the change feed processor knows where it left off and can resume from the correct point in the feed. This allows the system to monitor the progress and distribute the workload across multiple instances if needed. 2. Prevent the change feed processor from retrying the entire batch when one document cannot be read Feature: Dead-letter queue Reason: The Dead-letter queue allows you to handle documents that cannot be processed. If a document cannot be read or processed, instead of failing the entire batch, the problematic document is moved to a dead-letter queue, allowing the change feed processor to continue processing the rest of the batch without retrying the failed document.
upvoted 1 times
...
...
sarmaria
Highly Voted 1 year, 9 months ago
Got this on 16/03/23. Went with proposed solution. Make sure to prepare for case study. I got city and lights case study. No Kubernetes, Search, Logic Apps questions for me.
upvoted 13 times
...
Stann07
Most Recent 1 year ago
On my exam Dec 18. went with the given answer. scored 842
upvoted 3 times
...
AndySmith
1 year, 1 month ago
On exam 3-Nov-2023. Went with proposed anwer - 932/1000. 1) Change feed estimator 2) Dead letter queue
upvoted 4 times
...
dddddd111
1 year, 3 months ago
I got this same question. Provided answers are correct. (Note: I failed the exam 20/9/23. I only scored 644 and I felt bad. I think because many questions here in Examtopics are not accurate. I suggest following the most voted answers and don't just not rely on Examtopics answers. At the beginning of the exam, you will be asked which programming languages you want to use. C#/Python. I chose C#. Also, I just want to add that some questions here are really in the actual exams, but the choices are written and formatted differently. Please be aware of that. Goodluck. I feel bad for failing it, but I want to retake next month. I will try Python. T_T
upvoted 10 times
Nitin23
1 year, 3 months ago
this is a bad site
upvoted 2 times
...
...
kayvg
1 year, 4 months ago
The answer is correct A change feed estimator is used to monitor teh progress of your change feed processor instances as they read the change feed A dead-letter queue is holding a queue for messages that cannot bbe delivered to their destination A deployment unit is to provide a container for an application or service, which is not relevant The lease container is used to coordinate processing the change feed, which is not relevant aswell
upvoted 1 times
...
kvtborad
1 year, 4 months ago
I got this question on 6th August 2023. chose highly voted. passed with 904. I got Case study: city and Lights. All questions are from ExamTopics.
upvoted 2 times
...
JH81
1 year, 6 months ago
Got this on 6/28/2023 and passed with 850. Went with answer.
upvoted 2 times
...
aragones
1 year, 7 months ago
Got this 2023-05-12. My case: case: You need to configure authorization. case: You need to ensure the app does not time out and processes the blob data case study: VanArsdel Inc Canada
upvoted 1 times
...
narenazure
1 year, 11 months ago
The answer is correct. To prevent your change feed processor from getting "stuck" continuously retrying the same batch of changes, you should add logic in your delegate code to write documents, upon exception, to an errored-message queue. This design ensures that you can keep track of unprocessed changes while still being able to continue to process future changes. The errored-message queue might be another Azure Cosmos DB container. The exact data store does not matter, simply that the unprocessed changes are persisted. Error handling section - https://learn.microsoft.com/en-us/azure/cosmos-db/nosql/change-feed-processor?tabs=dotnet
upvoted 1 times
...
Esward
1 year, 11 months ago
Given answers are correct!
upvoted 1 times
Esward
1 year, 11 months ago
To prevent your change feed processor from getting "stuck" continuously retrying the same batch of changes, you should add logic in your delegate code to write documents, upon exception, to an errored-message queue. This design ensures that you can keep track of unprocessed changes while still being able to continue to process future changes. The errored-message queue might be another Azure Cosmos DB container. The exact data store does not matter, simply that the unprocessed changes are persisted. In addition, you can use the change feed estimator to monitor the progress of your change feed processor instances as they read the change feed or use the life cycle notifications to detect underlying failures.
upvoted 2 times
...
...
Sreedharc
2 years, 1 month ago
got in 11/11/2022
upvoted 3 times
...
vcfvct
2 years, 2 months ago
Got this on 10/21/2022
upvoted 3 times
OPT_001122
2 years, 1 month ago
thanks for mentioning the date
upvoted 1 times
...
...
gmishra88
2 years, 2 months ago
Sure, this is also taken from a certification. But where does a dead letter queue come in change feed processor. If this comes, yes, this is the correct answer. But it all doesn't make any sense
upvoted 1 times
coffecold
2 years, 2 months ago
It is do-it-your self stuff: "To prevent your change feed processor from getting "stuck" continuously retrying the same batch of changes, you should add logic in your delegate code to write documents, upon exception, to a dead-letter queue " https://learn.microsoft.com/en-us/azure/cosmos-db/sql/change-feed-processor?tabs=dotnet
upvoted 3 times
Pentagon
2 years, 1 month ago
If just for saving the last position, I think it should be lease container. "When the delegate finishes processing the changes successfully, update the lease store with the latest processed point in time and go to #1" Dead-letter queue seems to be prevent re-trying too much instead of resuming at the last done position.
upvoted 1 times
...
...
...
Community vote distribution
A (35%)
C (25%)
B (20%)
Other
Most Voted
A voting comment increases the vote count for the chosen answer by one.

Upvoting a comment with a selected answer will also increase the vote count towards that answer by one. So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.

SaveCancel
Loading ...
exam
Someone Bought Contributor Access for:
SY0-701
London, 1 minute ago