• ホーム
  • ブログ
  • [2024年07月]更新のOracle 1z1-084問題集とリアルな試験問題 [Q28-Q50]

[2024年07月]更新のOracle 1z1-084問題集とリアルな試験問題 [Q28-Q50]

Share

[2024年07月]更新のOracle 1z1-084問題集とリアルな試験問題

2024年最新の1z1-084のPDF最近更新された問題


1Z0-084試験は、パフォーマンスとチューニング管理に関する知識と専門知識を証明したい人を対象としています。Oracleデータベース管理者、データベース開発者またはエンジニア、ITプロジェクトマネージャー、またはデータベースパフォーマンス最適化に責任を持つ他の専門家がこの試験を受けることで利益を得ることができます。既存のOracleデータベース管理認証をアップグレードしたい人にとっても有益であり、その認証にカウントされます。


1Z0-084試験は、Oracle Database 19cをすでに使用し、データベースのアーキテクチャと管理について堅固な理解を持っている経験豊富なプロフェッショナルを対象としています。この試験は、パフォーマンスとチューニング管理に関連するさまざまな分野における候補者の知識とスキルを試験するよう設計されています。試験は、複数選択問題、シナリオベースの問題、およびパフォーマンスベースの問題から構成されています。

 

質問 # 28
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


質問 # 29
You use SQL Tuning Advisor to tune a given SQL statement.
The analysis eventually results in the implementation of a SQL Profile.
You then generate the new SQL Profile plan and enforce it using a SQL PlanBaselinebut forget to disable the SQLProfile and a few days later you find out that the SQL Profile is generating a new execution plan.
Which two statements are true?

  • A. The conflict between the two plan stability methods results in an error.
  • B. The execution plan is the one enforced by the SQL Plan Baseline.
  • C. The execution plan is the one enforced by the SQL Profile.
  • D. The existence of two concurrent plan stability methods generates a child cursor for every execution.
  • E. The SQL Plan Baseline must be accepted in order to be used for the execution plan.
  • F. The SQL Profiles as well as SQL Plan Baseline are implemented using hints, so they both generate the same plan.

正解：C、E

解説：
When both a SQL Profile and a SQL Plan Baseline are in place, the SQL Profile has a stronger preference and the optimizer is more likely to choose the execution plan from the SQL Profile.
C: A SQL Profile is generally more influential than a SQL Plan Baseline because it contains additional statistics and directives that help the optimizer to generate a more efficient execution plan. If both exist, the optimizer will use the profile's plan unless the baseline's plan is proven to be better through the SQL performance monitoring process.
E: SQL Plan Baselines must be accepted before they can be used by the optimizer. If a SQL Plan Baseline is not accepted, it will not be considered for generating the execution plan. Therefore, the presence of an unaccepted SQL Plan Baseline will not automatically force the optimizer to use its plan.
References:
* Oracle Database SQL Tuning Guide, 19c
* Oracle Database Administrator's Guide, 19c


質問 # 30
You execute the following:
EXECUTE DBMS_AuTO_TASK_ADMIN.DISABLE;
Which advisor remains enabled?

  • A. Automatic Optimizer Statistics Collection
  • B. Optimizer Statistics Advisor
  • C. SQL Plan Management Evolve Advisor
  • D. Automatic Segment Advisor
  • E. Automatic SQL Tuning

正解：A

解説：
When you executeDBMS_AUTO_TASK_ADMIN.DISABLE, it disables all automated maintenance tasks related to the Auto Task framework. This includes tasks such as the Automatic SQL Tuning Advisor, Automatic Segment Advisor, and others. However, the Automatic Optimizer Statistics Collection (D) remains enabled as it is not part of the Auto Task framework. The gathering of optimizer statistics is controlled separately and is a critical part of the database's self-tuning mechanism to ensure the optimizer has up-to-date information about the data distribution within tables and indexes.
References
* Oracle Database 19c PL/SQL Packages and Types Reference - DBMS_AUTO_TASK_ADMIN
* Oracle Database 19c Database Administrator's Guide - Managing Optimizer Statistics


