Cause all that matters here is passing the Oracle 1Z0-581 exam. Cause all that you need is a high score of 1Z0-581 Pillar Axiom 600 Storage System Essentials exam. The only one thing you need to do is downloading Examcollection 1Z0-581 exam study guides now. We will not let you down with our money-back guarantee.
2016 Oct 1Z0-581 free practice test
Q31. The storage administrator is creating a clone of volume ABC. Identify the parameters on the clone that the storage administrator can change.
A. Volume Name B. Volume Group C. Storage Profile D. Storage Domain
E. Background Copy Priority
Explanation: A: Volume Name
Identifies the name that is assigned to a LUN for administrative purposes.
LUN names must be unique across the Pillar Axiom system and must be 82
or fewer UTF characters, or 255 or fewer ASCII characters.
Allows you to assign the LUN to an existing volume group.
[...] Opens the dialog that allows you to create new
C: Storage Profile
Identifies the set of QoS attributes applied to the LUN.
[...] Opens the View Storage Profiles dialog that allows
you to review the profile details.
D: Storage Domain
Identifies the name of the storage domain associated with the LUN.
Storage Domains allow storage administrators to assign logical volumes to a
specific collection of Bricks. Such assignments can be made to reduce
contention among volumes, to implement different levels of security for those
volumes, or both.
Reference: Pillar Axiom Administrator's Guide, Create SAN Clone LUN, Quality of Service Tab
Q32. Which option in Create Event Notification activates the notification when the event occurs on the Axiom storage system?
A. Enable EventNotification
B. Monitored Events
D. EmailNotification Recipient Email Addresses
E. Events not Monitored
Explanation: Create an Event Notification
Create event notifications so that you are notified when specific events occur in
the Pillar Axiom system. You can specify the types of system events that trigger
alerts as well as designate the recipients who receive the notices.
If you do not set up notices, you can still monitor system events using the event
log. CallHome notifications are also independent of email notifications and will
be sent to Pillar Data Systems about issues in the Pillar Axiom system.
(See step 5 below):
1 From the Monitor tab, click Event Notification.
2 Choose Actions > Create Event Notification.
3 Enter a name for the event notification in the Name field.
4 Enter a description in the Description field.
5 To enable the notification, select Enable Event Notification.
6 From the Monitored Events list, select the events for which you want to
trigger the notification.
To be notified of any login failures, in the event tree, navigate down to the
Informational > Audit list. Select the Login Failed item and then click the rightfacing
arrow to move the item to the Monitored Events column.
7 To add one or more event notification recipients, click Add.
8 Enter the email address of each notification recipient.
9 (Optional) Click Test Email to make sure that the alert is sent to the correct
email addresses and that the SMTP server is properly configured.
Note: Allow at least 10 minutes between email tests.
10 (Optional) To remove an email address from the list, select the address and
11 To save the new notification, click OK.
Note: Create event notifications so that you are notified when specific Pillar Axiom
system events occur. You may want to display the details of an event and make
changes as needed. You can also test notifications to make sure that the
specified email addresses are correct.
An event notification, when enabled, is defined as follows:
A Simple Mail Transfer Protocol (SMTP) email message
that notifies recipients of specified system events. System
events include informational, warning, or critical events such
as the creation of a logical volume or the occurrence of a
hardware or software problem. Event notifications are
optional and supplement normal event logging and
CallHome notification. (Formerly called an alert).
Reference:Pillar Axiom Administrator's Guide,About Managing Event Notifications
Q33. Why does it matter if the source power for a PDU is 115v, 208v, or 230v?
A. The Bricks, Slammers, and Pilots will draw different amperes depending on the input to the PDU.
B. The Bricks and Slammers will draw different amperes depending on the input to the PDU but the Pilot will not draw much to make a difference.
C. The Bricks and Pilots will draw the same amperes and not enough to make a difference but the Slammers will draw different amperes depending on the input to the PDU.
D. It does not matter because the Bricks, Slammers, and Pilots will draw the same amperes.
Explanation: The Pillar Axiom 600 system components must be plugged into the PDUs such that they do not exceed the amperage rating of any outlet group. If you exceed the amperage rating, the circuit breakers trip. Except where indicated, the maximum rated amperage of the outlet banks remains the same regardless of the electrical service voltage. Therefore, components draw about half the amperage at 230V than at 115V, and you can plug more components into each power distribution unit (PDU). The table below lists the maximum electrical requirements of the Pillar Axiom 600 components. Each component has redundant power cords plugged into different PDUs on separate circuits. Table Pillar Axiom 600 electrical requirements Reference: Pillar Axiom 600 Hardware installation Guide, Component Power Usage
Q34. Identify two Items displayed on the AxiomONE Storage Services Manager user interface status bar.
A. system status
B. time zone
C. storage utilization
D. currentrunning processes
Explanation: In addition to context-sensitive help, the Pillar Axiom Storage Services Manager GUI makes readily available certain vital information about the operation of the Pillar Axiom system. This information is displayed in the status bar at the bottom of each overview window.
Displays the overall system status.
Display all background tasks
Click this icon to open the Background
Processes dialog. From this dialog, you can also
open the View Axiom Communication Details
dialog (see below)
Reference: Pillar Axiom Administrator's Guide, Status Bar Description
Q35. Select the hardware component that virtualizes the storage pool.
B. Network Interface Module
D. Private Management Interface
Explanation: A Storage Domain is defined as: A subset of a virtual storage pool consisting of a defined group of Brick storage enclosures. This group can consist of any assortment of Bricks, regardless of Storage Class, capacity, or any other attribute. A Storage Domain is typically used to provide specific allocation or security features for a collection of logical volumes.
Note: Storage Domains allow storage administrators to assign logical volumes to a specific collection of Bricks. Such assignments can be made to reduce contention among volumes, to implement different levels of security for those volumes, or both.
Updated 1Z0-581 answers:
Q36. The storage administrator is ready to define a storage domain. What must the storage administrator ensure before the storage domain can be created?
A. A storage Profile needs to be created to set the Storage Domain QoS setting.
B. The Storage Domain license must be installed.
C. There must be at least one Brick that does not contain volumes.
D. The storage administrator must be loggedin as the pillar support account.
Explanation: As of release 5.0, if you have installed the Storage Domain license, you can cause the system to migrate the redundant instances of the system configuration database onto separate Bricks by performing the following general actions:
Add new Bricks to the system.
Place them into a new Storage Domain.
Set the new Storage Domain as the primary domain.
The Pillar Axiom system will then migrate the configuration database onto the Bricks in the
newly primary domain and stripe the database across multiple Bricks.
Note: A Storage Domain is defined as: A subset of a virtual storage pool consisting of a defined group of Brick storage enclosures. This group can consist of any assortment of Bricks, regardless of Storage Class, capacity, or any other attribute. A Storage Domain is typically used to provide specific allocation or security features for a collection of logical volumes.
Reference: Pillar Axiom 300, 500, and 600. Release notes
Q37. Identify the location where the AxiomONE Storage Services Manager software in available for download.
A. via FTP (torn the Pillar Customer Support portal
B. from a web browser, by specifying the name or IP address of the Axiom
C. from a web browser, under Software on the Pillar Customer Support portal
D. from the AxiomONEStorage Manager user Interface, by clicking the Download ASSM GUI link on the Support tab
Explanation: Pillar Axiom Storage Services Manager graphical user interface (GUI) applications:
Storage Services Manager and Pillar Axiom MaxMan
The GUI applications are available in the following formats:
Windows Installer: Provides the download link for the
Windows installer in MSI format.
JAR and Run Scripts: Provides the download links to the selfcontained JAR (Java archive) file and scripts in Zip and Tar archive formats.
Reference: Pillar Axiom Administrator's Guide, About Accessing Pillar Axiom 600 Applications
Q38. The storage administrator is creating a LUN. Which organizational units can the LUN be assigned to?
A. Storage Class B. Typical Access C. Volume Group D. Storage Domain
E. Clone LUN Group
Explanation: Volume groups are organizational units that can contain any grouping of logical
volumes and nested volume groups
Note: A LUN is defined as:
A logical volume within a storage area network (SAN).
Administrators assign storage resources and Quality of
Service (QoS) attributes to each logical unit (LUN).
Reference: Pillar Axiom Administrator's Guide
Q39. The storage administrator is setting up an Axiom and would identify the two call-home triggers that should be selected. Select two.
A. Enable event triggered call-home
B. Enablestandard periodic call home
C. Enable larger periodic callhome
D. Enable Email Notifications
E. Enable Data Digestlike to enable basic call home functionality.
Explanation: Call-Home Triggering Allows you to specify when events logs and messages are sent to the CallHome server.
Enable event triggered call-home
Enables CallHome support, which enables the Pillar Axiom system to send status messages to the designated server.
Enable standard periodic Call-Home Enables the periodic sending of the Pillar Axiom event logs to the CallHome server.
Enable larger periodic Call-Home Enables large files to be sent to the CallHome server so that trace logs and performance statistics are automatically included in the CallHome logs.
Reference: Pillar Axiom Administrator's Guide, Call-Home Triggering
Q40. The storage administrator is looking for a specific event in the event log. Identify three event severities that can be filtered.
Explanation: The Pillar Axiom system generates events and classifies them by severity:
Critical: Access to data is compromised.
Warning:Administrator action is required to prevent a soft error
from becoming a hard error or critical event.
Informational: A configuration change has been detected or another
non-error event has occurred.
Reference: Pillar Axiom Administrator's Guide, Pillar Axiom event severities