• ホーム
  • ブログ
  • 無料セールまもなく終了！100%有効1z1-084試験問題集に57問題と解答が待ってます [Q30-Q52]

無料セールまもなく終了！100%有効1z1-084試験問題集に57問題と解答が待ってます [Q30-Q52]

Share

無料セールまもなく終了！100%有効1z1-084試験問題集に57問題と解答が待ってます

検証済み1z1-084問題集と解答であなたを合格確定させるOracle Database 19c試験解答！


Oracle 1Z0-084試験は、Oracleデータベース19cパフォーマンスおよびチューニング管理に関する候補者の知識とスキルを評価することに焦点を当てています。データベース管理者、パフォーマンスアナリスト、およびOracleデータベースシステムのパフォーマンスを管理する他の専門家を対象として設計されています。この試験に合格することは、個人がOracleデータベースパフォーマンスを最適化し、高い可用性と信頼性を確保するために必要な主要なコンセプトと技術の包括的な理解を持っていることを示します。

 

質問 # 30
Which two statements are true about space usage in temporary tablespaces?

  • A. Lack of temporary tablespace space for sort operations can be prevented by using temporary tablespace groups.
  • B. A sort will fail if a sort to disk requires more disk space and no additional extent can be found/allocated in/for the sort segment.
  • C. When a global temporary table instantiation is too large to fit in memory, space is allocated in a temporary tablespace.
  • D. When a session consumes all temporary tablespace storage, then the session would hang until the temporary space used by that session is cleared.
  • E. Temporary tablespaces setting Includes quotas to limit temporary space used by a session for that Temporary tablespace.

正解：A、C

解説：
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


質問 # 31
For which two actions can SQL Performance Analyzer be used to assess the impact of changes to SQL performance?

  • A. operating system upgrades
  • B. changes to database initialization parameters
  • C. operating system and hardware migrations
  • D. storage, network, and interconnect changes
  • E. database consolidation for pluggable databases (PDBs)

正解：B、E

解説：
SQL Performance Analyzer (SPA) can be used to assess the impact of different types of changes on SQL performance. These changes can include database initialization parameters, which can significantly affect how SQL statements are executed and therefore their performance. SPA allows you to capture a workload before and after the change and compare the performance of each SQL statement.
Database consolidation, including moving to pluggable databases (PDBs), can also affect SQL performance.
SPA can analyze the SQL workload to see how consolidation impacts performance, by comparing metrics such as elapsed time and CPU time before and after the consolidation.
References:
* Oracle Database SQL Tuning Guide, 19c
* Oracle Database Performance Tuning Guide, 19c


質問 # 32
You want to reduce the amount of db file scattered read that is generated in the database.You execute the SQL Tuning Advisor against the relevant workload. Which two can be part of the expected result?

  • A. recommendations regarding partitioning the tables
  • B. recommendations regarding the creation of materialized views
  • C. recommendations regarding rewriting the SQL statements
  • D. recommendations regarding the creation of SQL Patches
  • E. recommendations regarding the creation of additional indexes

正解：B、E

解説：
The SQL Tuning Advisor provides recommendations for improving SQL query performance. This may include suggestions for creating additional indexes to speed up data retrieval and materialized views to precompute and store query results.References:
* Oracle Database SQL Tuning Guide, 19c


質問 # 33
Which two statements are true about the use and monitoring of Buffer Cache Hit ratios and their value in tuning Database I/O performance?

  • A. The buffer cache advisory view v$db_cache_advice provides advice on cache hit ratios appropriate for the instance workload.
  • B. Both the RECYCLE and KEEP buffer caches should always have a very high cache hit ratio.
  • C. The performance of workloads that primarily generate full table scans and fast full index scans are always affected by the cache hit ratio.
  • D. A 99% cache hit ratio can be observed for database instances which have very poor I/O performance.
  • E. A 60% cache hit ratio can be observed for database instances which have very good I/O performance.

正解：A、D