質問 # 31
Buffer cache access is too frequent when querying the SALES table. Examine this command which executes successfully:
ALTER TABLE SALES SHRINK SPACE;
For which access method does query performance on sales improve?

  • A. index full scan
  • B. db file sequential read
  • C. index range scan
  • D. db file scattered read

正解：B

解説：
The SHRINK SPACE operation compacts the table, which can reduce fragmentation and thus improve performance for sequential reads of the table. This operation could improve full table scans, which are typically associated with db file sequential read wait events.
References:
* Oracle Database Administrator's Guide, 19c


質問 # 32
Examine these statements and output:

What parameter change activates the generation and use of SQL Plan Directives7

  • A. optimizer_features_enable=12.2.0.1
  • B. optimizer_adaptive_plans=TRUE
  • C. optimizer_capture_sql_plan_baselines_TRUE
  • D. optimizer_adaptive_statistics = TRUE
  • E. optimizer_dynamic_sampling=11

正解：D

解説：
The optimizer_adaptive_statistics parameter, when set to TRUE, enables the optimizer to use adaptive statistics, such as SQL Plan Directives, to help improve plans by automatically adjusting them based on the actual execution statistics.
References:
* Oracle Database SQL Tuning Guide, 19c


質問 # 33
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 SESSION CACHED CURSORS = 500;
  • C. ALTER SYSTEM SET CURSOR_INVALIDATION = DEFERRED;
  • D. ALTER SYSTEM SET CURSOR_SHARING = FORCE;

正解：C

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


質問 # 34
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 to 192G and MEMORY_TARGET to 256G.
  • B. Set DB_FLASH_CACHE_SIZE parameter to 192G.
  • C. Set DB_FLASH_CACHE_SIZE parameter to 128G, 64G.
  • D. Set DB_FLASH_CACHE_SIZE to 256G and change device /dev/sdk to 128G.
  • E. Disable Automatic Memory Management and set SGA_TARGET to 256G.

正解：C

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


質問 # 35
Which three statements are true about using the in Memory (IM) column store?

  • A. It does not improve performance for queries using user-defined virtual column results.
  • B. It can improve OLTP workload performance by avoiding the use of indexes.
  • C. It does not improve performance for queries that use join groups on columns from different tables.
  • D. It does not improve performance for queries using cached results of function evaluations on columns from the same table.
  • E. It does not require all database data to fit in memory to improve query performance.
  • F. It improves performance for queries joining several tables using bloom filter joins.

正解：B、E、F

解説：
The Oracle In-Memory (IM) column store feature enhances the performance of databases by providing a fast columnar storage format for analytical workloads while also potentially benefiting OLTP workloads.
* C (True):It can improve OLTP workload performance by providing a faster access path for full table scans and reducing the need for indexes in certain scenarios, as the In-Memory store allows for efficient in-memory scans.
* E (True):The In-Memory column store does not require all database data to fit in memory. It can be used selectively for performance-critical tables or partitions, and Oracle Database will manage the population and eviction of data as needed.
* F (True):In-Memory column store can significantly improve performance for queries joining several tables, especially when bloom filters are used, as they are highly efficient with the columnar format for large scans and join processing.
The other options provided are not correct in the context of the In-Memory column store:
* A (False):While In-Memory column store is designed for analytical queries rather than caching results of function evaluations, it does not specifically avoid improving performance for queries using cached results of function evaluations.
* B (False):In-Memory column store can improve the performance of queries that use join groups, which can be used to optimize joins on columns from different tables.
* D (False):In-Memory column store can improve the performance of queries using expressions, including user-defined virtual columns, because it supports expression statistics which help in
* optimizing such queries.
References:
* Oracle Database In-Memory Guide:In-Memory Column Store in Oracle Database
* Oracle Database In-Memory Guide:In-Memory Joins
* Oracle Database In-Memory Guide:In-Memory Aggregation


