What will the data architect see when selecting a month?

Exhibit.

Refer to the exhibit.

The data architect needs to build a model that contains Sales and Budget data for each customer.

Some customers have Sales without a Budget, and other customers have a Budget with no Sales.

During loading, the data architect resolves a synthetic key by creating the composite key.

For validation, the data architect creates a table that contains Customer, Month, Sales, and Budget columns.

What will the data architect see when selecting a month?
A . Customer Names and Sales records for the selected month, Budgets column can contain null or non-null values
B . All Customer Names for both Sales and Budget records for the selected month
C . Customer Names and Sales records for the selected month but with only non-null values in Budget column
D . Customer Names and Budaets records for the selected month. Sales column can contain null or non-null values

View Answer

Answer: A

Explanation:

In the scenario where the data model is built with a composite key (keyYearMonthCustNo) to resolve synthetic keys, the following outcomes occur:

Sales and Budget Data Integration:

The composite key ensures that each combination of Year, Month, and Customer is uniquely represented in the combined Sales and Budget data.

During data selection (e.g., when a specific month is selected), Qlik Sense will show all the customer names that have either Sales or Budget data associated with that month.

Resulting Data View:

For the selected month, customers with sales records will display their Sales data. However, if the corresponding Budget data is missing, the Budget column will contain null values.

Similarly, if a customer has a Budget but no Sales data for the selected month, the Sales column will show null values.

Validation Outcome:

When the data architect selects a month, they will see the following:

Customer Names and Sales records for the selected month, where the Sales column will have values and the Budget column may contain null or non-null values depending on the data availability.