Cognizant Interview Questions on Informatica
- 1) What is Star schema in informatica?
- 2) What is snow flake schema ?
- 3) How do remove duplicates values in informatica from DB and Flat file?
- 4) What are different types of SCD?
- 5) What is Performance tuning in Informatica?
- 6) What is Lookup Transformation in Informatica?
- 7) What is a difference between joiner and lookup transformation?
- 8) What are different types of loading in Informatica?
- 9) What is incremental loading is Informatica?
- 10) Which type of transformation is not supported by mapplets?
- 11) What are bridge tables in informatica?
Below are the list of Best Cognizant Informatica Interview Questions and Answers
Star Schema in a data warehouse, in which the center of the star can have one fact table and a number of associated dimension tables. As its structure resembles a star so it is known as a star schema.
In the data warehouse, Snowflake Schema is a logical arrangement of tables in a multidimensional database
distinct property(keyword) is used to eliminate duplicate rows in Informatica from a database and a flat-file.
We can eliminate duplicate rows from the flat-file by using group by function in an aggregator or in source qualifier in database.
You can select distinct all or by using sorter transformation in flat-file.
You can remove duplicates values in Informatica from DB as follows:
You can use the Distinct option of the Source Qualifier in the source table and load the target accordingly.
You can remove duplicates values in Informatica from Flat-file as follows:
When the source system is a Flat File distinct option is disabled in the source qualifier. You may use a Sorter Transformation and check the Distinct option. Then all the columns will the selected as keys, in ascending order by default.
The different types of SCD are as follows:
Type 0 – Fixed Dimension. No changes allowed, dimension never changes.
Type 1 – No History. Update record directly, there is no record of historical values, only the current state.
Type 2 – Row Versioning.
Type 3 – Previous Value column.
Type 4 – History Table. Type 6 – Hybrid SCD.
Performance tuning is the improvement of system performance that starts with the identification of bottlenecks in the source, target, and mapping and further to session tuning. Performance tuning aimed to optimize session performance by eliminating performance bottlenecks to get a better acceptable ETL load time.
Lookup transformation is a kind of join operation. Lookup transformation is a passive transformation. It has one of the joining tables as the source data and the other joining table known as the lookup table. Basically, It is used to look up a source, source qualifier, or target to get the relevant data. It also returns the result of the lookup to the target or another transformation.
The difference between joiner and lookup transformation is as follows:
|Joiner :||Lookup :|
|A joiner is used to join data from different sources.||lookup is used to get related values from another table or check for updates etc in the target table.|
|It supports Equiv Join only.||It supports both Equiv and Non-Equiv join.|
|It may be we can perform outer join only.||Lookup used to source as well as the target.|
|Joiner is used to source only.||It can not perform the outer join in lookup.|
|It may used only the "=" operator.||It may used = , < , > , <= . >= operators.|
|In joiner maybe not present in lookup override.||It may be present in the lookup override option.|
|Joiner table must participate in mapping.||The lookup may not participate in mapping|
|Joiner is used for joining two homogeneous or heterogeneous sources residing at different locations.||Lookup is used to look-up the data.|
|Joiner is an Active Transformation.||Lookup transformation is a Passive transformation.|
The different types of loading in Informatica are as follows:
- Normal loading
- Bulk loading
Normal loading loads record by record and writes log for that. Bulk loading loads the data fast and recovered easily.
Incremental data loading is defined as the process of loading the selective data. It is either updated or creates a new source system to the target system. This is different from a full data load where entire data is processed each load.
Normalizer, Cobol sources, XML sources, XML Source Qualifier transformations, Target definitions, Pre- and Post- session Stored Procedures, Other Mapplets are not supported by Mapplets.
A bridge table acts between a fact table and a dimension table. It is used to resolve many-to-many relationships between a fact and a dimension. The bridge table will contain only two dimension columns and key columns in both dimensions.
Latest Interview Questions
Weblogic Interview Questions
AngularJS Interview Questions
React Js Interview Questions
HTML5 Interview Questions
Firebase Interview Questions
BPO Interview Questions
Cobol Interview Questions
Actuarial Interview Questions
Tally Interview Questions
Hive Interview Questions
Xml Interview Questions
Redis Interview Questions
C Programming Interview Questions
CICS Interview Questions
UFT Interview Questions
AEM Interview Questions
C# Interview Questions
Zend Framework Interview Questions
Mainframe Interview Questions
Jenkins Interview Questions
Cassandra Interview Questions
Oracle Interview Questions
SDLC Interview Questions
Matlab Interview Questions
UX Designer Interview Questions
Swift Interview Questions
8051 Microcontroller Interview Questions
AWS Lambda Interview Questions
Vue.js Interview Questions
Postgresql Interview Questions
Subscribe Our NewsLetter
Never Miss an Articles from us.