質問 # 36
Database performance has degraded recently.
index range scan operations on index ix_sales_time_id are slower due to an increase in buffer gets on sales table blocks.
Examine these attributes displayed by querying DBA_TABLES:

Now, examine these attributes displayed by querying DBA_INDEXES:

Which action will reduce the excessive buffer gets?

  • A. Re-create the SALES table sorted in order of index IX_SALES_TIME_ID.
  • B. Partition index IX_SALES_TIME_ID using hash partitioning.
  • C. Re-create index IX_SALES_TIME_ID using ADVANCED COMPRESSION.
  • D. Re-create the SALES table using the columns in IX_SALES_TIME_ID as the hash partitioning key.

正解：C

解説：
Given that index range scan operations onIX_SALES_TIME_IDare slower due to an increase in buffer gets, the aim is to improve the efficiency of the index access. In this scenario:
* B (Correct):Re-creating the index usingADVANCED COMPRESSIONcan reduce the size of the index, which can lead to fewer physical reads (reduced I/O) and buffer gets when the index is accessed, as more of the index can fit into memory.
The other options would not be appropriate because:
* A (Incorrect):Re-creating theSALEStable sorted in order of the index might not address the issue of excessive buffer gets. Sorting the table would not improve the efficiency of the index itself.
* C (Incorrect):Using the columns inIX_SALES_TIME_IDas a hash partitioning key for theSALES table is more relevant to data distribution and does not necessarily improve index scan performance.
* D (Incorrect):Hash partitioning the index is generally used to improve the scan performance in a parallel query environment, but it may not reduce the number of buffer gets in a single-threaded query environment.
References:
* Oracle Database SQL Tuning Guide:Managing Indexes
* Oracle Database SQL Tuning Guide:Index Compression


質問 # 37
Examine this statement and output:

Which two situations can trigger this error?

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

正解：A、E

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


質問 # 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. Increase the size of the library cache.
  • C. Create the KEEP cache and cache tables accessed by the SQL statements.
  • D. Set the CURSOR_SHARING parameter to FORCE.
  • E. Create the RECYCLE cache and cache tables accessed by the SQL statements.

正解：B、D

解説：
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
What is the right time to stop tuning an Oracle database?

  • A. When the buffer cache and library cache hit ratio is above 95%
  • B. When the I/O is less than 10% of the DB time
  • C. When all the concurrency waits are eliminated from the Top 10
  • D. When the allocated budget for performance tuning has been exhausted

正解：D

解説：
The right time to stop tuning an Oracle database is often determined by the point of diminishing returns - when the cost of further tuning (in terms of time, resources, or money) exceeds the performance benefits gained.
This is often related to the budget allocated for performance tuning.
* A (Correct):When the allocated budget for performance tuning has been exhausted, it may be time to stop tuning unless the benefits of further tuning justify requesting additional budget.
* B (Incorrect):Eliminating all concurrency waits from the Top 10 is an unrealistic goal since some waits are inevitable and can occur due to application design, which might not be possible to eliminate completely.
* C (Incorrect):The buffer cache and library cache hit ratio being above 95% does not necessarily indicate that the database is fully optimized. Hit ratios are not reliable indicators of database performance and should not be used as sole criteria to end tuning efforts.
* D (Incorrect):Having I/O less than 10% of DB time is not a definitive indicator to stop tuning. It is essential to consider the overall performance goals and whether they have been met rather than focusing solely on I/O metrics.
References:
* Oracle Database Performance Tuning Guide:Introduction to Performance Tuning
* Oracle Database 2 Day + Performance Tuning Guide:Understanding the Tuning Process


質問 # 40
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 rewriting the SQL statements
  • B. recommendations regarding the creation of additional indexes
  • C. recommendations regarding the creation of SQL Patches
  • D. recommendations regarding partitioning the tables
  • E. recommendations regarding the creation of materialized views

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


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

正解：C

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


