You are creating a multi-page canvas app that loads tabular data from an external data source.
Once loaded, the data must be available to all screens within the canvas app.
You need to reduce the number of times that the app must retrieve data from the data source.
Which two data stores can you use? Each correct answer presents a complete solution.
NOTE: Each correct selection is worth one point.
To ensure that the tabular data loaded from an external data source is available across all screens and to reduce the number of times the app retrieves this data, you can use global variables and collections. Global variables allow data to be stored and made accessible across different screens within the app, thus avoiding multiple retrievals from the data source. Collections can hold tables of data locally within the app, making the data available across different screens without needing to query the external data source again.
B. global variable and C. collection https://learn.microsoft.com/en-us/power-apps/maker/canvas-apps/working-with-data-sources https://learn.microsoft.com/en-us/power-apps/guidance/planning/where-is-data
You can use two data stores to reduce the number of times that the app must retrieve data from the data source: collections and global variables. Collections are local data sources that are not backed by a connection to a service in the cloud, so the information can not be shared across devices for the same user or between users. Collections can be loaded and saved locally. Global variables are values that you can set and use throughout your app, on any screen. You can use global variables to store data that you want to use across screens.
Global Variable & Collections
they didn't say that we are speaking about multiple environment, they asked if we have a canvas app with different screen so one environment. It must be Global variable so B & C
Theoretically you can also use an environment variable, but it would be an overkill in this case, because you need the data only in your application. The environment variable would make it available for the whole environment, which in this case would be totally unnecessary.
global variables can store a table.. does that make it a valid option?
Environment Variables are only needed when exporting solutions to a different environment
After going through some information, I also agree it is C and D as environment variables allow for queries of the data source less than a direct connection. The global variable here has not much use
There is no reference to exporting the app/solution, therefore Global Variable & Collection
Global variable is not really for data source to store, but it can be also store on a variable. We know that collection and environment variable are really for, to contain data sources data.
Is that right? There is "You need to reduce the number of times that the app must retrieve data from the data source.".Global variable will retrieve data from the data source, and Collections and Environment not. [Use environment variables in solutions - Power Apps | Microsoft Docs](https://docs.microsoft.com/en-us/power-apps/maker/data-platform/environmentvariables)
I agree it is B and C
Out of the provided options, the two data stores you can use to achieve this functionality are: Collection (C): Collections are in-memory data structures within a canvas app. They can hold a table of data loaded from the external data source. Once loaded, the collection can be accessed and referenced from all screens within the app. This reduces the need to repeatedly retrieve data from the external source. Global variable (B): Global variables are another option for storing data accessible across all screens. However, unlike collections, global variables can only hold a single value at a time. If you need to store a table of data, a collection is the better choice. So the correct answers are C. collection and B. global variable.
B. Global variable C. Collection
You can use environment variables, but this would take quite a significant amount of development to maintain sync and will be considerably slower. BC correct
B&C = Global variable and Collection
C seems to be clear. D shoul not be correct. Also the Description say, don't use Environment Variables. I can't imagine in which way an Environment Variable can help caching retrieved data localy. B seems to be useful. Data can be loaded into a Variable that is globally available within the App (and within the the current session of a specific user).
Global Variable & Collections