質問 # 34
What are the least elevated values of statistics_level and C0NTR0LJ4ANAGEMENT_PACK_ACCESS that allow the usage of Monitoring of Database Operations?

  • A. STATISTICS_LEVEL=ALL and
    CONTROL_MANAGEMENT_PACK_ACCESS=DIAGOSTIC+TUNING
  • B. STATISTICS_LEVEL=TYPICAL and
    CONTROL_MANAGEMENT_PACK_ACCESS-DIAGOSTIC*TUNING
  • C. STATISTICS_LEVEL=TYPICAL and CONTROL_MANAGEMENT_PACK_ACCESS=DIAGOSTIC
  • D. STATISTICS_LEVEL=BASIC and CONTROL_MANAGEMENT_PACK ACCESS=DIAGOSTIC

正解：A

解説：
Monitoring of Database Operations requires that theSTATISTICS_LEVELparameter be set toALLand CONTROL_MANAGEMENT_PACK_ACCESSbe set toDIAGNOSTIC+TUNING. These settings enable all the advisory features and automatic tuning features within the Oracle Database, including the Automatic Workload Repository (AWR), Automatic Database Diagnostic Monitor (ADDM), and the full functionality of the SQL Tuning Advisor and SQL Access Advisor, which are components of the Diagnostic and Tuning packs.
* STATISTICS_LEVEL=ALL:This setting enables the collection of all system statistics for problem detection and self-tuning purposes.
* CONTROL_MANAGEMENT_PACK_ACCESS=DIAGNOSTIC+TUNING:This grants access to both the Diagnostic Pack and the Tuning Pack, which are essential for detailed performance monitoring and tuning capabilities.
References:
* Oracle Database Reference:STATISTICS_LEVEL
* Oracle Database Licensing Information User Manual:Oracle Database Management Packs


質問 # 35
A database supporting a mixed workload is hosted on a server with 64 CPUs.
A large number of free buffer waits and buffer busy waits occur affecting performance.
The buffer cache size was then increased but after a few hours, the same wait events occur more often than before the change.
Examine these parameter settings:

Which two actions can help reduce the number of these waits7

  • A. reducing the values of DB_FILE_MULTILOCK_READ_COUNT to 64
  • B. increasing the value of DBWRITERPROCESSES to 64,
  • C. setting dbwr_io_slaves to 64
  • D. Increasing the size of MEMORYTARGET
  • E. increasing the value of DB_FILE_MULTIBLOCK_READ_COUNT to 128

正解：B、C

解説：
Given a server with 64 CPUs, if the buffer cache size increase did not alleviate free buffer waits and buffer busy waits, one can look into optimizing I/O and the efficiency of the DB writer processes.
C: Setting the DBWR_IO_SLAVES parameter to a non-zero value, such as the number of CPUs, would initiate I/O slave processes to assist the DB writer process. This can help reduce I/O contention when writing from the buffer cache to disk, particularly for systems without asynchronous I/O capabilities.
D: Increasing the value of DBWRITERPROCESSES enables multiple DB writer processes to be active simultaneously. In a system with many CPUs, such as 64, increasing this value can improve the write throughput to disk and potentially reduce buffer busy waits.
References:
* Oracle Database Reference, 19c
* Oracle Database Performance Tuning Guide, 19c


質問 # 36
Accessing the SALES tables causes excessive db file sequential read wait events.
Examine this AWR except:

Now, examine these attributes displayed by querying dba_tables:

Finally, examine these parameter settings:

Which two must both be used to reduce these excessive waits?

  • A. Increase PCTFREE for the SALES table.
  • B. Compress the SALES table.
  • C. Coalesce all sales table indexes.
  • D. Partition the SALES table.
  • E. Re-create the SALES table.

正解：B、D

解説：
The AWR excerpt points to excessive physical reads on the SALES table and index, suggesting the need for optimizing table storage and access.
Partitioning the SALES table (A) can reduce 'db file sequential read' waits by breaking down the large SALES table into smaller, more manageable pieces. This can localize the data and reduce the I/O necessary for query operations.
Compressing the SALES table (D) can also help reduce I/O by minimizing the amount of data that needs to be read from disk. This can also improve cache utilization and reduce the 'db file sequential read' waits.
References:
* Oracle Database VLDB and Partitioning Guide, 19c
* Oracle Database Administrator's Guide, 19c
These changes are recommended based on Oracle's best practices for managing large tables and reducing I/O waits, ensuring better performance and efficiency.


