[Jan-2026] Oracle 1Z0-084 Exam Basic Questions With Answers [Q26-Q41]

[Jan-2026] Oracle 1Z0-084 Exam: Basic Questions With Answers

New 2026 Realistic Free Oracle 1Z0-084 Exam Dump Questions and Answer

Oracle 1Z0-084 certification exam is a comprehensive test that covers a wide range of topics related to Oracle Database 19c performance and tuning. 1Z0-084 exam consists of 75 multiple-choice questions that must be completed within 120 minutes. 1Z0-084 exam is computer-based and can be taken at authorized testing centers worldwide.

 

NEW QUESTION # 26
Examine this command:

What is the maximum number of baselines generated by this command that you can have at any given time?

• A. 0
• B. 1
• C. 2
• D. 3

Answer: C

Explanation:
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

NEW QUESTION # 27
Examine this code block, which executes successfully:
DBMS_SERVER_ALERT. SET_THRESHOLD (
DBMS_SERVER_ALERT.CPU_TIME_PER_CALL, DBMS_SERVER_ALERT. OPERATOR_GE, '8000', DBMS_SERVER_ALERT.OPERATOR_GE, '10000', 1, 2, 'inst1', DBMS_SERVER_ALERT.OBJECT_TYPE_SERVICE, 'main.regress.rdbms.dev.us.example.com') ;

What will happen?

• A. A warning alert will be issued when CPU time exceeds 1 minute for each user call.
• B. A critical alert will be issued when CPU time exceeds 2 minutes for each user call.
• C. A warning alert will be issued only when CPU time exceeds 10000 microseconds for each user call.
• D. A critical alert will be issued when CPU time exceeds 10000 microseconds for each user call.

Answer: D

Explanation:
In the provided code block, theDBMS_SERVER_ALERT.SET_THRESHOLDprocedure is used to set alert thresholds for the CPU time per call in Oracle Database. This procedure is a part of Oracle's Database Server Alert system, which monitors various metrics and generates alerts when certain thresholds are exceeded.
The parameters passed to theSET_THRESHOLDprocedure are as follows:
* The first parameterDBMS_SERVER_ALERT.CPU_TIME_PER_CALLspecifies the metric for which the threshold is being set, in this case, the CPU time consumed per database call.
* The second and third parametersDBMS_SERVER_ALERT.OPERATOR_GEand'8000'specify the warning threshold level and its value, respectively. However, these are not relevant to the answer as they are overridden by the critical threshold settings.
* The fourth and fifth parametersDBMS_SERVER_ALERT.OPERATOR_GEand'10000'set the critical threshold level and its value. This means that a critical alert will be generated when the CPU time per call exceeds 10000 microseconds.
* The remaining parameters specify the warning and critical alert intervals, the instance name, the object type, and the service name. These are not directly relevant to the behavior described in the options.
Thus, the correct answer is B, as the critical threshold for CPU time per call is set to 10000 microseconds, and the system is configured to issue a critical alert when this threshold is exceeded.
References:
* Oracle Database 19c documentation on theDBMS_SERVER_ALERT.SET_THRESHOLDprocedure, which details the parameters and usage of this procedure for setting alert thresholds within Oracle Database monitoring system.
* Oracle Database Performance Tuning Guide, which provides best practices and methodologies for monitoring and tuning Oracle Database performance, including the use of server alerts and thresholds.

NEW QUESTION # 28
Which two options are part of a Soft Parse operation?

• A. SQL Optimization
• B. Semantic Check
• C. Shared Pool Memory Allocation
• D. Syntax Check
• E. SQL Row Source Generation

Answer: B

NEW QUESTION # 29
Which statement is true about DB time in V$$YS_TIME_MODEL?

• A. DB time can be many times greater than the elapsed time since the database instance started.
• B. DB time is organized as a simple list of statistics and any time period is attributable to only one statistic.
• C. DB time includes the time spent executing the RMAN backup and restore command.
• D. DB tine excludes the time spent waiting for a CPU in the operating system run queue.

Answer: A

Explanation:
DB time includes the time spent on user and background processes. It can be greater than the elapsed time because it accumulates the active time of all the processes. For example, if two sessions are each active for 2 seconds at the same time, DB time would accumulate 4 seconds, while the elapsed time would be only 2 seconds.References:
* Oracle Database Performance Tuning Guide, 19c
* Oracle Database Reference, 19c

