A business analyst has access to all of a company's data for the past 10 years. The source table consists of the following fields: TransactionID…

To optimize app performance, the primary goal is to reduce the amount of data loaded into Qlik's in-memory engine. This involves reducing both the number of columns (fields) and rows (records).

Option D provides the most effective and appropriate strategy. Deselecting the Cardholder and other unnecessary fields reduces the width of the data model. Applying a filter during the data extraction process to only load the last two years of transactions significantly reduces the number of rows, which is the most impactful performance improvement. Finally, in a managed Qlik Sense environment, scheduling automated daily reloads is an administrative task performed in the Qlik Management Console (QMC), so requesting this from a system administrator is the correct procedure.

A. Bookmarks and sheet-level reloads do not reduce the amount of data loaded into the app's memory; they only affect the user's view or perform a manual, one-time data refresh.

B. Set analysis performs calculations on data already loaded in memory. It does not reduce the initial data volume and therefore does not improve the app's load performance or memory footprint.

C. A filter pane, like a bookmark, is a user interface object for filtering data already present in the app. It does not reduce the size of the in-memory data model.

---

1. Filtering Data During Load & Deselecting Fields:

Qlik Sense® for Windows Help, "Best practices for data modeling," Section: "Reduce the amount of data". This official guide states, "The best way to make an application more efficient is to make sure that you only load the data you actually need for your analysis... Remove unused fields and tables... Filter data that is not needed in the app using WHERE clauses." This supports deselecting fields and applying a filter to extract only the required years.

2. Scheduling Reloads:

Qlik Sense® for Windows Help, "Administering Qlik Sense Enterprise on Windows," Section: "Managing reloads". The documentation specifies, "You create and manage reload tasks in the Qlik Management Console (QMC)." This confirms that scheduling is an administrative function, separate from the app development interface (Data Manager), making the request to a system admin the correct workflow for a business analyst.

3. Performance Impact of Data Reduction:

Qlik Sense® for Windows Help, "Performance and scalability in Qlik Sense Enterprise," Section: "Data model". The documentation emphasizes, "The amount of data loaded into a Qlik Sense app affects its performance... Reducing the amount of data in the app is the most effective way to improve performance." This validates that the core strategy in option D (reducing rows and columns at load time) is the most effective for performance.