Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions
Mail Us support@pass4success.com
Location US
Mob_nav_barsMENU

Alibaba ACA-CloudNative Exam - Topic 2 Question 124 Discussion

How to keep the data consistency in microservices architecture refer to microservice.io?
D) Use a Choreographer and Event Bus. In the failed scenario in a service, a Choreographer will use event bus to cancel all the communications among services related.
A) Use PL/SQL Statement from RDBMS
B) Database lock required (commit and rollback scenario)
C) Use store procedure/function from RDBMS

Alibaba ACA-CloudNative Exam - Topic 2 Question 124 Discussion

Actual exam question for Alibaba's ACA-CloudNative exam
Question #: 124
Topic #: 2
[All ACA-CloudNative Questions]

How to keep the data consistency in microservices architecture refer to microservice.io?

Show Suggested Answer Hide Answer
Suggested Answer: D

by Melina at Apr 13, 2026, 04:27 AM

Limited Time Offer

25%

Off

Get Premium ACA-CloudNative Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

0/2000 characters
Submit Cancel
Coral
5 days ago
D ensures better communication and consistency.
upvoted 0 times
...
Abel
10 days ago
B could lead to bottlenecks. Locks aren't ideal.
upvoted 0 times
...
Xenia
15 days ago
A and C seem outdated. We need modern solutions.
upvoted 0 times
...
Brandee
20 days ago
I agree, D is more flexible for microservices.
upvoted 0 times
...
Keshia
25 days ago
I think option D is the best. Choreography helps manage failures.
upvoted 0 times
...
Sherron
1 month ago
Totally agree with D, event-driven is the future!
upvoted 0 times
...
Marilynn
1 month ago
Wait, can a Choreographer really handle all that? Sounds risky!
upvoted 0 times
...
Gerri
1 month ago
I think B can lead to bottlenecks.
upvoted 0 times
...
Catherin
2 months ago
A and C are outdated methods, though.
upvoted 0 times
...
Jessenia
2 months ago
D is the way to go for microservices!
upvoted 0 times
...
Fletcher
2 months ago
Totally agree with D, it’s more scalable!
upvoted 0 times
...
Dick
2 months ago
Wait, can a Choreographer really handle all that?
upvoted 0 times
...
Filiberto
2 months ago
I think B could lead to bottlenecks.
upvoted 0 times
...
Fausto
4 months ago
A and C are outdated methods for this.
upvoted 0 times
...
Celeste
4 months ago
D is the best approach for microservices!
upvoted 0 times
...
Maia
4 months ago
I recall that using PL/SQL or stored procedures might not align with microservices principles, but I can't remember the exact reasons.
upvoted 0 times
...
Zana
5 months ago
I’m a bit confused about the database lock scenario. I feel like it could lead to bottlenecks in a microservices setup.
upvoted 0 times
...
Alesia
5 months ago
I think option D sounds familiar; we practiced a similar question about event-driven architecture and how it helps maintain data consistency.
upvoted 0 times
...
Fredric
5 months ago
I remember we discussed the importance of eventual consistency in microservices, but I'm not sure if using a Choreographer is the best approach.
upvoted 0 times
...

Save Cancel