QSBA2024

Explanation:
To fulfill the CFO’s request for an app that allows each regional finance team to access only their data while navigating from a high-level sheet to detail sheets, the combination of a dashboard of KPIs and Section Access is ideal. A dashboard of KPIs provides high-level insights, and Section Access ensures that users from different regions can only see the data relevant to their region. Section Access allows for controlled access to data, ensuring data security and segregation.
Key Concepts:
Dashboard of KPIs: A dashboard displaying key performance indicators (KPIs) gives a high-level overview of financial data, allowing users to quickly assess critical metrics.
Section Access: This Qlik Sense feature controls data access based on user roles, ensuring that users only have access to the data relevant to their region.
Why the Other Options Are Less Suitable:
B. Pivot table: A pivot table is useful for detailed analysis but not suitable for designing a navigation structure or controlling access to data by region.
C. Multi KPI with set analysis: While set analysis can filter data, it doesn’t control access at the regional level as effectively as Section Access.
D. Dashboard with regional bookmarks: Bookmarks are user-specific and do not offer security or access control, which is required in this scenario. References for Qlik Sense Business Analyst:
Section Access for Regional Data Control: Qlik Sense recommends Section Access for managing data access when different users need to see only specific subsets of data.
Thus, A is the best solution because it combines high-level KPIs with robust data access controls using Section Access, making it the correct answer.

Explanation:
A line chart is the most appropriate visualization for comparing two continuous measures (Profit and Revenue) over time. Line charts are designed to show trends and patterns over a continuous scale (such as time), making it ideal for this scenario where we need to observe how both Profit and Revenue vary across a period.
Key Concepts:
Continuous Scale: Line charts are specifically suited for continuous data like time, making them the preferred choice when tracking changes over time for multiple measures.
Dual Measure Comparison: A line chart allows you to plot two measures on the same axis, making it easy to compare their trends over the same period.
Why the Other Options Are Less Suitable:
B. Bullet chart: A bullet chart is used to compare a single measure against a target, not for tracking two measures over time.
C. Bar chart: Bar charts are better suited for comparing categorical data, not continuous measures over time.
D. Scatter plot: Scatter plots are used to compare relationships between two measures but are not
suited for continuous time-based comparisons.
References for Qlik Sense Business Analyst:
Line Charts for Time Series Data: Line charts are the recommended visualization for comparing multiple measures over time in Qlik Sense, especially when working with continuous data like Profit and Revenue.
Thus, the line chart is the best choice for this scenario, making A the correct answer.

Explanation:
The best approach to allow users to frequently adjust the profit threshold in the visualization is to use a variable controlled by a variable slider. This method allows each user to adjust the threshold value independently without requiring any changes to the data model or the visualization itself. Given that the user base consists of heavy Excel users, using a slider provides a familiar and intuitive way to interact with the threshold.
Key Concepts:
Variables and Sliders: Variables can be used to store threshold values, and sliders provide an easy way for users to adjust those variables interactively.
User Interaction: A variable slider is a user-friendly option for adjusting thresholds frequently, especially for users who are accustomed to working with data interactively.
Why the Other Options Are Less Suitable:
A. Threshold field with a filter pane: This option is less flexible and doesn't allow the same dynamic interaction as a variable and slider.
B. Shared spreadsheet and frequent app reloads: This approach is inefficient and would increase the
load on the system unnecessarily. It is also less user-friendly for frequent threshold adjustments.
D. Bucket function: The Bucket function is not appropriate for this case, as it creates static groupings, which would not allow the user to adjust the threshold dynamically. References for Qlik Sense Business Analyst:
Interactive Thresholds with Variables: Qlik Sense's variables and slider objects provide the best mechanism for dynamically controlling thresholds in a visualization.
Thus, introducing a variable for the threshold and controlling it with a variable slider is the best solution, making C the correct answer.

Explanation:
To meet the requirement of controlling the number of products displayed in the bar chart, the business analyst should use a slider object tied to a variable. The variable will store the number of products the user wants to display. In the Appearance section of the bar chart's properties, the analyst can set the number of bars to a custom value using the variable, ensuring that the user can dynamically change the number of displayed products.
Key Concepts:
Slider Object: This provides a user-friendly way for users to adjust the number of products displayed in the bar chart.
Custom Bar Limitation: By setting the number of bars displayed to a custom value controlled by the variable, the business analyst ensures that the user can dynamically adjust how many products are shown.
Why the Other Options Are Less Suitable:
B. Use the variable to fix the limitation and add an input box: While this could work, sliders provide a better, more intuitive user experience than input boxes for adjusting values dynamically.
C. Use the variable to fix the limitation and add a slider: This is almost correct, but it misses the step of setting the number of bars to a custom value using the variable.
D. Add the slider object and set its value, but without custom bar settings: While adding a slider is correct, not setting the number of bars to custom using the variable means the user wouldn’t be able to dynamically control the number of displayed products. References for Qlik Sense Business Analyst:
Dynamic Control with Variables and Sliders: Qlik Sense best practices recommend using sliders and variables to give users control over visualizations, particularly when it comes to dynamically limiting data displayed.
Thus, adding the slider object and setting the number of bars to a custom value controlled by the variable is the best solution, making A the verified answer.

Explanation:
The banking dashboard requires several KPIs and visualizations based on current year (CY) and last year (LY) revenue, as well as cost and customer satisfaction. To build the required measures, the fields CY Revenue, LY Revenue, and CY Cost are necessary because they provide the comparison between the current and previous year, as well as cost-related data for the specific calculations. Key Concepts:
KPI for CY vs LY Revenue: This requires both CY Revenue and LY Revenue fields.
Scatter Plot for Cost vs Revenue: This comparison requires both CY Revenue and CY Cost to create the necessary relationship in the scatter plot.
Treemap for Customer Satisfaction: In addition to the customer satisfaction rating, the field CY Revenue would likely be used for additional insights by region.
Table with CY Cost: The table requires CY Cost data along with other relevant fields like record number, financial instrument, and bank.
Why the Other Options Are Less Suitable:
B. CY Revenue, LY Revenue, Cost: While this covers the revenue fields, it does not specifically include CY Cost, which is needed for the table and scatter plot.
C. Revenue and Cost: This option is too general and does not distinguish between current year and last year revenue, which is essential for the KPI.
D. Revenue and CY Cost: This does not include LY Revenue, which is required for the KPI.
References for Qlik Sense Business Analyst:
Comparison Measures in Qlik Sense: In Qlik Sense, comparisons across time periods like CY and LY require specific fields to calculate accurate insights, and it’s essential to ensure the appropriate fields are included for each visualization.
Thus, A provides the correct set of fields for the required dashboard, making it the verified answer.