ExamGecko
Question list
Search
Search

List of questions

Search

Related questions











Question 67 - Certified MuleSoft Platform Architect I discussion

Report
Export

Version 3.0.1 of a REST API implementation represents time values in PST time using ISO 8601 hh:mm:ss format. The API implementation needs to be changed to instead represent time values in CEST time using ISO 8601 hh:mm:ss format. When following the semver.org semantic versioning specification, what version should be assigned to the updated API implementation?

A.
3.0.2
Answers
A.
3.0.2
B.
4.0.0
Answers
B.
4.0.0
C.
3.1.0
Answers
C.
3.1.0
D.
3.0.1
Answers
D.
3.0.1
Suggested answer: B

Explanation:

4.0.0 As per semver.org semantic versioning specification:Given a version number MAJOR.MINOR.PATCH, increment the:- MAJOR version when you make incompatible API changes.- MINOR version when you add functionality in a backwards compatible manner.- PATCH version when you make backwards compatible bug fixes.As per the scenario given in the question, the API implementation is completely changing its behavior. Although the format of the time is still being maintained as hh:mm:ss and there is no change in schema w.r.t format, the API will start functioning different after this change as the times are going to come completely different.Example: Before the change, say, time is going as 09:00:00 representing the PST. Now on, after the change, the same time will go as 18:00:00 as Central European Summer Time is 9 hours ahead of Pacific Time.>> This may lead to some uncertain behavior on API clients depending on how they are handling the times in the API response. All the API clients need to be informed that the API functionality is going to change and will return in CEST format. So, this considered as a MAJOR change and the version of API for this new change would be 4.0.0

asked 23/09/2024
Ken Wilson
40 questions
User
Your answer:
0 comments
Sorted by

Leave a comment first