Deal of The Day! 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

MuleSoft Exam MCD-Level-2 Topic 1 Question 1 Discussion

Actual exam question for MuleSoft's MCD-Level-2 exam
Question #: 1
Topic #: 1
[All MCD-Level-2 Questions]

A developer has created the first version of an API designed for business partners to work commodity prices.

What should developer do to allow more than one major version of the same API to be exposed by the implementation?

Show Suggested Answer Hide Answer
Suggested Answer: C

To allow more than one major version of the same API to be exposed by the implementation, the developer should modify the baseUri property in the RAML file to include a variable that indicates the version number. The baseUri property defines the base URL of the API and can include variables that are replaced with actual values when mocking or deploying the API. By using a variable for the version number, the developer can expose different versions of the API using different base URLs and avoid conflicts or confusion. Reference: https://docs.mulesoft.com/api-designer/design-modify-raml-specs#baseuri https://docs.mulesoft.com/api-manager/2.x/api-versioning


by Junita at Apr 08, 2024, 11:31 PM

Limited Time Offer

25%

Off

Get Premium MCD-Level-2 Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

Submit Cancel
Alesia
9 months ago
I see your point Tawna, but I still think modifying flow names is the most flexible approach for handling different API versions.
upvoted 0 times
...
Tawna
9 months ago
But wouldn't modifying the base URL in the RAML file, like in option C, be simpler for versioning?
upvoted 0 times
...
Anjelica
9 months ago
I believe option B is also valid, adding a parameter in the listener could be a good way to handle multiple versions.
upvoted 0 times
...
Magda
9 months ago
I agree with Tawna, modifying flow names with a variable for version number seems like the correct approach.
upvoted 0 times
...
Tawna
9 months ago
I think the developer should choose option D to generate scaffolding from the RAML.
upvoted 0 times
...
Rene
9 months ago
By modifying the in the flows to include a parameter to replace the version number, it allows for flexibility in managing different versions of the API
upvoted 0 times
...
Joanna
9 months ago
What's your rationale for choosing option B?
upvoted 0 times
...
Rene
9 months ago
I disagree, I believe option B is better
upvoted 0 times
...
Stefania
10 months ago
Because modifying the flow names generated by APIKit to include a variable with the major version number seems like the most efficient solution
upvoted 0 times
...
Joanna
10 months ago
Why do you think that?
upvoted 0 times
...
Stefania
11 months ago
I think the developer should choose option D
upvoted 0 times
...
Nan
11 months ago
Hmm, I don't know. I feel like all these options are kinda messy. Why don't we just use a versioning strategy that's already been battle-tested, like the one used by the major cloud providers? That way, we don't have to reinvent the wheel.
upvoted 0 times
Nicholle
10 months ago
User 2
upvoted 0 times
...
Ronnie
11 months ago
User 1
upvoted 0 times
...
...
Virgie
11 months ago
Hmm, let me think about this... I think option C might be the way to go. Modifying the baseURI to include a variable for the version number sounds like a good way to expose multiple versions of the same API.
upvoted 0 times
...
Julieta
12 months ago
Whoa, this question is a tricky one! I'm not sure if I'm ready to tackle it yet. Gotta brush up on my API versioning skills, you know?
upvoted 0 times
...

Save Cancel