PR000041 practice question 6 of 15

Two pipelines (A & B) are entering a Joiner transformation with each having a record size of 100 bytes. Pipeline A has a total of 1000 records and…

Choose your answer, then check it against the explanation and the full breakdown below.

Two pipelines (A & B) are entering a Joiner transformation with each having a record size of 100 bytes. Pipeline A has a total of 1000 records and Pipeline B has a total of 1,000,000 records. Which pipeline should be designated the master pipeline?

Answer options

Correct Answer:

Explanation

To optimize performance, the Joiner transformation caches the entire master pipeline in memory or on disk before processing the detail pipeline. Designating the pipeline with the fewer number of records as the master minimizes the size of this cache. This reduces memory consumption and potential disk I/O, leading to faster processing. Pipeline A has only 1,000 records compared to Pipeline B's 1,000,000 records. Therefore, Pipeline A should be the master source to ensure the most efficient join operation.

Why Incorrect

B. Pipeline B

Designating the larger pipeline as the master would create an unnecessarily large cache, consuming excessive memory and degrading performance.

C. Both Pipelines should be cached for performance reasons

The Joiner transformation architecture is designed to cache only one source (the master) while streaming the other (the detail).

D. Pipeline B if and only if Pipeline A is sorted

While sorted input can optimize the join, the fundamental principle of selecting the smaller source as the master remains the primary performance consideration.

References

1. Informatica PowerCenter 10.5

Transformation Guide

Chapter 15: Joiner Transformation

Section: "Designating a Master Source"

Page 299.

The official documentation states

"For an unsorted Joiner transformation

designate the source with fewer rows as the master source. When the Integration Service processes an unsorted Joiner transformation

it blocks the master source while it caches all the master rows... Caching the source with fewer rows minimizes the amount of memory and disk storage that the Joiner transformation requires for the cache."

2. Informatica Intelligent Cloud Services Documentation

Transformations

"Joiner transformation"

Section: "Master and detail sources".

This guide reinforces the principle: "For better performance

use the source with fewer rows as the master source." This shows the concept is fundamental across Informatica products.

3. Kimball

& Caserta

J. (2004). The Data Warehouse ETL Toolkit. Wiley Publishing

Inc.

Chapter 4: Data Cleansing

Section: "The Joiner Stage".

While a third-party book

it is a foundational academic text in the field. It explains that join strategies in ETL tools universally benefit from caching the smaller of the two data sets to minimize memory and I/O overhead

which is the core principle tested in the question.

Question 6 of 15

Question breakdown

Tests: Joiner transformation performance tuning
Difficulty: Easy

Key idea: The Joiner caches the master source and streams the detail source, so the smaller source should be the master to keep the cache small.

How to reach the answer

Note that both pipelines have the same row size, so total volume depends only on row count.
Recall that the Joiner builds its cache from the master rows and streams detail rows past it.
Pipeline A (1,000 rows, about 100 KB) is far smaller than Pipeline B (1,000,000 rows, about 100 MB).
Making A the master minimizes cache memory and disk spill.
Sorted input does not change the rule that the smaller source should be the master.

Each option

ACorrect. With 1,000 rows, A gives the smallest master cache and the best join performance.
BIncorrect. Caching a million rows wastes memory and likely spills to disk, slowing the session.
CIncorrect. The Joiner caches only the master source; the detail source is streamed, not cached.
DIncorrect. Sorted input reduces caching overhead, but it does not make the larger source the better master.

Common trap: Some candidates believe the larger or 'driving' table should be the master, as in some database join conventions, which reverses the Joiner's caching logic.

In practice: When tuning slow sessions with heterogeneous joins, swapping the master and detail roles so the smaller source is cached often cuts cache size and run time dramatically.

Remember: In a Joiner, make the source with fewer rows the master.

Drafted with AI assistance and checked against the answer key.

Keep practicing

Take the free PR000041 practice test

Ten exam-style questions with answers and explanations, plus the exam facts and study guides.

Start the free practice test