Curious about Actual Oracle Operating Systems (1Z0-580) Exam Questions?

Correct : B

Note:

* A user can only assume roles that are assigned to the user's login account.

* After you have set up roles with default Solaris rights profiles, and assigned the roles to users, the roles can be used. A role can be assumed on the command line. In the Solaris Management Console, a role can also be used for administering the system locally and over the network.

* How to Assume a Role in a Terminal Window

The role must already be assigned to you. The name service must be updated with that information.

1. In a terminal window, determine which roles you can assume.

2. % roles

Comma-separated list of role names is displayed

3. Use the su command to assume a role.

4. % su - rolename

5. Password: <Type rolename password>

$

The su - rolename command changes the shell to a profile shell for the role. A profile shell recognizes security attributes (authorizations, privileges, and set ID bits).

6. Verify that you are now in a role.

7. $ /usr/ucb/whoami

rolename

You can now perform role tasks in this terminal window.

Correct : A

Use the pkg revert command to restore files to their as-delivered condition.

Correct : B

To ensure the system boots without starting the installation, make sure the entry you choose to boot does not have the install=true boot property specified in its kernel line.

Correct : D

Note:

* sendmail

* Enabling Access to Remote Clients

On an unmodified system, access to sendmail by remote clients is enabled and disabled through the service management facility (see smf(5)). In particular, remote access is determined by the value of the local_only SMF property:

svc:/network/smtp:sendmail/config/local_only = true

A setting of true, as above, disallows remote access; false allows remote access. The default value is true.

The following example shows the sequence of SMF commands used to enable sendmail to allow access to remote systems:

# svccfg -s svc:/network/smtp:sendmail setprop config/local_only = false

# svcadm refresh svc:/network/smtp:sendmail

# svcadm restart svc:/network/smtp:sendmail

Correct : B

Note:

* The services started by svc.startd are referred to as milestones. The milestone concept replaces the traditional run levels that were used in previous versions of Solaris. A milestone is a special type of service that represents a group of services. A milestone is made up of several SMF services. For example, the services that instituted run levels S, 2, and 3 in previous version of Solaris are now represented by milestone services named:

milestone/single-user (equivalent to run level S)

milestone/multi-user (equivalent to run level 2)

milestone/multi-user-server (equivalent to run level 3)

* Shut down the system.

# shutdown -iinit-state -ggrace-period -y

-iinit-state

Brings the system to an init state that is different from the default of S. The choices are 0, 1, 2, 5, and 6.

Run levels 0 and 5 are states reserved for shutting the system down. Run level 6 reboots the system. Run level 2 is available as a multiuser operating state.