Refer to the exhibit. The API needs to be updated using the company-wide standard for the Plan data type. The Object data type has already been published in Anypoint Exchange with the global…

The correct answer is D. Option D. As can be seen in RAML, POST expects input in application/json format which eliminates two of the options as two options are in xml format. Now out of the two remaining options, one has id field in request which is only mentioned for get response and not for POST request. Hence…

API Design with RAML

Question

Refer to the exhibit. The API needs to be updated using the company-wide standard for the Plan data type. The Object data type has already been published in Anypoint Exchange with the global reference . ACME/DataTypes/PlanDataType.raml. What is a valid RAML specification that reuses the Plan data type? A) B) C) D)

Exhibit

Options

AOption A
BOption B
COption C
DOption D

How the community answered

(37 responses)

A
14% (5)
B
8% (3)
C
3% (1)
D
76% (28)

Explanation

As can be seen in RAML, POST expects input in application/json format which eliminates two of the options as two options are in xml format. Now out of the two remaining options, one has id field in request which is only mentioned for get response and not for POST request. Hence id field is not expected in POST request. Hence correct answer is "name": "GoerdiLa Forge", "address": "1 Westland CA", "customer_since": "2014-01-04", "balance": "4829.29", "bank_agend_id": "12556"

Topics

#RAML fragments#Anypoint Exchange#data type reuse#RAML libraries

Community Discussion

No community discussion yet for this question.

Full MCD-LEVEL-1 Practice