IT Certifications · 1Z0-447

Oracle GoldenGate 12c Implementation Essentials Exam Practice Test

The Oracle GoldenGate 12c Implementation Essentials exam concerns configuring and operating database change-data replication. Its practice material samples tasks such as defining Extract and Replicat behavior, routing transaction records through trail files, mapping source data to target tables, and maintaining process recovery with checkpoints.

Exam overview

Exam providerOracle
Exam code1Z0-447
CategoryIT Certifications

About the Oracle GoldenGate 12c Implementation Essentials Exam

GoldenGate implementation work involves choosing how to capture database changes, manage local or remote trails, and deliver records to target systems. Administrators use parameter files to control process groups, select tables and transactions, and specify mappings; Extract configurations may use wildcards or filters to shape captured data. Data-pump Extracts can forward trail data between systems, while network reachability and trail sizing affect reliable delivery. Replicat configuration requires understanding trail input, MAP statements, and column correspondence when source and target schemas differ. Checkpoints record processing progress and support recovery after interruption. The available questions exercise recognition of these configuration choices and their operational purpose, including how components connect across a replication path.

Sample Practice Questions

Review a selection from this exam's published US Practice Tests practice bank.

Question 1

Which parameter-file setting is used to specify the trail file prefix from which a classic Replicat reads?

  1. AEXTTRAIL
  2. BRMTTRAIL
  3. CEXTFILE
  4. DEXTTRAILSOURCE
Show answerCorrect answer: D

EXTTRAILSOURCE identifies the input trail prefix for a classic Replicat. EXTTRAIL and RMTTRAIL are commonly used to define trail outputs for capture and pump processes.

Question 2

Which consideration is important when selecting a GoldenGate trail file size?

  1. ABalance file-management overhead against the size of individual files and operational needs
  2. BMake every trail file exactly the size of the database redo log
  3. CSet the size equal to the number of Replicat groups
  4. DChoose a size that prevents trail rollover
Show answerCorrect answer: A

Trail sizing is an operational choice: smaller files can increase file-management overhead, while larger files can affect handling and recovery workflows. Trail rollover is a normal mechanism and should not be disabled as a sizing goal.

Question 3

What is the purpose of a GoldenGate parameter-file wildcard such as TABLE HR.*; when used in an Extract configuration?

  1. AIt selects all matching tables in the HR schema for capture
  2. BIt excludes all tables whose names begin with HR
  3. CIt maps HR tables to a target schema automatically
  4. DIt enables DDL replication for every schema
Show answerCorrect answer: A

A TABLE rule identifies source objects for capture. A schema wildcard can select tables matching that schema pattern, subject to the applicable parameter syntax and any exclusions or filters configured.

Question 4

What is a key operational benefit of using a data-pump Extract between a local trail and a remote system?

  1. AIt can transfer captured trail data independently of the primary capture process
  2. BIt automatically resolves all conflicting updates at the target
  3. CIt replaces the need for a target Replicat
  4. DIt changes the source database character set
Show answerCorrect answer: A

A data pump reads a local trail and forwards records, often to a remote trail. This separation can help isolate network transfer from primary capture and can support routing or filtering configurations.

Question 5

Why might a GoldenGate administrator configure an Extract process to ignore a specific, known class of source transactions?

  1. ATo exclude changes that should not be replicated, when the selection criteria are well understood
  2. BTo make all target transactions commit before their source transactions
  3. CTo guarantee that a target can accept unsupported data types
  4. DTo eliminate the need for source transaction logging
Show answerCorrect answer: A

GoldenGate selection and filtering can exclude changes that are intentionally outside the replication scope. Filters must be designed carefully because excluded transactions will not be applied at the target; they do not change commit ordering or remove logging requirements.

Question 6

In a classic GoldenGate configuration, what is the purpose of a Replicat parameter file's MAP statement?

  1. ATo define source-to-target object mapping and related filtering or transformation rules
  2. BTo assign a TCP port to the Manager process
  3. CTo set the database archive log retention period
  4. DTo create a source database user
Show answerCorrect answer: A

MAP identifies source objects and their corresponding target objects. It can also be associated with options that control filtering and column mapping or transformation.

Question 7

What is the principal role of a GoldenGate parameter file for a process group?

  1. ADefine the process's configuration directives and behavior
  2. BStore every replicated row permanently
  3. CReplace the source database initialization file
  4. DAct as the network listener for all GoldenGate connections
Show answerCorrect answer: A

A parameter file contains directives that configure a process group, such as its input or output trail and the objects or operations it handles. It is not a data store or network listener.

How to use this practice test

Access is free. Each session presents up to 20 random questions from the 50-question practice bank, with results shown after the session. Use the questions to check your understanding of parameter-file settings, trail routing, table mapping, filtering, and checkpoint behavior; revisit any missed concepts in a GoldenGate configuration context.

Preparation tips

  • Trace a change from Extract capture through a local or remote trail to Replicat, noting each process group's role.
  • Practice reading parameter-file examples and identify how TABLE, MAP, wildcards, and transaction filters affect selected data.
  • Compare local-trail and data-pump designs; consider network connectivity and trail-file sizing in each topology.
  • Work through source-to-target mapping examples with differing column names, and identify how checkpoints support restart and recovery.
Official sourceOfficial exam page ↗