Salesforce Certified MuleSoft Platform Architect (Mule-Arch-201) Exam - Topic 7 Question 21 Discussion

Actual exam question for Salesforce's Salesforce Certified MuleSoft Platform Architect (Mule-Arch-201) exam

Question #: 21
Topic #: 7

[All Salesforce Certified MuleSoft Platform Architect (Mule-Arch-201) 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?

AThe update should be identified as a project risk and full regression testing of the functionality that uses this API should be run

BThe API producer should be contacted to understand the change to existing functionality

CThe API producer should be requested to run the old version in parallel with the new one

DThe API client code ONLY needs to be changed if it needs to take advantage of new features

Show Suggested Answer

Suggested Answer: D

by Heike at Nov 15, 2024, 12:00 PM

Limited Time Offer

25%

Off

Get Premium Salesforce Certified MuleSoft Platform Architect (Mule-Arch-201) Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

Submit Cancel

Desirae

3 months ago

Only changing code for new features seems risky to me.

upvoted 0 times

...

Leota

3 months ago

Wait, are we sure there are no hidden issues with the new version?

upvoted 0 times

...

Emilio

3 months ago

I agree, if the endpoint didn't change, we should be fine.

upvoted 0 times

...

Kallie

4 months ago

I think contacting the API producer is a bit overkill for a minor version change.

upvoted 0 times

...

Lucille

4 months ago

Sounds like a solid update, but always better to test thoroughly.

upvoted 0 times

...

Lera

4 months 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.

upvoted 0 times

...

Gwenn

4 months 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.

upvoted 0 times

...

Dana

4 months 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.

upvoted 0 times

...

Lashawnda

5 months 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.

upvoted 0 times

...

Yan

5 months 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.

upvoted 0 times

...

Lynda

5 months 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.

upvoted 0 times

...

Mitsue

5 months 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.

upvoted 0 times

...

Elbert

5 months 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.

upvoted 0 times

...

Teri

1 year 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

1 year ago

D) The API client code ONLY needs to be changed if it needs to take advantage of new features

upvoted 0 times

...

Albina

1 year ago

D) The API client code ONLY needs to be changed if it needs to take advantage of new features

upvoted 0 times

...

Zona

1 year ago

B) The API producer should be contacted to understand the change to existing functionality

upvoted 0 times

...

Terrilyn

1 year 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

1 year ago

B) The API producer should be contacted to understand the change to existing functionality

upvoted 0 times

...

Stanford

1 year 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

1 year 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

1 year 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

1 year ago

Definitely, better safe than sorry when it comes to updating API client code.

upvoted 0 times

...

Patti

1 year ago

Agreed, contacting the API producer is a good idea before making any updates.

upvoted 0 times

...

Dallas

1 year ago

Option B sounds like the best call. Understanding the changes is key.

upvoted 0 times

...

Detra

1 year ago

But what if the client code doesn't need to be changed?

upvoted 0 times

...

Justine

1 year ago

I agree with Lang, it's important to identify any project risks.

upvoted 0 times

...

Ariel

1 year 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