1Z0-821 Latest Exam Braindumps
Question 17: You have completed configuring a zone named dbzone on your Solaris 11 server. Theconfiguration is as following:
The global zone displays the following network information:
The zone has never been booted. Which three options correctly describe this zone?
A. It is a sparse root zone.
B. It is a whole root zone.
C. It is an immutable zone.
D. It is a native zone.
E. The zone shares the network interface with the host.
F. The zone uses a virtual network interface.
G. The hostid is the same as the global zone.
H. The IP address of the zone is 10.0.2.18.
Correct Answer: C,E,G
Explanation:
C: Immutable Zones provide read-only file system profiles for solaris non-global zones.
Note that ip-type: exclusive:
Starting with OpenSolaris build 37 and Oracle Solaris 10 8/07, a default zone can be configured as an
"exclusive-IP zone" which gives it exclusive access to the NIC(s) that the zone has been assigned.
Applications in such a zone can communicate directly with the NIC(s) available to the zone.
Note on zones:
After installing Oracle Solaris on a system, but before creating any zones, all processes run in the
global zone. After you create a zone, it has processes that are associated with that zone and no other
zone. Any process created by a process in a non-global zone is also associated with that non-global
zone.
Any zone which is not the global zone is called a non-global zone. Most people call non- global zones
simply "zones." Some people call them "local zones" but this is discouraged.
The default native zone file system model on Oracle Solaris 10 is called "sparse-root." This model
emphasizes efficiency and security at the cost of some configuration flexibility.
Sparse-root zones optimize physical memory and disk space usage by sharing some directories, like
/usr and /lib. Sparse-root zones have their own private file areas for directories like /etc and /var.
Whole-root zones increase configuration flexibility but increase resource usage. They do not use
shared file systems for /usr, /lib, and a few others.
There is no supported way to convert an existing sparse-root zone to a whole-root zone.
Creating a new zone is required.
