Alibaba Exam ACA-CloudNative Topic 5 Question 103 Discussion

Actual exam question for Alibaba's ACA-CloudNative exam

Question #: 103
Topic #: 5

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

AUse PL/SQL Statement from RDBMS

BDatabase lock required (commit and rollback scenario)

CUse store procedure/function from RDBMS

DUse 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.

Show Suggested Answer

Suggested Answer: A

by Marleen at Nov 14, 2024, 10:31 PM

Limited Time Offer

25%

Off

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

Contribute your Thoughts:

Submit Cancel

Janine

1 months ago

If Option D doesn't work, I guess we could always try Option E: Throw the whole thing out and go back to monoliths. Just kidding, but seriously, D is the way to go.

upvoted 0 times

Celeste

4 days ago

C) Use store procedure/function from RDBMS

upvoted 0 times

...

Phyliss

16 days ago

B) Database lock required (commit and rollback scenario)

upvoted 0 times

...

Phil

23 days ago

A) Use PL/SQL Statement from RDBMS

upvoted 0 times

...

Scarlet

2 months ago

D is the clear winner here. Who wants to deal with manual database locks and rollbacks when you can auMyate the whole process? Sign me up for the Choreographer and Event Bus!

upvoted 0 times

Keneth

8 days ago

Database lock required seems like a hassle. D is definitely the more efficient choice.

upvoted 0 times

...

Kris

9 days ago

I prefer the Choreographer and Event Bus as well. It simplifies the process and reduces the chances of errors.

upvoted 0 times

...

Alpha

14 days ago

I think using store procedure/function from RDBMS could also be a good option for data consistency.

upvoted 0 times

...

Chana

1 months ago

I agree, D is definitely the way to go. Automation is key in microservices architecture.

upvoted 0 times

...

Hmm, I was leaning towards C until I read the details on D. Encapsulating the failure handling in a Choreographer is a much cleaner solution than trying to coordinate it across the individual services.

upvoted 0 times

...

Eugene

2 months ago

I'm not sure about the other options, but D definitely sounds like the most comprehensive approach. Handling failures across multiple services can be tricky, so having a centralized way to manage that is key.

upvoted 0 times

Gail

1 months ago

I think so too. It provides a centralized way to handle failures and maintain consistency across services.

upvoted 0 times

...

Claribel

1 months ago

I agree, using a Choreographer and Event Bus seems like the best way to ensure data consistency in microservices architecture.

upvoted 0 times

...

Elouise

2 months ago

Option D seems like the way to go. Using a Choreographer and Event Bus to handle failed scenarios seems like a robust and flexible solution for maintaining data consistency in a microservices architecture.

upvoted 0 times

...