Examice

Exam 1z0-083 All QuestionsBrowse all questions from this exam

Question 169

Which two are true about Lockdown profiles in a container database (CDB) and its pluggable databases (PDBs)? (Choose two.)

A Lockdown profile created from a base Lockdown profile is always automatically modified if the profile on which it is based is modified.

A PDB Lockdown profile can be created in an application root.

A Lockdown profile created from a base Lockdown profile is never automatically modified if the profile on which it is based is modified.

A PDB Lockdown profile can be created in CDB$ROOT.

A PDB Lockdown profile can be created in a regular PDB.

Correct Answer: B, D

A PDB Lockdown profile can be created in an application root because it allows the lockdown profile to be applied to the application root and to all PDBs in the application container. Additionally, a PDB Lockdown profile can be created in CDB$ROOT, which allows the lockdown profile to apply to all PDBs in the entire CDB. This ensures that necessary restrictions or permissions can be uniformly enforced across multiple pluggable databases.

Discussion

frankkkOptions: BD

BD correct https://docs.oracle.com/en/database/oracle/oracle-database/19/sqlrf/CREATE-LOCKDOWN-PROFILE.html#GUID-1CDEC3A3-F3F1-4279-9370-36AACF416E0A

jackymak

B: If you set PDB_LOCKDOWN while connected to an application root, then the lockdown profile applies to the application root and all PDBs in the application container. D: If you set PDB_LOCKDOWN while connected to a CDB root, then the lockdown profile applies to all PDBs in the CDB. It does not apply to the CDB root.

ilputtoOptions: BD

as per documentation, lockdown profiles can be created in cdb$root and application root.

antonicaOptions: AC

E is false. SQL> CREATE LOCKDOWN PROFILE app_root_prof2; CREATE LOCKDOWN PROFILE app_root_prof2 * ERROR at line 1: ORA-65040: operation not allowed from within a pluggable database

gedde

for me B , D and E are all correct according to documentation? https://docs.oracle.com/en/database/oracle/oracle-database/19/sqlrf/CREATE-LOCKDOWN-PROFILE.html#GUID-1CDEC3A3-F3F1-4279-9370-36AACF416E0A why is E incorrect ?

greenday5494Options: BE

confused, it can be created in app root, CDB Root, and specific PDBs as per documentation: If you set PDB_LOCKDOWN while connected to a particular PDB, then the lockdown profile applies to that PDB and overrides the lockdown profile for the CDB or application container, if one exists.

greenday5494

https://docs.oracle.com/en/database/oracle/oracle-database/19/sqlrf/CREATE-LOCKDOWN-PROFILE.html#GUID-1CDEC3A3-F3F1-4279-9370-36AACF416E0A "When a lockdown profile is assigned to a PDB, users in that PDB cannot perform the operations that are the disabled for the profile. To assign a lockdown profile, set its name for the value of the PDB_LOCKDOWN initialization parameter. You can assign a lockdown profile to individual PDBs, or to all PDBs in a CDB or application container, as follows:"

_gio_Options: BD

https://docs.oracle.com/en/database/oracle/oracle-database/19/sqlrf/CREATE-LOCKDOWN-PROFILE.html#GUID-1CDEC3A3-F3F1-4279-9370-36AACF416E0A

hilaireOptions: BD

BD correct

vkra

https://blogs.oracle.com/database/post/a-simple-guide-to-lockdown-profiles