New Year Sale 2026! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions
Mail Us support@pass4success.com
Location US
Mob_nav_barsMENU

Salesforce Certified MuleSoft Platform Architect (Mule-Arch-201) Exam - Topic 8 Question 22 Discussion

Actual exam question for Salesforce's Salesforce Certified MuleSoft Platform Architect (Mule-Arch-201) exam
Question #: 22
Topic #: 8
[All Salesforce Certified MuleSoft Platform Architect (Mule-Arch-201) Questions]

An existing Quoting API is defined in RAML and used by REST clients for interacting with the quoting engine. Currently there is a resource defined in the RAML that allows the creation of quotes; however, a new requirement was just received to allow for the updating of existing quotes.

Which two actions need to be taken to facilitate this change so it can be processed?

Choose 2 answers

Show Suggested Answer Hide Answer
Suggested Answer: A, C

To accommodate the new requirement of allowing updates to existing quotes, the following actions should be taken:

Update the RAML Definition (Option C):

The RAML specification defines the structure and behavior of the API. Adding a new method (such as PUT or PATCH) for updating quotes requires modifying the RAML to include this new endpoint. This ensures the API specification is up-to-date and accurately reflects the new functionality.

Update the API Implementation (Option A):

Once the RAML is updated, the backend API implementation must also be modified to handle the new update requests. This could involve adding logic to process and validate update requests, connect to necessary backend resources, and apply the changes to existing quotes.

of Incorrect Options:

Option B (removing and creating new clients) is unnecessary; client applications can remain as they are, with no need for complete replacement.

Option D (deprecating existing versions) may not be required if backward compatibility is maintained.

Option E (adding a new policy) does not facilitate functional changes and is unrelated to implementing the update feature.

Reference For more details on updating RAML definitions and API implementations, refer to MuleSoft's API Design documentation on RAML and RESTful API practices.


by Renay at Dec 09, 2024, 08:27 AM

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:

0/2000 characters
Submit Cancel
Holley
3 months ago
Adding a new API policy could help, but is it really required?
upvoted 0 times
...
Lizbeth
3 months ago
Wait, do we really need to deprecate existing versions? That sounds risky.
upvoted 0 times
...
Wilda
3 months ago
Removing old client apps seems unnecessary. Why not just update them?
upvoted 0 times
...
Gerald
4 months ago
Agree, updating the API implementation is a must too!
upvoted 0 times
...
Andra
4 months ago
Definitely need to update the RAML with new method details for the update request.
upvoted 0 times
...
King
4 months ago
Adding a new API policy sounds relevant, but I feel like updating the RAML is more critical for this change.
upvoted 0 times
...
Graham
4 months ago
I’m a bit confused about whether we need to remove old client applications. That seems excessive just for an update.
upvoted 0 times
...
Izetta
4 months ago
I remember we practiced a similar question where we had to update an API. Updating the API implementation seems like a must-do step.
upvoted 0 times
...
Jacqueline
5 months ago
I think we definitely need to update the RAML with the new method details for the update request, but I'm not sure about the other option.
upvoted 0 times
...
Shasta
5 months ago
Adding a new API policy to API Manager is a good idea to control access to the updated endpoint. That way we can manage the changes more effectively.
upvoted 0 times
...
Aide
5 months ago
Deprecating existing versions of the API in Exchange seems like an unnecessary step. We should be able to make the changes without impacting the current version.
upvoted 0 times
...
Craig
5 months ago
I think the key here is to focus on the RAML and API implementation changes. The client applications should be able to handle the new update functionality without needing to be completely replaced.
upvoted 0 times
...
Felice
5 months ago
Hmm, I'm a bit unsure about the client application piece. Do we really need to remove the old ones and create new ones? That seems like a lot of extra work.
upvoted 0 times
...
Eden
5 months ago
This seems straightforward. I'd start by updating the RAML to include the new update method, then make the corresponding changes to the API implementation.
upvoted 0 times
...
Pilar
1 year ago
Are you kidding me? Deprecating the existing API version? That's like trying to force everyone to use your new smartphone by shutting down the old landlines. C and A are the way to go, my dudes.
upvoted 0 times
Tran
1 year ago
A) Update the API implementation to accommodate the new update request
upvoted 0 times
...
Lawanda
1 year ago
C) Update the RAML with new method details for the update request
upvoted 0 times
...
...
Mitsue
1 year ago
I'm going with C and A. Updating the RAML and the API implementation are essential steps. The other options just sound like overkill or busywork.
upvoted 0 times
Mila
1 year ago
Updating the RAML with new method details and accommodating the new update request in the API implementation are the most important steps.
upvoted 0 times
...
Tammara
1 year ago
Adding a new API policy could be helpful, but not as essential as updating the RAML and API implementation.
upvoted 0 times
...
Remedios
1 year ago
Removing old client applications and deprecating existing versions seem unnecessary for this change.
upvoted 0 times
...
Ocie
1 year ago
I agree, updating the RAML and API implementation are the key actions needed.
upvoted 0 times
...
...
Erick
1 year ago
Hah, imagine if we had to remove all the existing client apps just to add a new endpoint. That would be like nuking the whole city to get rid of a mouse. C and A are clearly the way to go.
upvoted 0 times
Kirby
1 year ago
Agreed, C and A are definitely the best actions to take in this situation.
upvoted 0 times
...
Cornell
1 year ago
Yeah, removing all client apps would be overkill. Updating the RAML and API implementation is the way to go.
upvoted 0 times
...
...
Magnolia
1 year ago
I don't think we need to remove old client applications. We can just update them to account for the changes.
upvoted 0 times
...
Gerry
1 year ago
Should we deprecate existing versions of the API in Exchange as well?
upvoted 0 times
...
Rosendo
1 year ago
I agree with Tarra. We also need to update the RAML with new method details.
upvoted 0 times
...
Essie
1 year ago
Hmm, I think C and A are the right answers here. You can't just update the API without also updating the RAML to reflect the changes. And adding a new policy in the API Manager seems unnecessary.
upvoted 0 times
...
Carylon
1 year ago
Obviously, we need to update the RAML and the API implementation to handle the new update request. I'm not sure why we would need to remove old client apps or deprecate the existing API version.
upvoted 0 times
Dianne
1 year ago
C) Update the RAML with new method details for the update request
upvoted 0 times
...
Ty
1 year ago
A) Update the API implementation to accommodate the new update request
upvoted 0 times
...
...
Tarra
1 year ago
I think we need to update the API implementation for the new update request.
upvoted 0 times
...

Save Cancel