In RAML, how would you declare a query parameter named year with type integer, making it optional?

• A. year: type: integer required: false
• B. year: type: integer required: true
• C. year: required: false
• D. year: type: string required: false

Answer: (A)

In RAML, you control a query parameter by giving it a name, a type, and whether it is required. To have a parameter named year that must be an integer when provided and is optional to the caller, you declare year with a type of integer and set required: false. This combination enforces the value, if present, to be an integer, while allowing the parameter to be omitted entirely. The other patterns don’t fulfill both parts: missing the type or using a non-integer type would fail the integer constraint, and marking the parameter as required would make it mandatory rather than optional.