QSBA2024 Exam Dumps : Qlik Sense Business Analyst Certification Exam-2024

The app is experiencing performance issues due to inefficient calculations in a master measure that processes the field TransactionName, which has a complex structure (e.g., "1_ABCDEFGHI_23454"). Let’s analyze the available options and whyOption Bis the best solution.

A. Ask the developer of the underlying database to change the structure of the field TransactionName.While modifying the data structure in the underlying database might improve performance, this approach is not ideal. It’s a time-consuming process that might not be feasible, especially when working with large datasets that have already been integrated into the Qlik Sense app. The performance improvement should focus on optimizing the Qlik app itself.

B. In the Data manager, use the Split function to split the field values with the underscore character as the separator. In the Data manager, use the Add calculated field function to multiply the 1st and the 3rd column of the split field. Reload the data.This is the most efficient approach. By using theSplit functionin the Data Manager to break down the TransactionName field based on the underscore separator, the data becomes more accessible for calculations. You can then create a calculated field that multiplies the first and third components of the split data (corresponding to the 1st part and the numeric identifier at the end). This reduces the need for complex string manipulation functions (e.g., Left, Right, Trim) within the master measure, which can be resource-intensive when applied to large datasets.

C. Change the master measure definition as follows: subfield( TransactionName, '',!) * subfield( TransactionName, '', 3)This option suggests using thesubfield() functionto split the string within the master measure itself. While this approach is valid, it doesn’t provide as significant a performance improvement compared to pre-processing the data in theData Manager. Calculating fields directly within the visualizations is more computationally expensive compared to handling it during the data load phase.

D. In the Data manager, use the Replace function to remove the middle part of the field TransactionName.TheReplace functionwould remove the middle section of the transaction name, but it doesn’t address the need to split the field for efficient multiplication. It would also result in a loss of important data that may be required for other analyses.

Key Qlik Sense Business Analyst References:

TheData Managerprovides powerful tools for transforming and optimizing data before it is used in visualizations. Pre-processing the data using functions likeSplitsignificantly reduces the load on front-end visualizations.

Splitting fields during the data load rather than in the master measures improves performance, especially in large datasets where string manipulation functions in visualizations can degrade performance.

Calculated fieldsallow analysts to create new expressions based on transformed data, ensuring that the app remains efficient while meeting analytical needs.

Thus, the correct solution is touse the Split function to separate the field values and then use a calculated field to multiply the required components, which enhances app performance.

To meet the requirement of controlling the number of products displayed in the bar chart, the business analyst should use aslider objecttied to a variable. The variable will store the number of products the user wants to display. In theAppearancesection of the bar chart's properties, the analyst can set the number of bars to acustom valueusing 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 theslider objectand setting the number of bars to acustom valuecontrolled by the variable is the best solution, makingAthe verified answer.

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 fieldsCY Revenue, LY Revenue, and CY Costare 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 includeCY 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,Aprovides the correct set of fields for the required dashboard, making it the verified answer.