Which two statements are true about the tools used to configure Oracle Net Services?
Correct Answer: B,D
A .False. lsnrctl can start a default listener without listener.ora. B .True. EMCC provides centralized Net Services configuration. C .False. NetCA can run standalone, not just during installation. D .True. Net Manager configures local naming (e.g., TNSNAMES.ORA). E .False. Net Manager is local, not centralized like EMCC.
Question 27
Which statement is true about the PDB_DBA role granted to a local user during the creation of a new PDB?
Correct Answer: A
A .True. PDB_DBA grants admin rights (e.g., CREATE SESSION, ALTER SYSTEM) within the PDB. B .False. DDL on objects requires ownership or explicit grants. C .False. User management needs CREATE USER privilege, not inherent. D .False. It includes multiple privileges, not none.
Question 28
Which two statements are true concerning logical and physical database structures?
Correct Answer: A,C
False. All blocks in a segment use the tablespace's block size (e.g., 8KB). While a database can have tablespaces with different block sizes (e.g., 8KB, 32KB), a single segment's blocks are uniform, as it resides in one tablespace. Explanation: Logical structures (e.g., segments, extents) map to physical structures (e.g., data files, blocks). Let's dissect each option: A : A segment can span multiple data files in some tablespaces. True. A segment (e.g., a table or index) is a logical entity stored in a tablespace. In a smallfile tablespace (default in Oracle), a segment's extents can span multiple data files if the tablespace has multiple files and space allocation requires it. This is common in large tables or when autoextend adds new files. Mechanics:Oracle allocates extents across available data files in a round-robin fashion (with ASSM) or as needed, ensuring the segment's data is distributed. This doesn't apply to bigfile tablespaces, which use a single data file. Example:A 10GB table in a tablespace with two 5GB data files will span both. B : Segments can span multiple tablespaces. False. A segment is confined to a single tablespace. Oracle enforces this to maintain logical separation (e.g., a table's data stays in its assigned tablespace). Partitioned tables can have partitions in different tablespaces, but each partition is a separate segment. Why Not:The segment header and extent map reside in one tablespace, preventing cross-tablespace spanning for a single segment. C : A segment might have only one extent. True. A segment starts with one extent upon creation (e.g., a small table or index). If no further growth occurs, it remains a single-extent segment. This is common with small objects or when INITIAL extent size suffices. Mechanics:In locally managed tablespaces (default), the initial extent is allocated based on INITIAL or tablespace defaults (e.g., 64KB), and additional extents are added only as needed. D : All tablespaces may have one or more data files. False. Bigfile tablespaces are restricted to one data file (up to 128TB). Smallfile tablespaces (traditional) can have multiple data files (up to 1022), but the "all" phrasing makes this false due to bigfile exceptions. Clarification:The question's intent may assume smallfile tablespaces, but Oracle 23ai supports both types.
Question 29
Which three relationships between instances and Oracle databases are possible without using Multi-tenant?
Correct Answer: B,D,E
A .False. One instance can't mount multiple DBs without multitenant. B .True. RAC allows multiple instances to share one DB. C .False. Same as A; not possible without CDB. D .True. An instance can start in NOMOUNT with no DB. E .True. Standard single-instance configuration.
Question 30
Examine this command: ALTER DATABASE MOVE DATAFILE '\u01/sales1.dbf' TO '\u01/sales01.dbf' REUSE; Which two statements are true?
Correct Answer: A,D
This command moves/renames a data file online. Let's evaluate: A . DML may be performed on tables with one or more extents in this data file during the execution of this command. True. Introduced in 12c and refined in 23ai, MOVE DATAFILE is an online operation, allowing DML (e.g., INSERT, UPDATE) on tables within the file. Oracle ensures consistency via redo and undo. Mechanics:The file is copied to the new location/name while tracking changes, then switched atomically. Practical Use:Minimizes downtime in production systems. B . If Oracle Managed Files (OMF) is used, then the file is renamed but moved to DB_CREATE_FILE_DEST. False. With OMF, omitting the TO clause would place the file in DB_CREATE_FILE_DEST, but here, TO '\u01/sales01.dbf' explicitly specifies the target, overriding OMF defaults. Mechanics:OMF only applies if the destination is unspecified (e.g., MOVE DATAFILE ... without TO). Why Incorrect:Explicit path trumps OMF behavior. C . The tablespace containing SALES1.DBF must be altered READ ONLY before executing the command. False. READ ONLY isn't required; the operation is online and supports active use. Why Incorrect:Conflicts with Oracle's online move feature. D . The file is renamed and stored in the same location. True. The command renames /u01/sales1.dbf to /u01/sales01.dbf (correcting \u01 to /u01 as a Windows/Unix typo), keeping it in /u01/. REUSE allows overwriting if sales01.dbf exists. Mechanics:File is copied and renamed in-place within the same filesystem directory. E . The tablespace containing SALES1.DBF must be altered OFFLINE before executing the command. False. Offline mode isn't needed; the online move handles activetablespaces.
