You plan to perform cross-platform PDB transport using XTTS. Which two are true?

Question

Options

• AAutomatic conversion of endianess occurs.
• BThe source and target platforms must have the same endianess.
• CThe source PDB can be in MOUNT or OPEN state.
• DThe source PDB must not be an application root.
• EThe source PDB must be in MOUNT state.
• FA backup of the PDB must exist, taken using the BACKUP command with the To PLATFORM

• A
  3% (1)
• B
  88% (29)
• E
  3% (1)
• F
  6% (2)

Explanation

When performing cross-platform PDB transport using XTTS (Cross-Platform Transportable Tablespace via Incremental Backups), the method relies on applying incremental backups incrementally - a technique that requires the data blocks to be in the same byte format throughout. This means B is correct: unlike the traditional RMAN CONVERT approach, XTTS does not perform endianness conversion, so both platforms must share the same endianness (e.g., both little-endian). C is correct because the source PDB can be either in MOUNT state (offline) or OPEN READ ONLY state - both allow consistent data capture for transport.

Why the distractors are wrong:

• A - Endianness conversion is not automatic in XTTS; that's a key limitation distinguishing it from traditional cross-platform transportable tablespaces using RMAN CONVERT.
• D - Application roots are not excluded from XTTS transport; this restriction doesn't exist.
• E - Too restrictive; OPEN READ ONLY is also a valid state, so requiring only MOUNT is incorrect.
• F - The BACKUP ... TO PLATFORM clause belongs to the traditional cross-platform transportable tablespace flow, not XTTS, which uses incremental backups instead.

Memory tip: Think of XTTS as "Same Bytes, Two States" - same endianness required (no conversion magic), and the PDB can be in one of two valid states: MOUNT or READ ONLY OPEN.

No community discussion yet for this question.