質問 # 37
You need to collect and aggregate statistics for the ACCTG service and PAYROLL module, and execute:

Where do you find the output of this command?

  • A. By viewing V$SERV_MOD_ACT_STATS
  • B. By viewing V$SERVICE_STATS
  • C. In $ORACLE_BASE/diag/rdbms/<db unique name>/<instance name>/trace
  • D. In the current working directory

正解：A

解説：
When you enable statistics gathering for a specific service and module using DBMS_MONITOR.
SERV_MOD_ACT_STAT_ENABLE, the output is aggregated and can be viewed using the V$SERV_MOD_ACT_STATS dynamic performance view. This view contains the cumulative statistics of database activity broken down by service and module, which is exactly what you collect when executing the provided command.
* B (Incorrect): While many types of trace files are located in the Diagnostic Destination directory (
$ORACLE_BASE/diag), the aggregated statistics for services and modules are not written to trace files but are instead viewable through dynamic performance views.
* C (Incorrect): The V$SERVICE_STATS view provides service-level statistics but does not provide the combined service/module-level breakdown.
* D (Incorrect): The output of the PL/SQL block is not written to a file in the current working directory; it is stored in the data dictionary and accessible via dynamic performance views.
References:
* Oracle Database PL/SQL Packages and Types Reference: DBMS_MONITOR
* Oracle Database Reference: V$SERV_MOD_ACT_STATS


質問 # 38
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. Set OPTIMIZER_CAPTURE_SQL_PLAN_BASELINESto TRUE.
  • 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. Create the RECYCLE cache and cache tables accessed by the SQL statements.

正解：B、C

解説：
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


質問 # 39
Examine this statement and output:

Which two situations can trigger this error?

  • A. There is a file in the capture directory.
  • B. The instance is unable to access the capture directory.
  • C. The syntax is incomplete.
  • D. The user lacks the required privileges to execute the DBMS WORKLOAD CAPTURE package or the directory.
  • E. The capture directory is part of the root file system.

正解：B、D

解説：
The ORA-15505 error indicates that the instance encountered errors while trying to access the specified directory. This could be due to:
A: Insufficient privileges: The user attempting to start the workload capture might not have the required permissions to execute the DBMS_WORKLOAD_CAPTURE package or to read/write to the directory specified.
E: Accessibility: The database instance may not be able to access the directory due to issues such as incorrect directory path, directory does not exist, permission issues at the OS level, or the directory being on a file system that's not accessible to the database instance.
References:
* Oracle Database Error Messages, 19c
* Oracle Database Administrator's Guide, 19c


質問 # 40
Which two statements are true about disabling Automatic Shared Memory Management (ASMM)?

  • A. All auto-tuned SGA components are reset to their original user-defined values.
  • B. All SGA components retain their current sizes at the time of disabling.
  • C. The SGA size remains unaffected after disabling ASMM.
  • D. All SGA components excluding fixed SGA and other internal allocations are readjusted immediately after disabling ASMM.
  • E. It requires a database instance restart to take effect.
  • F. Both SGA_TARGET and SGA_MAX_SIZE must be set to zero.

正解：B、C

解説：
When ASMM is disabled, the sizes of the automatically managed SGA components remain at their current values. ASMM is controlled by theSGA_TARGETparameter. IfSGA_TARGETis set to a non-zero value, ASMM is enabled and Oracle will automatically manage the sizes of the various SGA components. When ASMM is disabled, by settingSGA_TARGETto zero, the SGA components that were automatically sized will retain their current sizes rather than being reset to their original user-defined values. The overall size of the SGA remains the same unless manually changed by modifying individual component sizes or SGA_MAX_SIZE.
References:
* Oracle Database Administration Guide, 19c
* Oracle Database Performance Tuning Guide, 19c


質問 # 41
Which three types of statistics are captured by statspack with snap level 6?

  • A. Parent and child latches
  • B. Enqueue statistics
  • C. Plan usage data
  • D. Segment-level statistics
  • E. Optimizer execution plans
  • F. Parent and child latches

正解：B、D、F

