Discuss Salesforce Salesforce Certified MuleSoft Platform Architect (Mule-Arch-201) Exam Topic 6 Question 37

The implementation of a Process API must change.

What is a valid approach that minimizes the impact of this change on API clients?

AUpdate the RAML definition of the current Process API and notify API client developers by sending them links to the updated RAML definition

BPostpone changes until API consumers acknowledge they are ready to migrate to a new Process API or API version

CImplement required changes to the Process API implementation so that whenever possible, the Process API's RAML definition remains unchanged

DImplement the Process API changes in a new API implementation, and have the old API implementation return an HTTP status code 301 - Moved Permanently to inform API clients they should be calling the new API implementation

Suggested Answer: C

Correct Answe r: Implement required changes to the Process API implementation so that, whenever possible, the Process API's RAML definition remains unchanged.

*****************************************

Key requirement in the question is:

>> Approach that minimizes the impact of this change on API clients

Based on above:

>> Updating the RAML definition would possibly impact the API clients if the changes require any thing mandatory from client side. So, one should try to avoid doing that until really necessary.

>> Implementing the changes as a completely different API and then redirectly the clients with 3xx status code is really upsetting design and heavily impacts the API clients.

>> Organisations and IT cannot simply postpone the changes required until all API consumers acknowledge they are ready to migrate to a new Process API or API version. This is unrealistic and not possible.

The best way to handle the changes always is to implement required changes to the API implementations so that, whenever possible, the API's RAML definition remains unchanged.

Get Premium Salesforce Certified MuleSoft Platform Architect (Mule-Arch-201) Questions as Interactive Web-Based Practice Test or PDF Real Exam Format Detailed Explanations Instant Access Get Your Practice Test

30 comments · newest first

Leonor 6 months ago

True, but A relies on clients actually reading the updates.

Renea 7 months ago

D might confuse clients with the 301 status. Better to keep it simple.

Dean 7 months ago

But what about option D? It clearly directs clients to the new API.

Dominic 7 months ago

I agree, C minimizes disruption for clients.

Curt 7 months ago

Hmm, I’m not sure about B. Delaying changes could lead to bigger issues later on.

Shaun 7 months ago

Wait, isn't option D a bit risky? Clients might not notice the 301 redirect.

Ciara 8 months ago

Totally agree with C! It minimizes disruption for clients.

Jannette 8 months ago

Option A is just asking for trouble. Updating the RAML definition without notifying clients properly? Recipe for disaster.

Elenora 8 months ago

Haha, Option B? Really? Postponing changes until clients are ready? Good luck with that!

Martha 8 months ago

Option D is an interesting idea, but I'm not sure how well that would work in practice. Clients might get confused.

Brock 9 months ago

I agree, Option C is the best approach. Backwards compatibility is crucial for API versioning.

Lauran 9 months ago

I recall that postponing changes, like in option B, could lead to issues down the line. It might be better to implement changes sooner rather than later, but I’m not sure what the best approach is.

Ariel 9 months ago

I feel like option D could be a bit risky. Redirecting clients with a 301 status code might confuse some of them, especially if they aren't expecting it.

Reena 9 months ago

I'm not entirely sure, but I remember discussing the importance of communication with API clients. Maybe option A could work, but it might not be enough if clients don't update their implementations.

Lai 9 months ago

I think option C sounds familiar from our practice questions. Keeping the RAML definition unchanged seems like a good way to avoid breaking changes for clients.

Shaunna 9 months ago

I'm not sure about option B. Postponing changes until clients are ready to migrate could be risky and lead to more issues down the line.

Lindsey 10 months ago

I'm leaning towards option A. Updating the RAML definition and notifying clients seems like a straightforward way to handle the changes.

Kerry 10 months ago

Option D seems like a good idea too. Implementing the changes in a new API version and redirecting clients to the new version could work well.

Ben 10 months ago

I think option C is the best. Keeping the RAML unchanged is crucial.

Millie 10 months ago

Option C is the way to go. Minimizing changes to the RAML definition is key to keeping API clients happy.

Leonardo 10 months ago

I think option C is the best way to go. Keeping the RAML unchanged is key!

Minna 11 months ago

I prefer option A. Just updating the RAML and notifying clients seems straightforward.

Luke 11 months ago

Option A is also good. Notifying clients keeps them in the loop.

Tandra 11 months ago

I think option C is probably the way to go. Keeping the RAML definition the same as much as possible will minimize the impact on API clients and make the transition smoother.

Flo 11 months ago

I'm a bit confused by this question. It seems like there are a few different approaches we could take, but I'm not sure which one would be the best.

Cammy 6 months ago

↳ replying to Flo

It’s tricky. Balancing change and communication is key.

Lillian 6 months ago

↳ replying to Flo

True, but clients might not be ready. Option B could delay issues.

Winifred 6 months ago

↳ replying to Flo

What about option A? Notifying clients seems important.

Georgiann 6 months ago

↳ replying to Flo

I agree, but option D could work too. Redirects are helpful.

Phil 6 months ago

↳ replying to Flo

I think option C is the best. Keeping the RAML unchanged sounds smart.

Salesforce Certified MuleSoft Platform Architect (Mule-Arch-201) Exam - Topic 6 Question 37 Discussion