Two customers in an organization want to use an app that contains a finance data set. With different analysis objectives, each customer will only use…

Set analysis is the most appropriate Qlik Sense feature for this scenario. It allows a business analyst to create specific expressions within visualizations that define a data scope independent of the user's current selections. By using set analysis, the analyst can build different charts or tables on the same or different sheets, each tailored to a customer's unique analytical objective. This approach maintains a single app and a single data model, ensuring efficiency, consistency, and ease of maintenance while providing customized analytical views for each customer.

A. Apply Section Access to manage the data for each customer

Section Access is a security feature for row-level data reduction, not a tool for tailoring analysis. It would restrict what data users are allowed to see, which is not the primary requirement here.

C. Duplicate and rename the apps for each customer

This creates significant maintenance overhead. Any change to the data model or a master visualization would need to be replicated in every duplicated app, which is inefficient and error-prone.

D. Unpivot, then re-associate the data tables for each customer

Unpivoting is a data transformation technique used in the load script. It addresses the structure of the data model, not the creation of different analytical views for end-users within the app interface.

---

1. Qlik Sense® for Windows Help, "Using set analysis" section.

Reference: "Set analysis offers a way of defining a set of data values that is different from the normal set defined by the current selections in an app. This is useful when you want to make comparisons between data sets, for example, to compare sales for the current year with the previous year, or to compare a selected region's sales with the total for all regions." This directly supports using set analysis to create different analytical views (comparisons/subsets) for different objectives.

2. Qlik Sense® for Windows Help, "Managing security with section access" section.

Reference: "You can use section access to control the security of an app. It allows you to control what data and what features users can access when they open an app... Section access is applied to the data in an app, restricting user access to specific data rows and columns." This confirms that Section Access is a security/governance tool, making it less suitable for the stated goal of meeting "analysis objectives."

3. Henric Cronström, Qlik Principal Enterprise Architect, "App Proliferation" (Qlik Community Blog).

Reference: While not a formal document, this blog by a Qlik expert articulates a widely-held best practice. It explains the problems of app duplication: "The main problem with app proliferation is maintenance. If you need to change a formula, a master item, or a variable, you will have to do it in all apps... This is both tedious and error-prone." This supports the reasoning for why option C is incorrect.

4. Roche, D. (2019). Mastering Qlik Sense. Packt Publishing.

Reference: Chapter 7, "Advanced Expressions and Set Analysis," explains that set analysis allows developers to "define the scope of an aggregation, completely independent of the selections made by the user." This capability is the foundation for creating visualizations that cater to different, pre-defined analytical objectives as required by the question.