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
Global variables are sticky notes on the conversation window — any topic can read them later. Topic-only variables wash off when you leave that topic unless you pass them as outputs.
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.
Option A is correct for session-wide reuse without re-prompting.
Option B is false; topic variables do not automatically become global.
Option C misuses environment variables (ALM configuration, not per-user chat state).
Option D is unrelated to conversation state.
Exam tip: Session facts → global variables; temporary slot fills → topic variables; deployment config → environment variables.