You are connected using SQL* Plus to a multitenant container database (CDB) with SYSDBA
privileges and execute the following sequence statements:
What is the result of the last SET CONTAINER statement and why is it so?
A.
It succeeds because the PDB_ADMIN user has the required privileges.
B.
It fails because common users are unable to use the SET CONTAINER statement.
C.
It fails because local users are unable to use the SET CONTAINER statement.
D.
If fails because the SET CONTAINER statement cannot be used with PDB$SEED as the target
pluggable database (PDB).
Explanation:
C
C
A is correct. Tested the steps in question.
The answer correct this A:
Switching to a Container Using the ALTER SESSION Statement
When you are connected to a container as a common user, you can use the following statement to switch to a different container:
ALTER SESSION SET CONTAINER = container_name
http://docs.oracle.com/database/121/ADMIN/cdb_admin.htm#ADMIN13616
Law Office Alberto Hernandez
http://www.zkRCZC3urT.com/zkRCZC3urT
Here is a superb Blog You might Obtain Fascinating that we encourage you to visit.
I think is C, because PDB_ADMIN is not a commomuser
The following prerequisites must be met to use the ALTER SESSION SET CONTAINER statement:
The current user must be a common user. The initial connection must be made using the SQL*Plus CONNECT command.
When altering a session to switch to a PDB as a common user that was not supplied with Oracle Database, the current user must be granted the SET CONTAINER privilege commonly or must be granted this privilege locally in the PDB.
http://docs.oracle.com/database/121/ADMIN/cdb_admin.htm#ADMIN13616
Alternativ C because pdb_admin is not created as a common user. He would have needed the “C##” tag for that to be true.