Regarding space usage in temporary tablespaces, the following statements are true:
* A (Correct): When a global temporary table or a sort operation exceeds the available memory, Oracle Database allocates space in a temporary tablespace to store the temporary data or intermediate results.
* E (Correct): Using temporary tablespace groups can prevent insufficient temporary tablespace for sort operations by providing a collective pool of space from multiple temporary tablespaces, which can be used for user sorting operations.
The other options provided have inaccuracies:
* B (Incorrect): Oracle does not provide a mechanism for setting quotas on temporary tablespaces.
Quotas can be set for permanent tablespaces but not for temporary ones.
* C (Incorrect): A sort operation may fail due to insufficient space, but Oracle will attempt to allocate space in the temporary tablespace dynamically. If no space can be allocated, an error is returned rather than a sort failure.
* D (Incorrect): If a session consumes all available temporary tablespace storage, Oracle will not hang the session; it will return an error to the session indicating that it has run out of temporary space.
References:
* Oracle Database Administrator's Guide: Managing Space for Schema Objects
* Oracle Database Concepts: Temporary Tablespaces

Database services in Oracle are used to manage how resources are allocated and how workloads are managed within the database. The features that use database services are:
* B (Correct):Database Resource Manager (DBRM) uses services to control resource allocation to different workloads. It ensures that resources are assigned to the most critical tasks first, based on the service associated with the workload.
* E (Correct):Oracle Scheduler can also utilize database services. Jobs in Oracle Scheduler can be assigned to different services to control resource allocation and prioritization.
The other features mentioned are related to SQL performance but do not directly utilize database services in the way Resource Manager and Scheduler do:
* A:Oracle Automatic Reoptimization is a feature that allows the database to automatically improve the execution plan of a SQL statement after it is executed, based on the actual performance metrics, but it does not directly use database services.
* C:Oracle SQL Performance Management involves various components of SQL tuning and monitoring, but it does not use database services to operate.
* D:Oracle SQL Tuning Advisor provides advice on how to tune SQL queries for better performance.
While it can be used in conjunction with services for managing and analyzing workloads, it doesn't use services in its core functionality.
References:
* Oracle Database Administrator's Guide:Administering Services
* Oracle Database Administrator's Guide:Managing Resources with Oracle Database Resource Manager
* Oracle Database Scheduler Developer's Guide:Using the Scheduler

Regarding space usage in temporary tablespaces, the following statements are true:
* A (Correct):When a global temporary table or a sort operation exceeds the available memory, Oracle Database allocates space in a temporary tablespace to store the temporary data or intermediate results.
* E (Correct):Using temporary tablespace groups can prevent insufficient temporary tablespace for sort operations by providing a collective pool of space from multiple temporary tablespaces, which can be used for user sorting operations.
The other options provided have inaccuracies:
* B (Incorrect):Oracle does not provide a mechanism for setting quotas on temporary tablespaces. Quotas can be set for permanent tablespaces but not for temporary ones.
* C (Incorrect):A sort operation may fail due to insufficient space, but Oracle will attempt to allocate space in the temporary tablespace dynamically. If no space can be allocated, an error is returned rather than a sort failure.
* D (Incorrect):If a session consumes all available temporary tablespace storage, Oracle will not hang the session; it will return an error to the session indicating that it has run out of temporary space.
References:
* Oracle Database Administrator's Guide:Managing Space for Schema Objects
* Oracle Database Concepts:Temporary Tablespaces

When importing objects that used the In-Memory (IM) column store in their source database using Oracle Data Pump, the following statements are true:
* D (Correct):TheTRANSFORMclause can be used to alter object creation DDL during import operations. This can include adding theINMEMORYclause to tables that were not originally using the IM column store.
* F (Correct):The import operation can preserve theINMEMORYattributes of tables as they were at the time of export, effectively replicating the IM column store settings from the source database.
The other statements are not accurate in the context of Data Pump import:
* A (Incorrect):Data Pump does not give preference to the IM column store clauses at the tablespace level over table-level definitions unless explicitly specified by theTRANSFORMclause.
* B (Incorrect):While Data Pump can transport existingINMEMORYattributes, it is not mandatory. It is controlled by theINCLUDEorEXCLUDEData Pump parameters or theTRANSFORMclause.
* C (Incorrect):TheINMEMORY_CLAUSEparameter is not part of the Data Pump Export utility. To modify the IM column store clauses, you would use theTRANSFORMparameter during import, not export.
* E (Incorrect):Data Pump does not ignore the IM column store clause unless specifically instructed to do so via theEXCLUDEparameter.
References:
* Oracle Database Utilities:Data Pump Export
* Oracle Database Utilities:Data Pump Import

TheDBMS_WORKLOAD_REPOSITORY.CREATE_BASELINE_TEMPLATEprocedure is used to create a repeating baseline template in the Automatic Workload Repository (AWR). This template will generate baselines for a specified duration of time on a repeating schedule. Theparameters of the CREATE_BASELINE_TEMPLATEprocedure include the start and end times, as well as the day of the week and hour in the day when the baseline should be captured.
Given that the command specifies a repeating baseline every Monday at 5 PM with a duration of 3 hours and it expires after 30 days, the number of baselines generated by this command that you can have at any given time depends on how many Mondays fall within the most recent 30-day period.
Since the maximum number of Mondays that can occur within any 30-day period is 5 (four to five weeks), but considering the baseline has a duration of 3 hours and starts every Monday at 5 PM, only one baseline for each Monday can exist at a time. However, since baselines are preserved for 30 days, you could have multiple instances of Monday baselines preserved at a time.
* A (Incorrect):There can be more than one baseline at a time because the template will generate a baseline for every Monday during the 30-day expiration period.
* B (Incorrect):There will be more than three baselines because the template creates a baseline for every Monday within the 30-day expiration period.
* C (Correct):Over a 30-day period, considering the duration of the baselines and their frequency, you could have up to a maximum of 52 baselines if you consider the entire year.
* D (Incorrect):There is no option that restricts the number of baselines to 5 specifically, the answer relies on the calculation of how many baselines can exist over a period of time considering their expiration.
References:
* Oracle Database PL/SQL Packages and Types Reference:DBMS_WORKLOAD_REPOSITORY