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 8 Question 11 Discussion

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

An API implementation is updated. When must the RAML definition of the API also be updated?

Show Suggested Answer Hide Answer
Suggested Answer: A

Correct Answer : When the API implementation changes the structure of the request or response messages

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

>> RAML definition usually needs to be touched only when there are changes in the request/response schemas or in any traits on API.

>> It need not be modified for any internal changes in API implementation like performance tuning, backend system migrations etc..


Contribute your Thoughts:

Tawny
4 months ago
Haha, I bet the developer who had to optimize the API for better response time was pulling their hair out. Option D is a bit overkill for the RAML update.
upvoted 0 times
Karl
2 months ago
Cheryl: It's important to update the RAML when the structure of request or response messages changes though.
upvoted 0 times
...
Marci
3 months ago
I agree, option D seems like overkill for just improving response time.
upvoted 0 times
...
Cheryl
3 months ago
Definitely! I think updating the RAML definition for that might be a bit much though.
upvoted 0 times
...
Providencia
3 months ago
Definitely, but I think updating the RAML only when the structure changes makes more sense.
upvoted 0 times
...
Callie
3 months ago
Yeah, optimizing for response time can be a real headache.
upvoted 0 times
...
Dorian
3 months ago
Yeah, optimizing the API for better response time can be a real challenge.
upvoted 0 times
...
...
Rima
4 months ago
I think both A and B are valid reasons to update the RAML definition, depending on the specific changes made to the API implementation
upvoted 0 times
...
Ludivina
4 months ago
Option B also makes sense. Changing the backend system is a significant change that should be reflected in the RAML definition.
upvoted 0 times
...
Gracia
4 months ago
B) When the API implementation changes from interacting with a legacy backend system deployed on-premises to a modern, cloud-based (SaaS) system
upvoted 0 times
...
Jaclyn
4 months ago
I agree with option A. Updating the RAML ensures that the API documentation accurately reflects the changes in the implementation.
upvoted 0 times
Twila
3 months ago
That would be a good time to update the RAML as well, to reflect the new system.
upvoted 0 times
...
Stephen
3 months ago
What about when the API implementation changes from interacting with a legacy system to a cloud-based one?
upvoted 0 times
...
Claudio
4 months ago
Yes, that way the API documentation stays accurate.
upvoted 0 times
...
Melodie
4 months ago
I think the RAML should be updated when the API implementation changes the structure of the request or response messages.
upvoted 0 times
...
...
Chauncey
5 months ago
The RAML definition should be updated when the API implementation changes the structure of the request or response messages (option A). Keeping the RAML in sync is crucial for maintaining contract compatibility.
upvoted 0 times
Giuseppe
4 months ago
Agreed, keeping the RAML definition in sync with the API implementation is key for ensuring compatibility.
upvoted 0 times
...
Giuseppe
5 months ago
Yes, you're right. It's important to update the RAML when the structure of the messages changes.
upvoted 0 times
...
...
Josefa
5 months ago
I agree with Cammy, the RAML definition should be updated to reflect the changes in the API implementation
upvoted 0 times
...
Cammy
5 months ago
A) When the API implementation changes the structure of the request or response messages
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