SAA-C03 · Question #182
A company has an application that receives and processes purchase orders. The application supports only XML data. The company needs to configure the application to accept orders in JSON format. The…
The correct answer is B. Use an HTTP proxy integration to pass XML requests to the application. For JSON requests, use. Why Option B is Correct: HTTP Proxy Integration: Passes XML requests directly to the application, which already supports JSON Conversion: An AWS Lambda function converts JSON requests to XML and calls the API Gateway: Acts as a front end to handle JSON requests and integrates…
Question
A company has an application that receives and processes purchase orders. The application supports only XML data. The company needs to configure the application to accept orders in JSON format. The company does not want to modify the application. A solutions architect is using an Amazon API Gateway HTTP API to create a new purchase order API. The solutions architect needs to modify the application DNS record to point to the new HTTP API. Which solution will meet this requirement?
Options
- AUse an HTTP proxy integration to pass XML requests to the application. For JSON requests, use
- BUse an HTTP proxy integration to pass XML requests to the application. For JSON requests, use
- CUse an HTTP custom integration to pass XML requests to the application. For JSON requests,
- DUse an HTTP custom integration to pass XML requests to the application. For JSON requests,
How the community answered
(24 responses)- A4% (1)
- B75% (18)
- C13% (3)
- D8% (2)
Explanation
Why Option B is Correct: HTTP Proxy Integration: Passes XML requests directly to the application, which already supports JSON Conversion: An AWS Lambda function converts JSON requests to XML and calls the API Gateway: Acts as a front end to handle JSON requests and integrates seamlessly with Lambda for the transformation process. Why Other Options Are Not Ideal: Option A: Suggests using API Gateway mappings to convert JSON to XML. API Gateway mapping templates are limited in functionality and are not ideal for complex transformations. Option C and D: Use HTTP custom integration unnecessarily, which adds complexity without additional benefits.
Community Discussion
No community discussion yet for this question.