[2016-Jun-NEW]Braindump2go New Oracle 1Z0-053 Dumps Guarantee 100% Pass[NQ21-NQ30]

2016 June Oracle Official 1Z0-053: Oracle Database 11g: Administration II Exam Questions New Updated Today in Braindump2go.com. 100% 1Z0-053 Exam Pass Guaranteed!

NEW QUESTION 21 – NEW QUESTION 30:

 

QUESTION 21
Which three statements are true regarding the functioning of the Autotask Background Process (ABP)? (Choose three.)

A.    It creates jobs without considering the priorities associated with them.
B.    It translates tasks into jobs for execution by the scheduler.
C.    It determines the list of jobs that must be created for each maintenance window.
D.    It is spawned by the MMON background process at the start of the maintenance window.
E.    It maintains a repository in the SYSTEM tablespace to store the history of the execution of all tasks.

Answer: BCD
Explanation:
AutoTask Overview
Oracle 11g added a new component to the Oracle automated task infrastructure, that began in Oracle 10g, called AutoTask. AutoTask provides a central component that is responsible for management of scheduled maintenance tasks.
AutoTask Architecture
AutoTask builds on much of the existing architecture of Oracle 10g.
The AutoTask architecture consists of the following components:
AutoTask Background Process (ABP)-APB is spawned by MMON and is responsible for managing the AutoTask features. It coordinates the AutoTask clients and the scheduler. It also maintains AutoTask related history that can be seen in the DBA_AUTOTASK_TASK view. AutoTask Clients-Automated maintenance tasks that are scheduled by AutoTask.
Oracle 11g includes clients for statistics gathering, the Segment Advisor, and the Automatic SQL Tuning Advisor.
The AutoTask Maintenance Windows-Individual maintenance windows exist for different days of the week.
These windows can be modified as required.
Resource Manager-A resource plan is enabled that is designed to limit the amount of resources that the AutoTask tasks can consume. This resource plan can be modified as required.
OEM-You can manage the start time and duration of the various AutoTask maintenance windows and add or remove maintenance tasks with OEM.
You can also use OEM to enable or disable maintenance tasks.
The Scheduler-AutoTask operations rely heavily on the Scheduler. The AutoTask architecture uses scheduler windows and the scheduler infrastructure to execute AutoTask tasks.

QUESTION 22
Which statements are true regarding the concept of problems and incidents in the fault diagnosability infrastructure for Oracle Database 11g? (Choose all that apply.)

A.    Only the incident metadata and dumps are stored in the Automatic Diagnostic Repository (ADR).
B.    The problem key is the same as the incident number.
C.    The database sends an incident alert to the Oracle Enterprise Manager Database Home page.
D.    Every problem has a problem key, which is a text string that describes the problem.
E.    The database makes an entry into the alert log file when problems and incidents occur.

Answer: CDE
Explanation:
Reference at here
Fault Diagnosability Infrastructure Overview
The fault diagnosability infrastructure aids in preventing, detecting, diagnosing, and resolving problems. The problems that are targeted in particular are critical errors such as those caused by code bugs, metadata corruption, and customer data corruption. When a critical error occurs, it is assigned an incident number, and diagnostic data for the error (such as trace files) are immediately captured and tagged with this number. The data is then stored in the Automatic Diagnostic Repository (ADR)–a file-based repository outside the database–where it can later be retrieved by incident number and analyzed.
About Incidents and Problems
A problem is a critical error in a database instance, Oracle Automatic Storage Management (Oracle ASM) instance, or other Oracle product or component. Critical errors manifest as internal errors, such as ORA- 00600, or other severe errors, such as ORA-07445 (operating system exception) or ORA-04031 (out of memory in the shared pool). Problems are tracked in the ADR. Each problem has a problem key, which is a text string that describes the problem. It includes an error code (such as ORA 600) and in some cases, one or more error parameters. An incident is a single occurrence of a problem. When a problem (critical error) occurs multiple times, an incident is created for each occurrence. Incidents are timestamped and tracked in the Automatic Diagnostic Repository (ADR). Each incident is identified by a numeric incident ID, which is unique within the ADR. When an incident occurs, the database:
Makes an entry in the alert log.
Sends an incident alert to Oracle Enterprise Manager (Enterprise Manager). Gathers first-failure diagnostic data about the incident in the form of dump files (incident dumps).
Tags the incident dumps with the incident ID.
Stores the incident dumps in an ADR subdirectory created for that incident.