解説：
Statspack is a performance diagnostic tool provided by Oracle prior to the introduction of the Automatic Workload Repository (AWR). At snap level 6, Statspack captures the following types of statistics:
* A (Correct):Parent and child latches are captured. Latch statistics provide information about contention for latches, which are low-level serialization mechanisms used by Oracle.
* E (Correct):Enqueue statistics, which provide information on the waits for locks that manage the concurrency between users.
* F (Correct):Segment-level statistics, which provide detailed information on database segments such as tables, indexes, etc., to identify I/O and contention issues.
* C (Incorrect):While optimizer execution plans are an essential aspect of performance tuning, detailed execution plan capture is not part of the Statspack report at level 6.
* D (Incorrect):Plan usage data refers to how frequently a plan is being used, which is more associated with AWR and not typically captured in Statspack reports.
References:
* Oracle Database Performance Tuning Guide:Using Statspack


質問 # 42
Which application lifecycle phase could be managed reactively?

  • A. Production
  • B. Design and development
  • C. Upgrade or migration
  • D. Testing
  • E. Deployment

正解：A

解説：
The production phase of the application lifecycle is often managed reactively. While proactive measures and performance tuning are essential, unforeseen issues can arise in production that require immediate attention and resolution. Reactive management involves monitoring performance and responding to issues as they occur, ensuring the application maintains acceptable performance levels for end-users.
References
* Oracle Database 19c Performance Tuning Guide - Reactive Tuning


質問 # 43
Which two options are part of a Soft Parse operation?

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

正解：D

解説：
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


質問 # 44
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 tine excludes the time spent waiting for a CPU in the operating system run queue.
  • C. DB time includes the time spent executing the RMAN backup and restore command.
  • D. DB time is organized as a simple list of statistics and any time period is attributable to only one statistic.

正解：A

解説：
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


質問 # 45
You are informed that the RMAN session that is performing the database duplication is much slower than usual. You want to know the approximate time when the rman operation will be completed.
Which view has this information?

  • A. V$SESSTAT
  • B. V$RMAN_BACKUP_JOB_DETAILS
  • C. V$SESSION
  • D. V$SESSION_LONGOPS

正解：D

解説：
In Oracle Database, theV$SESSION_LONGOPSview provides insights into various operations within the database that are expected to take more than six seconds to complete. These include operations related to RMAN (Recovery Manager), such as database duplication tasks. This view displays information about the progress of these long-running operations, including the start time, elapsed time, and estimated time to completion.
When an RMAN session is performing a database duplication and is observed to be slower than usual, checking theV$SESSION_LONGOPSview can give an approximation ofwhen the RMAN operation might complete. This view includes fields likeTIME_REMAININGandELAPSED_SECONDSthat help in estimating the completion time of the operation based on its current progress.
References:
* Oracle Database Reference:V$SESSION_LONGOPS
* Oracle Database Backup and Recovery User's Guide:Monitoring RMAN Jobs


質問 # 46
Examine this statement and its corresponding execution plan:

Which phase introduces the CONCATENATION step?

  • A. SQL Row Source Generation
  • B. SQL Adaptive Execution
  • C. SQL Execution
  • D. SQL Semantic Check
  • E. SQL Transformation

正解：E

解説：
The CONCATENATION step in an execution plan is introduced during the SQL Transformation phase. This phase is part of the optimizer's query transformations which can include various techniques to rewrite the query for more efficient execution. The CONCATENATION operation is used to combine the results of two separate SQL operations, typically when there is an OR condition in the WHERE clause, as seen in the provided query.
References:
* Oracle Database SQL Tuning Guide, 19c
* Oracle Database Concepts, 19c


質問 # 47
Which two types of performance problems are reported by ADDM for PDBS?

  • A. User I/O waits
  • B. Excessive checkpoint writes
  • C. I/O capacity limits
  • D. Top SQL statements
  • E. SGA sizing issues

正解：A、C

解説：
The Automatic Database Diagnostic Monitor (ADDM) analyzes and reports on various types of performance problems. For Pluggable Databases (PDBs), it can identify issues such as I/O capacity limits which may hinder the overall performance by causing bottlenecks. Additionally, ADDM can report on user I/O waits, which can indicate performance issues related to the time it takes for user queries to read data from the disk.
References:
* Oracle Multitenant Administrator's Guide, 19c
* Oracle Database Performance Tuning Guide, 19c


