A Copilot Studio developer builds a 'Get Customer Profile' topic that collects a customer's account tier (Bronze, Silver, Gold) and stores it in a topic variable. A separate 'Process Discount' topic needs to read the account tier to calculate the appropriate discount. What is the correct way to pass the account tier between topics?

## Why B is Correct Copilot Studio topics support input and output variables for topic-to-topic data passing. In the 'Get Customer Profile' topic, you declare the account tier as an output variable. When a 'Redirect to another topic' node calls 'Process Discount,' a mapping dialog appears where you assign the output variable's value to the 'Process Discount' topic's input variable. This is a clean, explicit data contract between topics.

## Why the Distractors Are Wrong A (Global variable): While using a global variable works, it is not the recommended pattern when the data flows directionally between two topics in sequence. Global variables are best for data needed broadly throughout the conversation, not for a single producer-consumer relationship.

C (Dataverse round-trip): Writing to and reading from Dataverse between topics is slow, complex, and unnecessary when topic input/output parameters provide a direct, in-memory channel.

D (Combine topics): Topics should be split for maintainability and reuse. The inability to pass variables between topics is false — Copilot Studio explicitly supports topic-level input/output parameters.

## Exam Tip Topic input/output variables vs. global variables: Use topic I/O for directed, sequential flows. Use globals for broadly shared session state. Both are valid; the exam tests whether you know the input/output parameter mechanism exists.