QUESTION 23
What two statements are true regarding the recommendations received from the SQL Access Advisor? (Choose two.)

A.    It cannot generate recommendations that support multiple workload queries.
B.    It can recommend partitioning on tables provided that the workloads have some predicates and joins
on the columns of the NUMBER or DATE type.
C.    It can recommend partitioning only on tables that have at least 10,000 rows.
D.    It can recommend only B-tree indexes and not bitmap or function-based indexes.

Answer: BC

QUESTION 24
You are managing Oracle Database 11g with an ASM storage with high redundancy. The following command was issued to drop the disks from the dga disk group after five hours:
ALTER DISKGROUP dga OFFLINE DISKS IN FAILGROUP f2 DROP AFTER 5H;
Which statement is true in this scenario?

A.    It starts the ASM fast mirror resync.
B.    All the disks in the dga disk group would be OFFLINE and the DISK_REPAIR_TIME disk attribute
would be set to 5 hours.
C.    It drops all disk paths from the dga disk group.
D.    All the disks in the dga disk group in failure group f2 would be OFFLINE and the DISK_REPAIR_TIME
disk attribute would be set to 5 hours.

Answer: D
Explanation:
 

QUESTION 25
Which statement describes the significance of the CHANGE FAILURE command in RMAN? (Choose all that apply.)

A.    It is used to change failure priority only for HIGH or LOW priorities.
B.    It is used to execute the advised repair script.
C.    It is used to change failure priority only for the CRITICAL priority.
D.    It is used to explicitly close the open failures.
E.    It is used to inform the database about the repair after the repair script executes.

Answer: AD

QUESTION 26
Which statements are true regarding the creation of an incident package file by using the EM Workbench Support? (Choose all that apply.)

A.    You can add or remove the trace files to the package.
B.    You can create the incremental incident package ZIP file for new or modified diagnostic information
for the incident package already created.
C.    You can add SQL test cases to the incident package.
D.    You cannot create an incremental incident package when the physical files are purged rom the ADR.

Answer: ABC
Explanation:
Refer to here
About Quick Packaging and Custom Packaging
The Enterprise Manager Support Workbench provides two methods for creating and uploading an incident package: the quick packaging method and the custom packaging method. Quick Packaging–This is the more automated method with a minimum of steps, organized in a guided workflow (a wizard). You select a single problem, provide a package name and description, and then schedule upload of the package contents, either immediately or at a specified date and time. The Support Workbench automatically places diagnostic data related to the problem into the package, finalizes the package, creates the zip file, and then uploads the file. With this method, you do not have the opportunity to add, edit, or remove package files or add other diagnostic data such as SQL test cases. However, it is the simplest and quickest way to get first- failure diagnostic data to Oracle Support. Quick packaging is the method used in the workflow described in “Investigating, Reporting, and Resolving a Problem”. Note that when quick packaging is complete, the package that was created by the wizard remains. You can then modify the package with custom packaging operations at a later time and manually reupload.
Custom Packaging–This is the more manual method, with more steps. It is intended for expert Support Workbench users who want more control over the packaging process. With custom packaging, you can create a new package with one or more problems, or you can add one or more problems to an existing package. You can then perform a variety of operations on the new or updated package, including:
Adding or removing problems or incidents
Adding, editing, or removing trace files in the package Adding or removing external files of any type Adding other diagnostic data such as SQL test cases
Manually finalizing the package and then viewing package contents to determine if you must edit or remove sensitive data or remove files to reduce package size.
You might conduct these operations over a number of days, before deciding that you have enough diagnostic information to send to Oracle Support. With custom packaging, you create the zip file and request upload to Oracle Support as two separate steps. Each of these steps can be performed immediately or scheduled for a future date and time.
Select the Full or Incremental option to generate a full package zip file or an incremental package zip file.
For a full package zip file, all the contents of the package (original contents and all correlated data) are always added to the zip file.
For an incremental package zip file, only the diagnostic information that is new or modified since the last time that you created a zip file for the same package is added to the zip file. For example, if trace information was appended to a trace file since that file was last included in the generated physical file for a package, the trace file is added to the incremental package zip file. Conversely, if no changes were made to a trace file since it was last uploaded for a package, that trace file is not included in the incremental package zip file.

