Which statement best describes how the Poll scope's watermark is accessed in a flow?

Which statement best describes how the Poll scope's watermark is accessed in a flow?

• A. A flow variable
• B. The payload
• C. Inbound property
• D. A session variable

Answer: (A)

The thing being tested is where the Poll scope keeps and accesses its per-poll state. The watermark is internal to the flow’s execution and needs to persist as the Poll scope iterates across polls. Flow variables are exactly for storing data that is specific to the current flow instance and that you want to read and update as the flow processes messages, including across repeated poll iterations. That’s why the watermark is accessed as a flow variable—the Poll scope uses the flow scope to remember where it left off and to determine where to start for the next poll. Payload holds the actual message content and changes as messages are processed, so it isn’t a stable place to store cross-poll state. Inbound properties reflect metadata of the incoming message and are not intended for persisting polling state. Session variables, when available, span across flows, which isn’t appropriate for per-flow poll tracking. The flow variable approach keeps the watermark tied to the specific flow instance and its polling lifecycle.

The thing being tested is where the Poll scope keeps and accesses its per-poll state. The watermark is internal to the flow’s execution and needs to persist as the Poll scope iterates across polls. Flow variables are exactly for storing data that is specific to the current flow instance and that you want to read and update as the flow processes messages, including across repeated poll iterations. That’s why the watermark is accessed as a flow variable—the Poll scope uses the flow scope to remember where it left off and to determine where to start for the next poll.

Payload holds the actual message content and changes as messages are processed, so it isn’t a stable place to store cross-poll state. Inbound properties reflect metadata of the incoming message and are not intended for persisting polling state. Session variables, when available, span across flows, which isn’t appropriate for per-flow poll tracking. The flow variable approach keeps the watermark tied to the specific flow instance and its polling lifecycle.