NEW QUESTION # 30
You must configure and enable Database Smart Flash Cache for a database.
You configure these flash devices:

Examine these parameter settings:

What must be configured so that the database uses these devices for the Database Smart Flash Cache?

• A. Set DB_FLASH_CACHE_SIZE parameter to 128G, 64G.
• B. Set DB_FLASH_CACHE_SIZE to 256G and change device /dev/sdk to 128G.
• C. Disable Automatic Memory Management and set SGA_TARGET to 256G.
• D. Set DB_FLASH_CACHE_SIZE parameter to 192G.
• E. Set DB_FLASH_CACHE_SIZE to 192G and MEMORY_TARGET to 256G.

Answer: A

Explanation:
To configure and enable Database Smart Flash Cache, you must set the DB_FLASH_CACHE_SIZE parameter to reflect the combined size of the flash devices youintend to use for the cache. In this scenario, two flash devices are configured: /dev/sdj with 128G and /dev/sdk with 64G.
* Determine the combined size of the flash devices intended for the Database Smart Flash Cache. In this case, it's 128G + 64G = 192G.
* However, Oracle documentation suggests setting DB_FLASH_CACHE_SIZE to the exact sizes of the individual devices, separated by a comma when multiple devices are used.
* Modify the parameter in the database initialization file (init.ora or spfile.ora) or using an ALTER SYSTEM command. Here's the command for altering the system setting:
ALTER SYSTEM SET DB_FLASH_CACHE_SIZE='128G,64G' SCOPE=SPFILE;
* Since this is a static parameter, a database restart is required for the changes to take effect.
* Upon database startup, it will allocate the Database Smart Flash Cache using the provided sizes for the specified devices.
It is important to note that MEMORY_TARGET and MEMORY_MAX_TARGET parameters should be configured independently of DB_FLASH_CACHE_SIZE. They control the Oracle memory management for the SGA and PGA, and do not directly correlate with the flash cache configuration.
References
* Oracle Database 19c Documentation on Database Smart Flash Cache
* Oracle Support Articles and Community Discussions on DB_FLASH_CACHE_SIZE Configuration

NEW QUESTION # 31
You need to transport performance data from a Standard Edition to an Enterprise Edition database. What is the recommended method to do this?

• A. Export the data by using the exp utility and parameter file spuexp.par from the Statspack repository and import it by using imp into a dedicated Statspack schema on the destination.
• B. Export the data by using the expdp utility and parameter file spuexp.par from the Statspack repository and import it by using impdp into Export the data by using expdp from the Statspack repository and import it by using impdp into the AWR repository.
• C. Export the data by using expdp from the ftatspack repository and import it by using impdp into the AWR repository.
• D. Export the data by using expdp from Statspack and import it by using $ORACLE_HOME/rdbms/admin
  /awrload into the AWR repository.

Answer: A

Explanation:
To transport performance data from an Oracle Database Standard Edition, which uses Statspack, to an Enterprise Edition database, which uses AWR, you must consider the compatibility of data structures and repository schemas between these tools. The recommended method is:
* D (Correct): Export the data using the exp utility with a parameter file appropriate for Statspack (like spuexp.par) from the Statspack repository and import it into a dedicated Statspack schema on the destination. Since Statspack and AWR use different schemas, it's not recommended to import Statspack data directly into the AWR repository.
The other options are incorrect because:
* A (Incorrect): expdp is not designed to export from Statspack, and awrload is intended for loading from an AWR export file, not a Statspack export.
* B (Incorrect): Although expdp and impdp are used for exporting and importing data, the AWR repository schema is different from the Statspack schema, so importing Statspack data directly into the AWR repository is not recommended.
* C (Incorrect): Using expdp to export from Statspack and then importing directly into the AWR repository is not the correct approach due to the schema differences between Statspack and AWR.
References:
* Oracle Database Performance Tuning Guide: Migrating from Statspack to AWR

NEW QUESTION # 32
Examine this AWRreport excerpt:

You must reduce the impact of database I/O, without increasing buffer cache size and without modifying the SQL statements.
Which compression option satisfies this requirement?

