MENU
An API implementation is updated. When must the RAML definition of the API also be updated?
Suggested Answer: A
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
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..
36 comments · newest first
AN
Annice
11 months ago
A is the only clear trigger for an update, for sure!
DO
Dominga
11 months ago
C seems off, version changes shouldn't affect RAML, right?
DE
Detra
12 months ago
Wait, does B really require an update? Seems a bit much.
DA
Daniel
12 months ago
I agree with A, makes total sense!
RO
Rodolfo
1 year ago
Definitely A! Changes in request/response structure need updates.
ER
Ernestine
1 year ago
I think migrating to a newer version of the Mule runtime might not necessarily need a RAML update unless there are structural changes.
CO
Colby
1 year ago
I feel like optimizing for response time might not require a RAML update, but I'm a bit uncertain about that.
MA
Ma
1 year ago
I think we had a practice question about updating API definitions when switching backend systems. That seems relevant here, but I can't recall the specifics.
CO
Corinne
1 year ago
I remember we discussed that the RAML should definitely be updated when the request or response structure changes, but I'm not sure if that's the only time.
DO
Doyle
1 year ago
Wait, what's the difference between a legacy on-premises system and a modern cloud-based system? I'm a bit confused on how that would impact the RAML definition.
VA
Vanesa
1 year ago
Okay, let's see. The key is to focus on when the API implementation changes in a way that affects the request or response messages. I think I've got a good handle on this.
KI
Kizzy
1 year ago
Hmm, I'm not entirely sure about this one. I'll have to think it through carefully to make sure I understand the different scenarios.
WI
Wilburn
1 year ago
This seems like a straightforward question about when the RAML definition needs to be updated. I'm pretty confident I can figure this out.
TH
Thad
1 year ago
I remember learning about this in class. The RAML definition needs to be updated whenever the API implementation changes in a way that affects the contract, like the request or response structure. The other options seem more like implementation details.
LE
Leana
1 year ago
Ah, I remember learning about the Project Browser in class. I think the answer is D, but I'll double-check to be sure.
ER
Erinn
1 year ago
I remember the Jenson Measure calculations, but I'm a bit unsure of the specific rankings here.
TA
Tawny
2 years 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.
KA
Karl
2 years ago
Cheryl: It's important to update the RAML when the structure of request or response messages changes though.
MA
Marci
2 years ago
I agree, option D seems like overkill for just improving response time.
CH
Cheryl
2 years ago
Definitely! I think updating the RAML definition for that might be a bit much though.
PR
Providencia
2 years ago
Definitely, but I think updating the RAML only when the structure changes makes more sense.
CA
Callie
2 years ago
Yeah, optimizing for response time can be a real headache.
DO
Dorian
2 years ago
Yeah, optimizing the API for better response time can be a real challenge.
RI
Rima
2 years 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
LU
Ludivina
2 years ago
Option B also makes sense. Changing the backend system is a significant change that should be reflected in the RAML definition.
GR
Gracia
2 years ago
B) When the API implementation changes from interacting with a legacy backend system deployed on-premises to a modern, cloud-based (SaaS) system
JA
Jaclyn
2 years ago
I agree with option A. Updating the RAML ensures that the API documentation accurately reflects the changes in the implementation.
TW
Twila
2 years ago
That would be a good time to update the RAML as well, to reflect the new system.
ST
Stephen
2 years ago
What about when the API implementation changes from interacting with a legacy system to a cloud-based one?
CL
Claudio
2 years ago
Yes, that way the API documentation stays accurate.
ME
Melodie
2 years ago
I think the RAML should be updated when the API implementation changes the structure of the request or response messages.
CH
Chauncey
2 years 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.
GI
Giuseppe
2 years ago
Agreed, keeping the RAML definition in sync with the API implementation is key for ensuring compatibility.
GI
Giuseppe
2 years ago
Yes, you're right. It's important to update the RAML when the structure of the messages changes.
JO
Josefa
2 years ago
I agree with Cammy, the RAML definition should be updated to reflect the changes in the API implementation
CA
Cammy
2 years ago
A) When the API implementation changes the structure of the request or response messages