QlikView Architecture Interview Questions Answers 4 Experinced

Here is the one more new set of QlikView Interview questions and answers, This set contains QlikView Architecture related interview questions with answers.
Q-1). Optimized and unoptimized QVD Load Situations?
Ans: Optimized load is much faster and therefore preferable, especially for larger data sets.
Optimized loads are possible if no transformations (calculations) are made during the load, and no (almost) filtering is done in a WHERE clause.
The only acceptable filter is using function Exists:
WHERE Exists(Field)

So for example this load can't be optimized:
Load * From ... WHERE Country = 'US'

but this load can:
Load * From ... WHERE EXISTS(Country)
On the other hand, the only time you want the load not to be optimized, is if you load a Mapping table from a QVD file. In this case, Optimized load doesn't quite work, so you want to make the load non-optimized deliberately.
 
Q-2). Explain 3 tier architecture implementation while deploying QlikView application?
Ans:
1st Tier - Raw data is getting loaded and QVD is creating.
2nd Tier - QVD is transform in the business login and requirement of the business and data model is created.
3rd Tier - Reading the all QVD from 2nd tier and make a single QVW or may be any binary load.

Q-3). Briefly explain how does QlikView storage the data internally?
 Ans: QlikView store data in to QVD . QVD have data compression capability . QlikView have better performance compared to other BI because of in memory analytics approach , in built ETL handling capability.
for more click here

Q-4). What are the restrictions of Binary Load?
 Ans: Binary load is used only for one application means you are able to read data from only one QVW application and on the above of the set scripts is a restriction.
In qlikview data is stored in QVDs but if you are using any QVW application data is loaded in the RAM thats why it is called as In-Memory analysis tool.

Q-5). How are NULLS implemented in QlikView?
 Ans: Click here for Answer

Q-6). How do you optimize QlikView Application? (What tools are used and where do you start?)
Ans: Click here for Answer

Q-7). What is the difference between Subset ratio & Information Density?
Ans: Information density of the field, which indicates the percentage of rows that contain a non-null value
Subset ratio, which shows the percentage of all distinct values for a field in the
table compared to all the distinct values for that field in the entire data model. It is only relevant for key fields since they are present in multiple tables and do not all share the same value.

Subset ratios can be used to easily spot problems in key field associations.
For example, when the combined total of subset ratios for multiple tables is 100 percent, this may indicate that there are no matching keys between these tables.

REF: QlikView 11 For Developers..
Let me give you simple example

Sales:
Load * Inline
[
  Customer, Sales
  A, 100
  B, 200
  D, 300
];


Customer:
Load * Inline
[
  Customer
  A
  B
  C
  D
];

If you write above sample script and will check the Table (CTRL + T), you will find two tables.
Sales and Customers
On Sales Table, if you hover the mouse on Customer field, you can see the Subset Ratio is 75% because there is not sales data for Customer C.
Now if you change the script for table Customer like below..
Customer:
Load * Inline
[
  Customer
  A
  B
  C
  D
]
Where Exists (Customer);
If will not load the Customer C as there are no sales data for the same.
Now check the Subset Ratio. It will be 100%.

If subset ratio is less than 100%, the key is called as Primary Key
but for 100% it is called as Perfect Key.