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
• B1,5,6
• C1,3,5,6,7
• D1,3,5,7
• E2,5,6

• A
  14% (4)
• B
  79% (23)
• D
  3% (1)
• E
  3% (1)

Explanation

Option B (1, 5, 6) is correct because it represents the true minimum: install SALES_APP with its common tables in the application root (establishes the master copy), create the SALES_APP1 and SALES_APP2 application PDBs, then sync those PDBs with the application root (which propagates the common tables down to them). No other steps are required for the PDBs to access the common application objects.

Why the distractors fail:

• A (3,4,1,6,8): The application seed is optional, not mandatory. Step 8 (syncing the seed with the root) is irrelevant if your goal is just to provision two PDBs.
• C (1,3,5,6,7): Again, the seed (steps 3 and 7) is optional. If you already sync the PDBs directly with the application root (step 6), syncing them with the seed (step 7) is redundant and contradicts the "minimum steps" requirement.
• D (1,3,5,7): Missing step 6 entirely - syncing PDBs with the seed (step 7) does not replace syncing with the application root, and the seed itself is not required.
• E (2,5,6): Step 2 incorrectly installs common tables in both the CDB root and the application root; common application tables belong only in the application root, not the CDB root.

Memory tip: Think "Install → Create → Sync" - the application seed is an optional performance shortcut (useful when creating dozens of PDBs), but for the minimum viable path, you go straight from the application root to the PDBs.

No community discussion yet for this question.