A maker stores a customer’s loyalty tier in a variable during the Greeting topic and needs that value in a later Returns topic without asking again. Which variable scope should they use?
Select an answer to reveal the explanation.
Short Explanation
You need the global conversation-scoped variable—it sticks around for the session and later topics can read it. Topic-only variables won't carry over unless you pass them out, so don't rely on them.
Full Explanation
Copilot Studio distinguishes topic variables (local) from global/conversation variables (available across topics in the session). Cross-topic retention requires global scope or explicit input/output passing on redirects. The global conversation-scoped variable that persists across topics for the session is correct because it lets the Returns topic reuse the loyalty tier later without re-prompting. The topic-only Greeting variable with no output or global promotion is wrong because topic variables do not automatically become visible in other topics. The environment variable named LoyaltyTier overwritten by end users is wrong because environment variables are ALM configuration, not per-user chat state. The Dataverse security role name used as a pseudo-variable in Message nodes is wrong because it is unrelated to conversation state. Exam tip: Session facts → global variables; temporary slot fills → topic variables; deployment config → environment variables.