多选题Which three statements are true concerning the multitenant architecture?（）AEach pluggable database (PDB) has its own set of background processes.BA PDB can have a private temp tablespace.CPDBs can share the sysaux tablespace.DLog switches occur only at

All administration tasks must be done to a specific pluggable database.

The pluggable databases increase patching time.

The pluggable databases reduce administration effort.

The pluggable databases are patched together.

Pluggable databases are only used for database consolidation.

Schema objects owned by the C# # A_ADMIN common user can be shared across all PDBs.

The C # # A_ADMIN user will be able to use the TEMP_TS temporary tablespace only in root.

The command will, create a common user whose description is contained in the root and each pdb.

The schema for the common user C # # A_ADMIN can be different in each container.

The command will create a user in the root container only because the container clause is not used

The root container can be flashed back without flashing back the pluggable databases (PDBs).

To enable flashback database, the CDB must be mounted.

Individual PDBs can be flashed back without flashing back the entire cdb.

The DB_FLASHBACK RETENTION_TARGET parameter must be set to enable flashback of the cdb.

A CDB can be flashed back specifying the desired target point in time or an SCN, but not a restore point.

The PDB must be open in read-only mode.

The PDB must be in mount state.

The PDB must be unplugged.

The PDB data files are always removed from disk.

A dropped PDB can never be plugged back into a multitenant container database (CDB).

It succeeds because the PDB_ADMIN user has the required privileges.

It fails because common users are unable to use the SET CONTAINER statement.

It fails because local users are unable to use the SET CONTAINER statement.

If fails because the SET CONTAINER statement cannot be used with PDB$SEED as the target pluggable database (PDB).

If no PDB plan is enabled for a pluggable database, then all sessions for that PDB are treated to an equal degree of the resource share of that pdb.

In a PDB plan, subplans may be used with up to eight consumer groups.

If a PDB plan is enabled for a pluggable database, then resources are allocated to consumer groups across all PDBs in the cdb.

If no PDB plan is enabled for a pluggable database, then the PDB share in the CDB plan is dynamically calculated.

If a PDB plan is enabled for a pluggable database, then resources are allocated to consumer groups based on the shares provided to the PDB in the CDB plan and the shares provided to the consumer groups in the PDB plan.

Multitenant architecture can be deployed only in a Real Application Clusters (RAC) configuration.

Multiple pluggable databases (PDBs) share certain multitenant container database (CDB) resources.

Multiple CDBs share certain PDB resources.

Multiple non-RAC CDB instances can mount the same PDB as long as they are on the same server.

Patches are always applied at the CDB level.

A PDB can have a private undo tablespace.

The PDB must be open in read only mode.

The PDB must be dosed.

The unplugged PDB becomes a non-cdb.

The unplugged PDB can be plugged into the same multitenant container database (CDB)

The unplugged PDB can be plugged into another cdb.

The PDB data files are automatically removed from disk.

Each pluggable database (PDB) has its own set of background processes.

A PDB can have a private temp tablespace.

PDBs can share the sysaux tablespace.

Log switches occur only at the multitenant container database (CDB) level.

Different PDBs can have different default block sizes.

PDBs share a common system tablespace.

Instance recovery is always performed at the CDB level.

BACKUP PLUGGABLE DATABASE PDB1 while connected to the root container

BACKUP PLUGGABLE DATABASE PDB1 while connected to the PDB1 container

BACKUP DATABASE while connected to the PDB1 container

BACKUP DATABASE while connected to the boot container

BACKUP PLUGGABLE database PDB1 while connected to PDB2

System privileges apply only to the PDB in which they are used.

Local users cannot use local system privileges on the schema of a common user.

The granter of system privileges must possess the set container privilege.

Common users connected to a PDB can exercise privileges across other PDBs.

System privileges with the with grant option container all clause must be granted to a common user before the common user can grant privileges to other users.

ALTER PLUGGABLE DATABASE OPEN ALL ISSUED from the root

ALTER PLUGGABLE DATABASE OPEN ALL ISSUED from a pdb

ALTER PLUGGABLE DATABASE PDB OPEN issued from the seed

ALTER DATABASE PDB OPEN issued from the root

ALTER DATABASE OPEN issued from that pdb 

ALTER PLUGGABLE DATABASE PDB OPEN issued from another pdb

ALTER PLUGGABLE DATABASE OPEN issued from that pdb

SYSTEM

SYSAUX

EXAMPLE

UNDO

TEMP

USERS