• A. STORE COMPRESS
• B. COLUMN STORE COMPRESS FOR QUERY HIGH
• C. ROW STORE COMPRESS ADVANCED
• D. MN STORE COMPRESS FOR QUERY LOW

Answer: C

Explanation:
To reduce the impact of database I/O without increasing the size of the buffer cache and without modifying SQL statements, you can use table compression. Among the given options,ROW STORE COMPRESS ADVANCEDis the most suitable form of table compression to satisfy this requirement.
Advanced row compression (ROW STORE COMPRESS ADVANCED) is designed to work well with all supported types of data, whether it's OLTP or data warehouse environments. It offers a higher level of compression than basic table compression (ROW STORE COMPRESS BASIC)without significant overhead during DML operations. This feature can help reduce the amount of I/O required to retrieve data by storing it more efficiently on disk.
* A, B, D:WhileCOLUMN STORE COMPRESS FOR QUERY HIGHandROW STORE
COMPRESSare both valid compression types,COLUMN STORE COMPRESS FOR QUERY
* HIGHapplies to the In-Memory column store and is not available in all versions and editions, andROW STORE COMPRESSis less advanced thanROW STORE COMPRESS ADVANCED.
References:
* Oracle Database Concepts Guide:Table Compression
* Oracle Database Performance Tuning Guide:Row Compression

NEW QUESTION # 33
The CURS0R_SHARING and OPTIMIZER_CAPTURE_SQL_PLAN_BASELINES parameters are set to default. The top five wait events in an awr report are due to a large number of hard parses because of several almost identical SQL statements.
Which two actions could reduce the number of hard parses?

• A. Create the RECYCLE cache and cache tables accessed by the SQL statements.
• B. Set the CURSOR_SHARING parameter to FORCE.
• C. Increase the size of the library cache.
• D. Create the KEEP cache and cache tables accessed by the SQL statements.
• E. Set OPTIMIZER_CAPTURE_SQL_PLAN_BASELINESto TRUE.

Answer: B,C

Explanation:
To reduce the number of hard parses due to several almost identical SQL statements, you can take the following actions:
* C (Correct):Increasing the size of the library cache can help reduce hard parses by providing more
* memory to store more execution plans. This allows SQL statements to be shared more effectively.
* E (Correct):Setting theCURSOR_SHARINGparameter toFORCEwill cause Oracle to replace literals in SQL statements with bind variables, which can significantly reduce the number of hard parses by making it more likely that similar SQL statements will share the same execution plan.
The other options do not directly impact the number of hard parses:
* A (Incorrect):Creating the KEEP cache and caching tables accessed by the SQL statements can improve performance for those tables, but it does not directly reduce the number of hard parses.
* B (Incorrect):Creating the RECYCLE cache and caching tables accessed by the SQL statements can make it more likely that objects will be removed from the cache quickly, which does not help with hard parse issues.
* D (Incorrect):SettingOPTIMIZER_CAPTURE_SQL_PLAN_BASELINEStoTRUEcan help stabilize SQL execution plans but will not reduce the number of hard parses. This parameter is used to automatically capture SQL plan baselines for repeatable SQL statements, which can prevent performance regressions due to plan changes.
References:
* Oracle Database Performance Tuning Guide:Minimizing Hard Parses
* Oracle Database SQL Tuning Guide:CURSOR_SHARING

NEW QUESTION # 34
A database instance is suffering poor I/O performance on two frequently accessed large tables.
No Big Table caching occurs in the database.
Examine these parameter settings:

Which are two actions either one of which will allow Big Table caching to occur?

• A. Increasing DB_CACHESIZE to 1 G
• B. Increasing DB_BIG_TABLE_CACHE_PERCENT_TARGET to at least 50
• C. Setting PARALLEL_DEGREE_POLICYAUTO
• D. Setting PARALLEL_DEGREE_POLICYADAPTIVE
• E. Increasing DB_BIG_TABLE_CACHE_PERCENT_TARGET to at least 25
• F. Setting DB_KEEP_CACHE_SIZE to at least 50M

Answer: A,E

