PR000041 practice question 5 of 15

Which is the correct priority of assigning a mapping variable?

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

Which is the correct priority of assigning a mapping variable?

Answer options

Correct Answer:

A

Explanation

The Informatica Integration Service determines the start value for a mapping variable by following a specific order of precedence. Option A provides the most comprehensive sequence. The process begins with runtime overrides: values from a workflow parameter file are read, then overridden by a session parameter file if specified. A pre-session variable assignment provides a further, higher-priority override. If none of these runtime values are provided, the service uses the value saved in the repository from the previous successful session. If no repository value exists (e.g., on the first run), it uses the initial value declared in the mapping. The ultimate fallback is the default value for the variable's data type (e.g., 0 for a number).

Why Incorrect

B. This option is incomplete. It correctly orders the parameter files and repository/initial values but omits the pre-session assignment, which is a critical, high-precedence override mechanism.

C. This order is incorrect. The repository value has a lower priority than runtime configurations like parameter files and pre-session assignments, which can override it.

D. This option is highly incomplete. It only shows the lowest levels of the hierarchy and completely ignores the higher-precedence runtime overrides from parameter files and assignments.

References

1. Informatica PowerCenter 10.5

Advanced Workflow Guide

"Chapter 2: Workflow and Task Variables"

section on "Mapping Variable and Parameter Precedence".

This guide details the definitive order of precedence

stating that the Integration Service uses the following hierarchy to determine a variable's start value: 1. Pre-session variable assignment

2. Value in a parameter file

3. Value saved in the repository

4. Initial value

5. Datatype default value. This confirms that runtime assignments and files have precedence over repository and initial values.

2. Informatica PowerCenter 10.5

Workflow Basics Guide

"Chapter 10: Parameters and Variables in a Workflow"

section on "Parameter and Variable Precedence".

This document corroborates the hierarchy

explaining that values defined closer to the task execution (e.g.

in a session parameter file or pre-session assignment) override values defined at a more general level (e.g.

workflow parameter file or initial value). Option A

while slightly confusing in its ordering of the highest-priority items

lists the complete set of sources in a logical evaluation flow.

Question 5 of 15

Question breakdown

Tests: Mapping parameters and variables: start value precedence
Difficulty: Medium

Key idea: The Integration Service takes a mapping variable's start value from the highest-priority source available: parameter files, then pre-session assignment, then repository-saved value, then declared initial value, then datatype default.

How to reach the answer

Recall the core order: parameter file, then repository value, then initial value, then datatype default.
Add the runtime overrides: a workflow parameter file outranks a session parameter file, and pre-session variable assignments also sit above the persisted value.
Check each option for a repository value placed above parameter files. C does this, which is wrong.
Discard options that omit sources (B, D).
Only A includes every source in descending priority.

Each option

ACorrect. It lists all sources in descending priority, from parameter files and pre-session assignment down to the repository value, initial value, and default.
BIncorrect. It omits the pre-session assignment and datatype default, and it puts the session parameter file ahead of the workflow parameter file.
CIncorrect. It ranks the repository value above parameter files, but parameter files override persisted values.
DIncorrect. It lists only the lowest-priority fallbacks and ignores all runtime overrides.

Common trap: Because mapping variables persist their last value in the repository, people assume that saved value always wins. A parameter file value overrides it.

In practice: In incremental loads that use $$LastRunDate, developers override the persisted value with a parameter file to reprocess history. Otherwise they reset the value in the repository.

Remember: Parameter file beats repository value, which beats initial value, which beats datatype default.

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

More questions

Other PR000041 practice questions