質問 # 42
Multiple sessions are inserting data concurrently into a table that has an LOB column.
At some point in time, one of the sessions cannot find available space in the LOB segment and needs to allocate a new extent.
Which wait event will be raised in the other sessions that need space in the LOB column?

  • A. enq: SQ - contention
  • B. enq: TM - contention
  • C. enq: TX - allocate ITL entry
  • D. enq: HW - contention

正解：D

解説：
When sessions concurrently insert data into a table with an LOB column and one session needs to allocate a new extent because it cannot find available space, the wait event associated with this contention is "enq: HW - contention". The HW stands for High Water Mark which is related to space allocation in the database segment.
When asession needs to allocate a new extent, it may raise this wait event in other sessions that are also attempting to allocate space in the same LOB segment.
References
* Oracle Database 19c Reference Guide - enq: HW - contention


質問 # 43
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


質問 # 44
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. Alert log
  • B. Session trace file SQL trace file automatically generated by the error
  • C. ASH report
  • D. SQL trace file automatically generated by the error

正解：A

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


質問 # 45
A Standard Edition production database has performance problems for two hours on the same day each week.
Which tool must you use to diagnose the problem?

  • A. AWR Compare Periods report
  • B. Database Replay
  • C. Statspack report
  • D. SQL Performance Analyzer

正解：C

解説：
For a Standard Edition production database, the Statspack tool is available to diagnose performance problems.
The Automatic Workload Repository (AWR) and its related tools like AWR Compare Periods report and SQL Performance Analyzer are features of the Oracle Database Enterprise Edition and are not available in Standard Edition. Database Replay is also a feature of the Enterprise Edition. Statspack is a performance diagnostic tool provided for earlier versions and Standard Editions of the Oracle Database to collect, store, and analyze performance data.
References
* Oracle Database 19c Administrator's Guide - Using Statspack to Diagnose Database Performance Issues


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

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

正解：C


質問 # 47
Which two statements are true about Data Pump import for objects that used the in Memory (IM) column store in their source database?

  • A. It can generates the INMEMORY clause that matches the table settings at export time.
  • B. It ignores the IM column store clause of the exporting objects.
  • C. It must always transports existing INMEMORY attributes.
  • D. Its TRANSFORM clause can be used to add the INMEMORV clause to exported tables that lack them.
  • E. Its INMEM0RY_CLAUSE of the Data Pump Export allows modifications to IM column store clause of a table with existing INMEMORY setting.
  • F. It always gives preference to the IM column store clause defined at the tablespace level over table-level definitions.

正解：A、D

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


質問 # 48
Which two statements are true about session wait information contained in v$session or v$session_wait?

  • A. Rows for sessions that are currently waiting have a wait time of 0.
  • B. Rows for sessions that are currently waiting have their wait time incremented every microsecond.
  • C. Rows for sessions displaying WAITED UNKNOWN TIME in the STATE column indicate that the session is still waiting.
  • D. Rows for sessions that are not waiting might contain the actual wait time for the last event for which they waited.
  • E. Rows for sessions that are not waiting always contain the total wait time since the session started.

正解：A、D

解説：
In theV$SESSIONview, Oracle provides information about the session waits:
B: When theWAIT_TIMEcolumn has a value of 0, it signifies that the session is currently waiting for a resource. This column represents the duration of the current or last wait.
C: If the session is not actively waiting, theWAIT_TIMEcolumn shows the time the session spent waiting for the last wait event. If theSTATEcolumn is showing "WAITED KNOWN TIME", it means the session is not currently waiting, but it indicates the time for which it had waited.
References:
* Oracle Database Reference, 19c
* Oracle Database Performance Tuning Guide, 19c


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

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

正解：C

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


質問 # 50
......

最新の1z1-084合格保証される試験問題集認証サンプル問題：https://www.passtest.jp/Oracle/1z1-084-shiken.html

1z1-084試験合格保証最新57問題：https://drive.google.com/open?id=1Vx3rh9TgP5a2V-h2-r6jETfd-z6crp8n

関するブログ

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