Examine this configuration and requirement: 1. The hr user created a private database link in the pdb2 pluggable database linking to the hr schema in the PDBl pluggable database. 2. Other users in…

Question

Options

• AOnly grant other users access to the HR.EMPLOYEES table In the pdb2 pluggable database.
• BGrant other users access to the database link in the PDBI pluggable database.
• CGrant access to the view of the remote HR.EMPLOYEES table In the PDB2 pluggable database.
• DGrant other users access to the database link In the PDB2 pluggable database.
• ECreate a view In the HR schema for the remote hr. employees table of the pdb2 pluggable

• A
  3% (1)
• B
  13% (5)
• C
  5% (2)
• D
  79% (31)

Explanation

D and E work together because a private database link is owned solely by the user who created it (hr), meaning other users cannot use it directly. The solution is to create a view in the HR schema within PDB2 that wraps the remote table access via the link (E), then grant other users in PDB2 the privilege to query through that database link/view (D) - keeping everything scoped to PDB2 where the link lives.

Why the distractors fail:

• A is wrong because granting access to HR.EMPLOYEES in PDB2 gives access to a local table, not the remote one in PDB1.
• B is wrong because the database link was created in PDB2, not PDB1; granting something in PDB1 does nothing for users in PDB2.
• C is wrong (or redundant) because granting access to a view without first creating one (E) accomplishes nothing - E must come first, making C an incomplete or misplaced option.

Memory tip: Think "Private = Build a Bridge, Grant Locally." A private database link needs a view as a bridge (E) built in the same PDB where the link lives, and the grant must happen in that same PDB (D) - never from the remote side.

No community discussion yet for this question.