質問 # 48
Examine this statement and output:

Which three statements are true?

  • A. 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.
  • B. Both 9822 and 8779 sessions are waiting for operating system resources.
  • C. Session 9857 is not waiting.
  • D. Session 8779 may be waiting due to a network problem.
  • E. Session 9857 waited 1354 seconds for another process, which was also waiting for a transaction to end.
  • F. Session 8779 may be waiting for a user or application response.

正解：A、D、F

解説：
For this SQL statement and output, we can analyze the EVENT column 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


質問 # 49
Examine this statement and output:

Which two situations can trigger this error?

  • A. There is a file in the capture directory.
  • B. The instance is unable to access the capture directory.
  • C. The syntax is incomplete.
  • D. The user lacks the required privileges to execute the DBMS WORKLOAD CAPTURE package or the directory.
  • E. The capture directory is part of the root file system.

正解：B、D

解説：
The ORA-15505 error indicates that the instance encountered errors while trying to access the specified directory. This could be due to:
A: Insufficient privileges: The user attempting to start the workload capture might not have the required permissions to execute the DBMS_WORKLOAD_CAPTURE package or to read/write to the directory specified.
E: Accessibility: The database instance may not be able to access the directory due to issues such as incorrect directory path, directory does not exist, permission issues at the OS level, or the directory being on a file system that's not accessible to the database instance.
References:
* Oracle Database Error Messages, 19c
* Oracle Database Administrator's Guide, 19c


質問 # 50
Which two statements are true about the use and monitoring of Buffer Cache Hit ratios and their value in tuning Database I/O performance?

  • A. The buffer cache advisory view v$db_cache_advice provides advice on cache hit ratios appropriate for the instance workload.
  • B. Both the RECYCLE and KEEP buffer caches should always have a very high cache hit ratio.
  • C. The performance of workloads that primarily generate full table scans and fast full index scans are always affected by the cache hit ratio.
  • D. A 99% cache hit ratio can be observed for database instances which have very poor I/O performance.
  • E. A 60% cache hit ratio can be observed for database instances which have very good I/O performance.

正解：A、D

解説：
A high buffer cache hit ratio typically indicates that the database is effectively using the buffer cache and does not often need to read data from disk. However, this metric alone is not a reliable indicator of the I/O performance of the database for several reasons:
* Full table scans and fast full index scans (A) can bypass the buffer cache by design if the blocks are not
* deemed reusable shortly, which can impact the cache hit ratio.
* A high cache hit ratio (B) can be misleading if the database performance is poor due to other factors, such as inefficient queries or contention issues.
* The buffer cache advisory (C) is a more valuable tool for understanding the potential impact of different cache sizes on the database's I/O performance. It simulates scenarios with different cache sizes and provides a more targeted recommendation.
* The RECYCLE and KEEP buffer caches (D) are specialized caches designed for certain scenarios.
While high hit ratios can be beneficial, they are not universally required; some workloads might not be significantly impacted by lower hit ratios in these caches.
* A lower cache hit ratio (E) does not necessarily mean poor I/O performance. In some cases, a system with a well-designed storage subsystem and efficient queries might perform well even with a lower cache hit ratio.
References
* Oracle Database 19c Performance Tuning Guide - Buffer Cache Hit Ratio
* Oracle Database 19c Performance Tuning Guide - v$db_cache_advice


質問 # 51
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 critical alert will be issued when CPU time exceeds 10000 microseconds for each user call.
  • B. A warning alert will be issued only when CPU time exceeds 10000 microseconds for each user call.
  • C. A critical alert will be issued when CPU time exceeds 2 minutes for each user call.
  • D. A warning alert will be issued when CPU time exceeds 1 minute for each user call.

正解：A

解説：
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.


質問 # 52
......

1z1-084試験問題集で100%合格率1z1-084試験：https://www.passtest.jp/Oracle/1z1-084-shiken.html

試験問題集リアルOracle Database 19c問題集57問題と解答が待ってますを試そう：https://drive.google.com/open?id=1Vx3rh9TgP5a2V-h2-r6jETfd-z6crp8n

関するブログ

もっと
1z1-084 無料問題集