Explanation:
Big Table caching is a feature that allows frequently accessed large tables to be cached in memory to improve I/O performance. From the parameter settings provided, Big Table caching is not occurring because DB_BIG_TABLE_CACHE_PERCENT_TARGETis set to 10, which is the minimum threshold for enabling the feature, but the size of the cache is too small for the big tables to be effectively cached.
To enable Big Table caching, one of the following actions could be taken:
* C (Correct):IncreasingDB_BIG_TABLE_CACHE_PERCENT_TARGETto at least 25. This action would allocate a larger percentage of the buffer cache for storing big tables, which could allow for caching large tables and thus improve I/O performance.
* D (Correct):IncreasingDB_CACHE_SIZEto 1G. Since the size of the buffer cache is a determining factor for how much data can be cached, increasing this parameter would provide more memory space for big tables to be cached.
Options A, B, E, and F will not enable Big Table caching because:
* A:IncreasingDB_BIG_TABLE_CACHE_PERCENT_TARGETto 50 without adjusting the overall size of the cache might still not be sufficient if theDB_CACHE_SIZEis not large enough to hold the big tables.
* B:SettingDB_KEEP_CACHE_SIZEto at least 50M only specifies a separate buffer pool for objects with the KEEP cache attribute and does not affect Big Table caching.
* E:andF:Changing thePARALLEL_DEGREE_POLICYtoADAPTIVEorAUTOinfluences the behavior of parallel execution but does not directly enable or influence Big Table caching.
References:
* Oracle Database Performance Tuning Guide:Big Table Caching
* Oracle Database Reference:DB_BIG_TABLE_CACHE_PERCENT_TARGET
* Oracle Database Reference:DB_CACHE_SIZE

NEW QUESTION # 35
Examine this command:

What is the maximum number of baselines generated by this command that you can have at any given time?

• A. 0
• B. 1
• C. 2
• D. 3

Answer: C

Explanation:
The DBMS_WORKLOAD_REPOSITORY.CREATE_BASELINE_TEMPLATE procedure 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. The parameters of the CREATE_BASELINE_TEMPLATE procedure 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

NEW QUESTION # 36
Examine this statement and output:

Which three statements are true?

• A. Session 9857 is not waiting.
• B. Both 9822 and 8779 sessions are waiting for operating system resources.
• C. Session 8779 may be waiting due to a network problem.
• D. Session 8779 may be waiting for a user or application response.
• E. Session 9822 will always stop waiting if the session that owns the TX enqueue issues a COMMIT statement as session 9822 is the first session in the transaction queue.
• F. Session 9857 waited 1354 seconds for another process, which was also waiting for a transaction to end.

Answer: C,D,E

Explanation:
For this SQL statement and output, we can analyze theEVENTcolumn to understand the type of wait:
B: The event "SQL*Net message from client" typically indicates that the session is waiting for a response from the client. This can be due to a network issue, user response, or an application processing delay.
E: The event "SQL*Net message from client" also implies that the session is idle waiting for the client (a user or an application) to send a request to the server. This event usually indicates that the session is not actively working but is instead waiting for the next command.
F: The wait event "enq: TX - row lock contention" suggests that session 9822 is waiting for a row-level lock held by another session. If the holding session issues a COMMIT or ROLLBACK, the lock will be released, and session 9822 will stop waiting. Since this session is experiencing row lock contention, it implies it's waiting for a specific transaction to complete.
References:
* Oracle Database Reference, 19c
* Oracle Wait Events Documentation

NEW QUESTION # 37
An Oracle 19c database uses default values for all optimizer initialization parameters.
After a table undergoes partition maintenance, a large number of wait events occur for:
cursor: pin S wait on X
Which command reduces the number of these wait events?

• A. ALTER SYSTEM SET CURSOR_SPACE_FOR_TIME - TRUE;
• B. ALTER SYSTEM SET CURSOR_INVALIDATION = DEFERRED;
• C. ALTER SYSTEM SET SESSION CACHED CURSORS = 500;
• D. ALTER SYSTEM SET CURSOR_SHARING = FORCE;

Answer: B

