Test: Sun Systems Fault Analysis Workshop Online Assessment

Review your answers, feedback, and question scores below.

This online assessment measures your understanding of the concepts prese
nted in the Sun Systems Fault Analysis Workshop. This assessment is offered as a
n alternative option to attending the 5-day instructor-led class. You will have
two chances to take it and successfully pass the assessment, otherwise you will
be required to attend the class.
Sun Systems Fault Analysis Workshop Online Assessment
(Answer all questions in this section)
51.
When modifying the boot behavior of an x86-based Solaris
server, the modification can be permanent or temporary. <br/><br/> Which option
would change the boot behavior temporarily, for a single boot cycle, until the
next time the system is booted? Mark for Review
(1) Points
Use the eeprom command to set the temporary boot command.
Use the kernel command to set the temporary boot command.
Edit the bootenv.rc file with the temporary boot command.
Modify the boot_archive file with the temporary boot command.

Correct

Correct!

52.
The hypothesis that is formulated in the diagnosis phase
will state the most probable cause of a fault. A hypothesis to be tested follow
ing one of these recommended test methodologies: Factual, Experimental, or Assum
ptive.<br/><br/> You decide to follow the Experimental methodology for a hypothe
sis formulated for a reported fault. <br/><br/> Which option describes the actio
n to be performed in the Experimental approach? Mark for Review
(1) Points
Rely on previous experiences about the actual cause and take corrective
action.
Review all probable causes based on past problem logs to rapidly isolate
the actual cause.
Test each probable cause of the fault and determine conclusively the act
ual cause.
Make educated guesses about the actual cause of the fault and take corre
ctive action.

Correct

Correct!

53.
The customer wants to know what command could be used on
their Solaris servers to display the output of the current system definition; l
isting all hardware devices, pseudo devices, system devices, and loadable module
s.<br/><br/> Which command displays this output by analyzing the contents of phy
sical and virtual memory?
Mark for Review
(1) Points
sysdef -i
/usr/platform/`uname -m`/sbin/prtdiag
/usr/sbin/sysdef
/usr/sbin/prtconf

Correct

Correct!

54.
Your customer reports that one of their x86-based Solari
s servers will not boot from the primary boot drive. Because the boot drive has
been mirrored, they need to make a change to the server so that the system boots
from the alternate boot disk.<br/><br/> Which option describes the procedure to
change the default boot disk? Mark for Review
(1) Points
Change the bootpath parameter in the boot_archive file so that it points
to the correct boot device.
Use the eeprom command to change the bootpath parameter so that it point
s to the correct boot device.
Change the bootpath parameter in the /boot/solaris/bootenv.rc file so th
at it points to the correct boot device.
Use the eeprom command to change the boot-file parameter so that it poin
ts to the correct boot drive.

Correct

Correct!

55.
The response time within a newly configured zone is very
poor, and many services are not running. The customer who configured this new z
one, had booted it and logged in successfully.<br/><br/> Within the new zone the

following command was run, which explains the state of service.<br/><br/> # svc
s -xv<br/> No output for more than 5 minutes.<br/><br/> From the message generat
ed you surmise what the probable cause of the slow zone is, and run the next set
of commands:<br/> # zoneadm -z newzone halt<br/> # zonecfg -z newzone<br/> zone
cfg:newzone> remove capped-memory<br/> zonecfg:newzone> commit<br/> zonecfg:newz
one> info<br/> zonecfg:newzone> exit<br/> # zoneadm -z newzone boot<br/> # zlogi
n newzone<br/> # svcs -xv<br/> The zone should run faster than before.<br/><br/>
Which option would be the cause of this poor response time reported on the new
zone?
Mark for Review
(1) Points
Zone initiation failed, uninstall and install again.
Physical memory capping changed.
Loopback filesystem not enabled.
Zone misconfigured, resources caps too low.

Correct

Correct!

Previous

Page 11 of 11

Summary