Cyber Monday 2024! 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 6 Question 10 Discussion

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

An API client calls one method from an existing API implementation. The API implementation is later updated. What change to the API implementation would require the API client's invocation logic to also be updated?

Show Suggested Answer Hide Answer
Suggested Answer: C

Correct Answer : When a new required field is added to the method called by the API client

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

>> Generally, the logic on API clients need to be updated when the API contract breaks.

>> When a new method or a child method is added to an API , the API client does not break as it can still continue to use its existing method. So these two options are out.

>> We are left for two more where 'datatype of the response if changed' and 'a new required field is added'.

>> Changing the datatype of the response does break the API contract. However, the question is insisting on the 'invocation' logic and not about the response handling logic. The API client can still invoke the API successfully and receive the response but the response will have a different datatype for some field.

>> Adding a new required field will break the API's invocation contract. When adding a new required field, the API contract breaks the RAML or API spec agreement that the API client/API consumer and API provider has between them. So this requires the API client invocation logic to also be updated.


Contribute your Thoughts:

Alise
4 months ago
Haha, oh boy. This is like a game of API roulette. I'm just going to go with C and hope I don't get fired for it.
upvoted 0 times
...
Stevie
4 months ago
Option D is the way to go, clearly. Adding a child method is the most logical choice here. What could possibly go wrong?
upvoted 0 times
...
Elli
4 months ago
Hmm, this is a tricky one. I'm torn between B and C, but I think C is the safest bet. Who knows what kind of weird API implementations are out there?
upvoted 0 times
Glory
3 months ago
Yeah, it's better to be safe and update the invocation logic just in case.
upvoted 0 times
...
Weldon
3 months ago
I agree, adding a new required field to the method called by the API client would definitely require an update.
upvoted 0 times
...
...
Odette
5 months ago
I agree with Annelle. Adding a required field is the only change that would force the client to update their invocation logic. The other options are just enhancements that the client can ignore.
upvoted 0 times
Rosamond
3 months ago
So, it's important for the client to stay updated with any required field changes in the API implementation.
upvoted 0 times
...
Precious
3 months ago
Yeah, the other options are just enhancements that the client can choose to ignore.
upvoted 0 times
...
Carli
3 months ago
I agree, that's the only change that would require the client to update their invocation logic.
upvoted 0 times
...
Pearline
4 months ago
I think the answer is C) When a new required field is added to the method called by the API client.
upvoted 0 times
...
...
Erick
5 months ago
I think the answer is B) When a new method is added to the resource used by the API client. That would definitely require updating the API client's invocation logic.
upvoted 0 times
...
Annelle
5 months ago
Option C is definitely the correct answer. Changing the data type or adding a new method wouldn't require the client to update their code, but adding a new required field would break the contract.
upvoted 0 times
Melda
4 months ago
Exactly, adding a new required field changes the contract between the API client and the implementation.
upvoted 0 times
...
Yvette
4 months ago
Yes, that's right. Changing the data type or adding a new method wouldn't necessarily break the client's code.
upvoted 0 times
...
Tamesha
4 months ago
Option C is definitely the correct answer. Changing the data type or adding a new method wouldn't require the client to update their code, but adding a new required field would break the contract.
upvoted 0 times
...
Lisha
4 months ago
D) When a child method is added to the method called by the API client
upvoted 0 times
...
Olene
4 months ago
C) When a new required field is added to the method called by the API client
upvoted 0 times
...
Julieta
4 months ago
B) When a new method is added to the resource used by the API client
upvoted 0 times
...
Gregg
4 months ago
I agree, option C is the correct answer. Adding a new required field would definitely require the client to update their code.
upvoted 0 times
...
Janine
4 months ago
A) When the data type of the response is changed for the method called by the API client
upvoted 0 times
...
...
Nicholle
5 months ago
I see your point, Margurite. But I think it could also be D) When a child method is added to the method called by the API client.
upvoted 0 times
...
Margurite
5 months ago
I disagree, I believe the correct answer is C) When a new required field is added to the method called by the API client.
upvoted 0 times
...
Julieta
5 months ago
I think the answer is A) When the data type of the response is changed for the method called by the API client.
upvoted 0 times
...

Save Cancel
az-700  pass4success  az-104  200-301  200-201  cissp  350-401  350-201  350-501  350-601  350-801  350-901  az-720  az-305  pl-300  

Warning: Cannot modify header information - headers already sent by (output started at /pass.php:70) in /pass.php on line 77