Explanation:
Thecursor: pin S wait on Xwait event suggests contention for a cursor pin, which is associated with mutexes (a type of locking mechanism) that protect the library cache to prevent concurrent modifications. This issue can often be alleviated by deferring the invalidation of cursors until the end of the call to reduce contention.
The correct command to use would be:
* C (Correct):ALTER SYSTEM SET CURSOR_INVALIDATION=DEFERRED;This setting defers the invalidation of dependent cursors until the end of the PL/SQL call, which can reduce thecursor: pin S wait on Xwait events.
The other options are incorrect in addressing this issue:
* A (Incorrect):SettingCURSOR_SHARINGtoFORCEmakes the optimizer replace literal values with bind variables. It doesn't address the contention for cursor pins directly.
* B (Incorrect):CURSOR_SPACE_FOR_TIME=TRUEaims to reduce the parsing effort by keeping cursors for prepared statements open. It may increase memory usage but does not directly resolve cursor: pin S wait on Xwaits.
* D (Incorrect):IncreasingSESSION_CACHED_CURSORScaches more session cursors but doesn't necessarily prevent the contention indicated by thecursor: pin S wait on Xwait events.
References:
* Oracle Database Reference:CURSOR_INVALIDATION
* Oracle Database Performance Tuning Guide:Reducing Cursor Invalidation

NEW QUESTION # 38
Users complain about slowness and session interruptions. Additional checks reveal the following error in the application log:

Which file has additional information about this error?

• A. ASH report
• B. Session trace file SQL trace file automatically generated by the error
• C. Alert log
• D. SQL trace file automatically generated by the error

Answer: C

Explanation:
When an ORA-00060 deadlock error occurs, detailed information about the error and the deadlock graph are dumped into the alert log. This log contains a trace file name that you can use to find additional detailed information about the sessions involved in the deadlock and the SQL statements they were executing.
References:
* Oracle Database Administrator's Guide, 19c
* Oracle Database Error Messages, 19c

NEW QUESTION # 39
Which two options are part of a Soft Parse operation?

• A. SQL Optimization
• B. Semantic Check
• C. Shared Pool Memory Allocation
• D. Syntax Check
• E. SQL Row Source Generation

Answer: B

Explanation:
During a soft parse, Oracle checks the shared SQL area to see if an incoming SQL statement matches one already in the shared pool. This operation includes syntax and semantic checks. The syntax check ensures the statement is properly formed, and the semantic check confirms that all the objects referenced in the SQL statement exist and that the user has the necessary privileges to access them.References:
* Oracle Database Concepts, 19c
* Oracle Database SQL Tuning Guide, 19c

NEW QUESTION # 40
Which two statements are true about cursor sharing?

• A. Adaptive Cursor Sharing guarantees that a suboptimal plan will never be used on any execution of a SQL statement.
• B. Setting optimizer_capture_sql_plan_baselines to TRUE loads all adaptive plans for the same statement into the cursor cache.
• C. Adaptive Cursor Sharing requires histograms on filtered columns, used in equality predicates, to allow different execution plans to be generated for statements whose bound values would normally generate different plans at hard parse time.
• D. Setting cursor_sharing to EXACT prevents Adaptive Cursor Sharing from being used.
• E. Setting Cursor_sharing to FORCE can result in a plan that is suboptimal for the majority of values bound to a bind variable when executing a cursor with one or more bind variables.

Answer: D,E

Explanation:
A: WhenCursor_sharingis set toFORCE, Oracle tries to avoid hard parses by replacing literals in SQL statements with bind variables, even if the original statement didn't include bind variables. This can lead to the use of a single execution plan for multiple executions of a statement with different literal values, which might not be optimal for all executions.
D: Settingcursor_sharingtoEXACTensures that SQL statements must match exactly for them to share a cursor. This setting prevents the use of Adaptive Cursor Sharing (ACS) since ACS relies on the ability to share cursors among similar statements that differ only in their literal values. WithEXACT, there's no cursor sharing for statements with different literals, hence no opportunity for ACS to operate.
References:
* Oracle Database SQL Tuning Guide, 19c
* Oracle Database Reference, 19c

NEW QUESTION # 41
......

Guaranteed Success in Oracle Database 19c 1Z0-084 Exam Dumps: https://www.examcost.com/1Z0-084-practice-exam.html

1Z0-084 Practice Test Engine: Try These 57 Exam Questions: https://drive.google.com/open?id=1ZjxRzU9m_aZl2_LKo9QND1YOVqft-MQF