The business analyst needs to optimize the app for performance and ensure that users only see data from the past two years, without cardholder information, and that the data is updated daily. Bydeselecting the Cardholder and time fieldsin the Data Manager, the analyst ensures that sensitive information is not loaded. Applying afilter to extract data based on transaction yearensures that only relevant data (the last two years) is included in the app, improving performance. Lastly, requesting a daily reload task from the system administrator ensures that the app stays up to date.

Key Concepts:

Deselecting Fields: This removes unnecessary fields, such as Cardholder information, from the data model, which improves performance and ensures privacy.

Filtering Data: Applying a filter to limit data to the last two years reduces the dataset size and improves app responsiveness.

Daily Reload Task: Requesting a daily reload ensures that the app’s data stays current, meeting the requirement for daily updates.

Why the Other Options Are Less Suitable:

A. Delete Cardholder and time fields, use bookmark: A bookmark is not an efficient solution for filtering by transaction year.

B. Set analysis and API reload: Set analysis works within the app but does not optimize the data load itself. Using an API for reload tasks is unnecessarily complex.

C. Use filter pane and auto-calendar: While auto-calendar fields can be useful, they don’t optimize the data loading process for performance.

References for Qlik Sense Business Analyst:

Efficient Data Loading: Qlik Sense recommends filtering data at the load stage to improve performance, especially when dealing with large datasets.

Thus,Dis the correct solution, making it the verified answer.