Your SALES_ROOT application container has two application PDBs.
The SALES_APP application has a common table, FIN.REVENUE, in the two PDBs.
Examine this query and its output:
Which two are true? (Choose two.)
Your SALES_ROOT application container has two application PDBs.
The SALES_APP application has a common table, FIN.REVENUE, in the two PDBs.
Examine this query and its output:
Which two are true? (Choose two.)
The CONTAINERS_DEFAULT attribute is not enabled for the REVENUE table, which implies that data in different PDBs will not be automatically pruned based on container maps. The MAPTABLE table defines a logical partition key on a commonly used column for the REVENUE table, helping those queries that use container maps to fetch results efficiently based on application PDBs.
C and F are correct. Tested in lab with exact same setting like in the output shown. A. -> incorrect - The CONTAINERS clause can be used. B. -> incorrect - It can be also a range based. C. -> CORRECT - https://docs.oracle.com/en/database/oracle/oracle-database/19/multi/administering-application-containers-with-sql-plus.html#GUID-AAF93A02-7C70-4024-8758-E351C213543E D. -> incorrect - Regular table E. -> incorrect - shown in the output CONTAINER_MAP = YES F. -> CORRECT - because CONTAINERS_DEFAULT is not enabled for the revenue table.
Because of what I can read from your link: "A container map can define a logical partition key on a column for a common object. " It seems to me that C is false! And the full statement is true if you invert the 2 object names! :-) MAPTABLE has CONTAINER_MAP=NO REVENUE has CONTAINER_MAP=YES
CF but michael_live reason for F is incorrect.
C F, thanks michael_live
Seems D is also correct SQL> select containers_default, container_map, container_map_object, table_name from DBA_TABLES where table_name='CONTAINERMAP'; CON CON CON --- --- --- TABLE_NAME -------------------------------------------------------------------------------- NO NO YES CONTAINERMAP SQL> select SHARING from dba_objects where OBJECT_NAME='CONTAINERMAP' and OBJECT_TYPE='TABLE'; SHARING ------------------ METADATA LINK
C and E -Use a container map to partition the data in metadata-linked objects. Container maps partition data in application PDBs based on a commonly-used column. -The map object is the partitioned table. The names of the partitions in the map table match the names of the application PDBs in the application container. The metadata-linked object is not physically partitioned at the table level, but it can be queried using the partitioning strategy used by the container map. -In addition, you can enable the CONTAINERS_DEFAULT attribute for a table or view in an application root. When this attribute is enabled, the CONTAINERS clause is used for queries and DML statements on the database object by default, and the CONTAINERS clause does not need to be specified in the SQL statements. To enable the CONTAINERS_DEFAULT attribute for a table or view in an application root, run the an ALTER TABLE or ALTER VIEW statement with the ENABLE CONTAINERS_DEFAULT clause. https://docs.oracle.com/en/database/oracle/oracle-database/19/multi/administering-application-containers-with-sql-plus.html#GUID-AAF93A02-7C70-4024-8758-E351C213543E
i mean C and F
For C. see my comment in reply to "michael_live" For D. See decoben415... comment below. For F. see comment from michael_live
based on this: container_map (yes) and containers_default (yes), when used together, allow, container_map to prune the partitions and therefore the application pdbs, based on the key that is passed to the query correct answers are: c,f
sorry E is wrong.. The object is enabled
C and E as the Map_table is not enabled . The container_map column shows "NO"