An integration developer is designing a mediation module that is required to pass MQRFH2 information to a downstream service using an MQ Binding. What part of the Service Message Object should the…

Question

Options

• AContext
• BHeaders
• CBusiness Object graph
• DBusiness Object metadata

• A
  10% (2)
• B
  50% (10)
• C
  25% (5)
• D
  15% (3)

Explanation

Headers (option B) is correct because the Service Message Object (SMO) Headers section is specifically designed to carry transport-protocol-specific information - and MQRFH2 is an MQ transport header. When a message is dispatched via an MQ Binding, the binding reads the SMO Headers section to construct the outgoing MQ message, including MQMD and MQRFH2 fields.

Context (A) is wrong because it holds processing metadata such as correlation, security, and transactional context - not transport-level headers. Business Object graph (C) is wrong because it represents the message payload (the actual business data being exchanged), not envelope/header information. Business Object metadata (D) is wrong because it carries type information about the business objects, not MQ-specific protocol headers.

Memory tip: Match the layer - transport headers belong in Headers, payload belongs in the Business Object graph. MQRFH2 is an MQ header, so it lives in Headers. If you can address it at the wire/protocol level, it goes in Headers.

No community discussion yet for this question.