How are outbound properties automatically passed to an outbound REST request using an HTTP Request component?

How are outbound properties automatically passed to an outbound REST request using an HTTP Request component?

• A. As query parameters
• B. As headers
• C. As body content
• D. As path variables

Answer: (B)

Outbound properties are values carried with the message as it moves to the HTTP transport, and the HTTP Request component uses those properties to populate the outgoing request. By default, these properties become HTTP headers on the REST call, so any information you put into outbound properties—such as authorization data or custom metadata—ends up in the request headers automatically. Query parameters, body content, and path variables are separate parts of the request that come from different places (the URL’s query string, the message payload, or the endpoint path). They’re not filled from outbound properties unless you explicitly map them to those parts.

Outbound properties are values carried with the message as it moves to the HTTP transport, and the HTTP Request component uses those properties to populate the outgoing request. By default, these properties become HTTP headers on the REST call, so any information you put into outbound properties—such as authorization data or custom metadata—ends up in the request headers automatically.

Query parameters, body content, and path variables are separate parts of the request that come from different places (the URL’s query string, the message payload, or the endpoint path). They’re not filled from outbound properties unless you explicitly map them to those parts.