Which ports can pass messages to downstream actions?

Which ports can pass messages to downstream actions?

• A. Success and Failure ports
• B. Success and custom ports
• C. Success, Failure and custom ports
• D. Custom ports

Answer: (C)

In an FME workflow, downstream actions are triggered by the signal and data carried through transformer ports. The built-in success and failure ports are the primary channels that indicate whether a transformer completed normally or encountered an issue, and they plant messages and control the next steps in the flow. Custom ports add user-defined output paths, allowing you to route messages or features based on your own criteria beyond just success or failure. Because any of these ports can connect to downstream actions, all three types—success, failure, and custom ports—can pass messages downstream. The other options miss one of these routing possibilities, making them incomplete.

In an FME workflow, downstream actions are triggered by the signal and data carried through transformer ports. The built-in success and failure ports are the primary channels that indicate whether a transformer completed normally or encountered an issue, and they plant messages and control the next steps in the flow. Custom ports add user-defined output paths, allowing you to route messages or features based on your own criteria beyond just success or failure. Because any of these ports can connect to downstream actions, all three types—success, failure, and custom ports—can pass messages downstream. The other options miss one of these routing possibilities, making them incomplete.