QUESTION 27
The application tables owned by the user TEST in a test database need to be exported to the APPS schema in the production database by using Data Pump.
Which option of Data Pump Import would you use to accomplish this?

A.    owner
B.    touser
C.    attach
D.    remap_schema

Answer: D

QUESTION 28
You want to track and store all transactional changes to a table over its lifetime. To accomplish this task, you enabled Flashback Data Archive with the retention of 5 years. After some time, the business requirement changed and you were asked to change the retention from 5 years to 3 years. To accomplish this, you issued the following command:
ALTER FLASHBACK ARCHIVE fla1 MODIFY RETENTION 3 YEAR;
What is the implication of this command?

A.    The command produces an error because the retention time cannot be reduced.
B.    All historical data is retained but the subsequent flashback data archives are maintained for only
three years.
C.    All historical data is purged and the new flashback data archives are maintained for three years.
D.    All historical data older than three years is purged from the flashback archive FLA1.

Answer: D
Explanation:
http://docs.oracle.com/cd/E11882_01/appdev.112/e25518/adfns_flashback.htm#ADFNS644
Your company wants to “shred” (delete) historical data changes to the Taxes table after ten years. When you create the Flashback Data Archive for Taxes, you specify a retention time of ten years:
CREATE FLASHBACK ARCHIVE taxes_archive TABLESPACE tbs1 RETENTION 10 YEAR;
When history data from transactions on Taxes exceeds the age of ten years, it is purged. (The Taxes table itself, and history data from transactions less than ten years old, are not purged.)

QUESTION 29
You are managing an Oracle Database 11g database with ASM storage. The ASM disk group has the COMPATIBLE.ASM attribute set to 11.1. Which statements are true regarding extent management and allocation units in the ASM disk group? (Choose all that apply.)

A.    The au_size disk group attribute determines the size of allocation units in the disk group.
B.    The allocation unit size may vary but the extent size is fixed.
C.    The allocation unit size and extent size are fixed for all the disks in a disk group and cannot be changed.
D.    Extent management is completely automated.

Answer: AD

QUESTION 30
Which are the prerequisites for performing flashback transactions on your database? (Choose all that apply.)

A.    Undo retention guarantee for the database must be configured.
B.    Supplemental log must be enabled for the primary key.
C.    Supplemental log must be enabled.
D.    Execute permission on the DBMS_FLASHBACK package must be granted to the user.

Answer: BCD


2016 Valid Oracle 1Z0-053 Study Materials:

 

1.| Latest 1Z0-053 Exam PDF and VCE Dumps 676q from Braindump2go: http://www.braindump2go.com/1z0-053.html [100% Exam Pass Guaranteed!]

 

2.| New 1Z0-053  Exam Questions and Answers – Google Drive: https://drive.google.com/folderview?id=0B75b5xYLjSSNOGJaLVVucEZfS28&usp=sharing

 

 

MORE Practice is the Most Important IF You want to PASS Oracle 1Z0-053 Exam 100%!
————— Braindump2go.com
————— Pass All IT Exams at the first Try!

         

Braindump2go Testking Pass4sure Actualtests Others
$99.99 $124.99 $125.99 $189 $29.99/$49.99
Up-to-Dated
Real Questions
Error Correction
Printable PDF
Premium VCE
VCE Simulator
One Time Purchase
Instant Download
Unlimited Install
100% Pass Guarantee
100% Money Back