MENU
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?
Suggested Answer: D
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
37 comments · newest first
DE
Desirae
11 months ago
Only changing code for new features seems risky to me.
LE
Leota
11 months ago
Wait, are we sure there are no hidden issues with the new version?
EM
Emilio
12 months ago
I agree, if the endpoint didn't change, we should be fine.
KA
Kallie
12 months ago
I think contacting the API producer is a bit overkill for a minor version change.
LU
Lucille
1 year ago
Sounds like a solid update, but always better to test thoroughly.
LE
Lera
1 year ago
I vaguely recall that running the old version in parallel could be a good fallback, but I don't think that's a common practice. It seems like a lot of extra work.
GW
Gwenn
1 year ago
I feel like option D could be valid too, but what if there are hidden issues in the new version? I’m a bit uncertain about just relying on that.
DA
Dana
1 year ago
I think option B makes sense because understanding the changes could help us assess the impact on our current implementation. We practiced a similar question about API updates last week.
LA
Lashawnda
1 year ago
I remember we discussed how semantic versioning indicates that there might be breaking changes, but since the endpoint hasn't changed, I'm not sure if we need full regression testing.
YA
Yan
1 year ago
This seems straightforward. As long as the endpoint didn't change, I just need to make sure my client code is compatible with the new version.
LY
Lynda
1 year ago
Okay, let's think this through step-by-step. I need to check the API documentation, understand the changes, and determine the appropriate response.
MI
Mitsue
1 year ago
Hmm, I'm a bit unsure about this one. I'll need to review the details on semantic versioning and how that affects API changes.
EL
Elbert
1 year ago
I'm pretty confident I know how to handle this. The key is to understand the semantic versioning changes and how they impact the client code.
TE
Teri
2 years ago
What, no option for 'duct tape and hope for the best'? That's my go-to solution for API changes!
BA
Barney
2 years ago
D) The API client code ONLY needs to be changed if it needs to take advantage of new features
AL
Albina
2 years ago
D) The API client code ONLY needs to be changed if it needs to take advantage of new features
ZO
Zona
2 years ago
B) The API producer should be contacted to understand the change to existing functionality
TE
Terrilyn
2 years 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
JE
Jennie
2 years ago
B) The API producer should be contacted to understand the change to existing functionality
ST
Stanford
2 years 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
JA
Janna
2 years 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?
GA
Gail
2 years 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!
GR
Gracia
2 years ago
Definitely, better safe than sorry when it comes to updating API client code.
PA
Patti
2 years ago
Agreed, contacting the API producer is a good idea before making any updates.
DA
Dallas
2 years ago
Option B sounds like the best call. Understanding the changes is key.
DE
Detra
2 years ago
But what if the client code doesn't need to be changed?
JU
Justine
2 years ago
I agree with Lang, it's important to identify any project risks.
AR
Ariel
2 years 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.
AM
Amos
2 years ago
It's good practice to stay informed about updates to APIs.
LI
Linn
2 years ago
I always check the release notes first before making any changes.
MA
Malcom
2 years ago
No need for full regression testing if the endpoint remains the same.
CO
Colton
2 years ago
Yeah, I think just updating the code for new features is the way to go.
LA
Lamonica
2 years ago
We can always reach out to the API producer if we have any questions about the update.
TR
Tran
2 years ago
I agree, option D seems like the most efficient choice.
MY
Myra
2 years ago
I agree, let's focus on updating our code to take advantage of any new features.
KI
King
2 years ago
The release notes should have all the information we need.
LA
Lang
2 years ago
I think the developer should do full regression testing.