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

Salesforce Exam MuleSoft Platform Architect I Topic 7 Question 21 Discussion

Actual exam question for Salesforce's MuleSoft Platform Architect I exam
Question #: 21
Topic #: 7
[All MuleSoft Platform Architect I Questions]

An API has been updated in Anypoint Exchange by its API producer from version 3.1.1 to 3.2.0 following accepted semantic versioning practices and the changes have been communicated via the API's public portal.

The API endpoint does NOT change in the new version.

How should the developer of an API client respond to this change?

Show Suggested Answer Hide Answer
Suggested Answer: D

Contribute your Thoughts:

Teri
1 months ago
What, no option for 'duct tape and hope for the best'? That's my go-to solution for API changes!
upvoted 0 times
Barney
10 days ago
D) The API client code ONLY needs to be changed if it needs to take advantage of new features
upvoted 0 times
...
Albina
15 days ago
D) The API client code ONLY needs to be changed if it needs to take advantage of new features
upvoted 0 times
...
Zona
18 days ago
B) The API producer should be contacted to understand the change to existing functionality
upvoted 0 times
...
Terrilyn
20 days ago
A) The update should be identified as a project risk and full regression testing of the functionality that uses this API should be run
upvoted 0 times
...
Jennie
29 days ago
B) The API producer should be contacted to understand the change to existing functionality
upvoted 0 times
...
Stanford
30 days ago
A) The update should be identified as a project risk and full regression testing of the functionality that uses this API should be run
upvoted 0 times
...
...
Janna
2 months ago
I'm with Gail on this one. Better play it safe and get the details from the API producer. Can't be too careful, you know?
upvoted 0 times
...
Gail
2 months ago
Option B sounds like the best call to me. Gotta understand those changes before making any updates to the client code. Don't want to break anything!
upvoted 0 times
Gracia
28 days ago
Definitely, better safe than sorry when it comes to updating API client code.
upvoted 0 times
...
Patti
1 months ago
Agreed, contacting the API producer is a good idea before making any updates.
upvoted 0 times
...
Dallas
1 months ago
Option B sounds like the best call. Understanding the changes is key.
upvoted 0 times
...
...
Detra
2 months ago
But what if the client code doesn't need to be changed?
upvoted 0 times
...
Justine
2 months ago
I agree with Lang, it's important to identify any project risks.
upvoted 0 times
...
Ariel
2 months ago
Hmm, I think option D is the way to go. No need to run a full regression test if the endpoint didn't change, right? I'll just check the release notes and see if there's anything I need to update.
upvoted 0 times
Amos
25 days ago
It's good practice to stay informed about updates to APIs.
upvoted 0 times
...
Linn
28 days ago
I always check the release notes first before making any changes.
upvoted 0 times
...
Malcom
1 months ago
No need for full regression testing if the endpoint remains the same.
upvoted 0 times
...
Colton
1 months ago
Yeah, I think just updating the code for new features is the way to go.
upvoted 0 times
...
Lamonica
2 months ago
We can always reach out to the API producer if we have any questions about the update.
upvoted 0 times
...
Tran
2 months ago
I agree, option D seems like the most efficient choice.
upvoted 0 times
...
Myra
2 months ago
I agree, let's focus on updating our code to take advantage of any new features.
upvoted 0 times
...
King
2 months ago
The release notes should have all the information we need.
upvoted 0 times
...
...
Lang
2 months ago
I think the developer should do full regression testing.
upvoted 0 times
...

Save Cancel