As part of an automated install of Oracle Solaris 11, a new role called "operator" is created and a password is correctly assigned, but you are not able to successfully assume this role. What is the problem?
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.
What two features identify Oracle Solaris 11 as being "built for clouds"?
B: Built-in Virtualization
Whatever the needs of your cloud infrastructure, Oracle has a comprehensive suite of built-in virtualization technologies to compliment your business requirements.
Choose from Oracle Solaris Zones, OVM Server for SPARC, OVM Server for x86 and OVM VirtualBox. With Oracle Solaris Zones, administrators can rapidly provision secure and isolated virtual environments in which to deploy cloud applications and services.
D:
Oracle Solaris is the best platform for the cloud because it combines key computing elements - operating system, virtualization, networking, storage management, and user environment - into a stable, secure, mission-critical foundation that customers can depend on
Which two actions are used to permanently configure a new interface?
Which five steps (dealing with first boot script creation) can be omitted when working with provisioning Oracle Solaris 11 Zones and services with the appropriate Zone context?
1. Create the first-boot script.
2. Create the manifest for an SMF service that runs once at first boot and executes the script.
3. Create an IPS package that contains the service manifest and the script.
4. Add the package to an IPS package repository.
5. Install that lockage during the Automated Installer installation by specifying that package in the AI manifest.
Running a Custom Script During First Boot
To perform any additional installation or configuration that cannot be done in the AI manifest or in a system configuration profile, you can create a script that is executed at first boot by a run-once SMF service.
1. Create the first-boot script.
2. Create the manifest for an SMF service that runs once at first boot and executes the script.
3. Create an IPS package that contains the service manifest and the script.
4. Add the package to an IPS package repository.
5. Install that package during the AI installation by specifying that package in the AI manifest.
The service runs and executes the script at first reboot after the AI installation.
A zone won't boot. Identify the five causes.
A: dedicated-cpu Resource
The dedicated-cpu resource specifies that a subset of the system's processors should be dedicated to a non-global zone while it is running. When the zone boots, the system will dynamically create a temporary pool for use while the zone is running.
C: s the global administrator in the global zone, you can import raw and block devices into a non-global zone. After the devices are imported, the zone administrator has access to the disk. The zone administrator can then create a new file system on the disk and perform one of the following actions:
Mount the file system manually
Place the file system in /etc/vfstab so that it will be mounted on zone boot
D, E: Booting a zone places the zone in the running state. A zone can be booted from the ready state or from the installed state. A zone in the installed state that is booted transparently transitions through the ready state to the running state. Zone login is allowed for zones in the running state.
Incorrect:
Not F: Sys_time not related to booting a zone.
