A company is building a canvas app that spans multiple screens.

A global variable is appropriate for a selected scalar value that must remain available while the user moves between screens. It is created with Set and can be referenced anywhere in the canvas app for the remainder of the session unless changed. A collection is an in-memory table, so it is the correct component for holding multiple rows and columns of tabular data that controls such as galleries can consume. Context variables are scoped to a screen and would not reliably satisfy the cross-screen requirement. A data source is an external system or table rather than an application-state container; connecting to one does not itself preserve a temporary selection or session table. The maker should avoid duplicating authoritative data in a collection unless offline or transformation behavior requires it, and should clear sensitive session state when appropriate. For large datasets, delegable source queries are preferable to indiscriminate collection loading. The Study Guide’s exact canvas-app objective is “manage variables and collections.” Options A and D match the required tabular and application-wide scalar state types.

Study Guide reference/topic: “Create canvas apps — Manage variables and collections.” AB-410 Study Guide | Microsoft Learn technical reference