Do XML SDK custom errors require a mapping element, a definition, or both?

• A. Only a definition
• B. Neither
• C. Only a mapping element
• D. Both

Answer: (D)

In the XML SDK, you need two parts to have a complete custom error: a definition and a mapping. The definition describes what the error is—its identity, code, default message, and optional remediation. The mapping defines how that error is produced and surfaced during runtime—how an exception or condition maps to that error and how the response should be structured (such as the HTTP status and the payload).

Think of it as two sides of the same coin. The definition gives you a concrete error you can reference, while the mapping ties that error to real execution paths and to how clients will see it. If you only have a definition, there’s no mechanism to trigger or map a runtime condition to that error. If you only have a mapping, there’s no predefined description of the error itself to return to clients. Having both ensures a consistent, well-defined error that is properly produced and properly presented to API clients.