Application PDBs, SALES_APP1 and SALES_APP2, must be created and they must access common tables of the SALES_APP application. Examine these steps: 1. Install the SALES_APP application, including the…

Question

Options

• A3, 4, 1, 6, 8
• B2, 5, 6
• C1, 5, 6
• D1, 3, 5, 6, 7
• E1, 3, 5, 7

• A
  26% (7)
• B
  11% (3)
• C
  52% (14)
• D
  4% (1)
• E
  7% (2)

Explanation

Option C (steps 1, 5, 6) is correct because it covers the three essential actions in sequence: install the application and its common objects in the application root (the authoritative definition point), create the application PDBs, then sync those PDBs with the application root so they inherit the common tables - nothing more is needed for the minimum viable setup. The application seed (steps 3, 4, 7, 8) is entirely optional; it serves as a pre-configured template to speed up future PDB creation but is not required, which eliminates options A, D, and E. Option B fails because step 2 incorrectly places common tables in the CDB root - application-level common objects belong exclusively in the application root, not the CDB root, which would expose them to all PDBs across the entire CDB. Options D and E both include seed-related steps (3 and 7) that add unnecessary complexity, and E makes the additional mistake of syncing with the seed instead of the application root (step 6), which is where the authoritative application definition actually lives.

Memory tip: Remember the three-word formula - Define, Create, Sync: define the app in the application root (step 1), create the PDBs (step 5), sync the PDBs to the root (step 6). Any step involving a "seed" is always optional and never part of the minimum path.

No community discussion yet for this question.