1z0-820
Upgrade to Oracle Solaris 11 System Administrator
Upgrade to Oracle Solaris 11 System Administrator: Practical Exam Guide
Upgrade to Oracle Solaris 11 System Administrator, exam 1Z0-820, is the upgrade examination for professionals moving from an earlier Solaris administration credential toward Oracle Certified Professional, Oracle Solaris 11 System Administrator (upgrade). It is intended for administrators and transition-focused IT architects who need to understand the operational differences between Oracle Solaris 10 and Oracle Solaris 11. This guide helps you decide whether the upgrade route fits your background, which technical areas to study first, how to use Oracle’s documentation effectively, and when you are ready to schedule the exam.
Does the upgrade route fit your background?
The first decision is eligibility: Oracle requires a prior Oracle Certified Professional Oracle Solaris Administrator credential or a Sun Certified Solaris Administrator credential, in any version. If you do not hold one of those credentials, treat this as a planning reference rather than assuming that the upgrade examination is your correct entry point. Oracle lists the requirement on the certification path at https://education.oracle.com/oracle-certified-professional-oracle-solaris-11-system-administrator-upgrade/trackp_820.
This route is most suitable for an administrator who already understands Solaris administration and needs to learn the Solaris 11 operating model. Oracle describes its Transition to Oracle Solaris 11 course as building on Oracle Solaris 10 system-administration experience and providing skills for moving from Oracle Solaris 10 to Oracle Solaris 11. That makes the upgrade path different from starting with general UNIX fundamentals.
The intended audience also includes IT architects who plan and perform transition tasks. In practice, that means the useful preparation focus is not limited to memorizing command names. You need to connect planning decisions with implementation consequences: how software is updated, how a new boot environment is used, how configuration changes affect networking and naming services, and how storage, security, and user environments change.
Before buying training or booking an exam, write down the earlier credential you hold and the Solaris release experience behind it. Then identify whether your work has involved only routine administration or also system transitions. Candidates with strong Solaris 10 administration experience but little Solaris 11 hands-on work should spend most of their preparation on differences and migration workflows. Candidates with broad Solaris 11 experience should use the older credential requirement as a reminder to verify that the upgrade exam, rather than a full certification path, matches their objective.
What credential and examination does Oracle identify?
Oracle identifies the target credential as “Oracle Certified Professional, Oracle Solaris 11 System Administrator (upgrade).” The required examination for this upgrade certification is “Upgrade to Oracle Solaris 11 System Administrator,” exam number 1Z0-820. Oracle’s certification catalog places “Upgrade to Oracle Solaris 11 System Administrator | 1Z0-820” under Solaris 11 Administration. Sources: https://education.oracle.com/oracle-certified-professional-oracle-solaris-11-system-administrator-upgrade/trackp_820 and https://www.oracle.com/in/a/ocom/docs/ou-certification-catalog.pdf.
The supplied official information does not provide a verified exam blueprint with domain percentages, question count, passing score, languages, price, or current retirement status. Do not fill those gaps with figures from third-party practice sites. In particular, there is no supported basis here for saying that one topic carries a larger percentage than another. Use Oracle’s current certification page to confirm any details that may change before scheduling.
The official path labels Transition to Oracle Solaris 11 as optional preparation for 1Z0-820. Oracle also lists the Oracle IT Infrastructure Learning Subscription as optional preparation. Optional does not mean irrelevant, and it does not mean that either resource is a prerequisite. Choose between them based on how much structured instruction and product coverage you need, not on an assumption that enrolling guarantees exam readiness.
The examination title tells you the central theme, but it should not be interpreted as a promise that every question will be a step-by-step upgrade procedure. A capable upgrade administrator must understand planning, release differences, system configuration, software, networking, storage, security, user management, and virtual environments. The official transition documentation provides those topic areas as a useful study map, while the certification page remains the authority for the exam requirement and eligibility.
Which technical areas deserve study time?
Study the transition topics as connected administration tasks rather than as isolated chapter names. Oracle’s transition documentation covers the overview, installation methods, devices, storage, file systems, software, network configuration, system configuration, security, virtual environments, and user account and environment changes. The same documentation is available at https://docs.oracle.com/cd/E23824_01/html/E24456/upgrade-1.html.
No official percentage weights are supplied in the research for the domains below, so the domain labels should guide coverage, not be treated as a scoring blueprint. The listed domain names and their source ordering are useful for building a checklist, while the depth of your study should depend on your actual experience and the parts of Solaris 11 you cannot yet explain or demonstrate.
Managing Oracle Solaris releases in a virtual environment: understand how a release transition interacts with virtualized or zone-based environments and what must be checked before applying a change. Focus on boundaries, dependencies, and recovery planning rather than assuming that a guest or zone behaves exactly like a standalone system.
Transitioning from Oracle Solaris 10 to Oracle Solaris 11: learn the overall migration choices and the differences that affect an existing installation. Use the overview to create a decision tree: what is being moved, which configuration must be preserved, which installation method is appropriate, and what must be validated after the transition.
Transitioning to an Oracle Solaris 11 installation method: compare the available transition approaches in the official documentation and record the conditions under which each is appropriate. Your notes should answer what the method changes, what it preserves, and what preparation or post-transition verification it requires.
Managing devices: review device-related changes and the administrator’s responsibilities when hardware, drivers, or device configuration is involved. Do not study this as a list of commands alone. Tie each procedure to discovery, compatibility, configuration, and validation.
Managing storage features: connect storage administration with ZFS, boot environments, datasets, pools, and the operational impact of changing the underlying system. Oracle’s transition documentation names Managing Storage Features as a distinct area; the practical study goal is to explain why a storage decision matters during a release transition.
Managing file systems: understand file-system behavior and transition implications, including what must be checked when root or shared file-system arrangements change. Make a before-and-after table for mount points, sharing, permissions, and application dependencies, using only behaviors you can verify in Oracle documentation or a controlled lab.
Managing software: learn the Solaris 11 packaging and update model, repository access requirements, update preview, boot-environment naming, and multi-step update situations. This is one of the areas where reading the current Solaris 11.4 update procedure is especially valuable.
Managing network configuration: study interface, naming-service, and network configuration changes as operational dependencies. A system can complete an installation or update and still fail its intended role if name resolution, routes, services, or application connectivity are not checked afterward.
Managing system configuration: review service, boot, identity, and general system settings that may differ from earlier Solaris administration habits. Build troubleshooting notes around symptoms and verification commands, but verify every command and option against current documentation before relying on it.
Managing security: cover the security changes that affect accounts, privileges, services, access, and post-transition validation. The goal is to reason about least privilege and retained access, not to disable controls simply to make a lab procedure work.
User account management and user environment changes: examine account behavior, profiles, defaults, home directories, and user-facing changes that can surprise an administrator after transition. Test both administrative and ordinary-user outcomes where possible.
The official documentation also includes Using Oracle Solaris Desktop Features. That topic may be less central to a server-focused role, but it should not be silently omitted from your checklist if your environment uses desktop features or if you are working through the transition documentation as a whole.
A practical prioritization rule is to study first the areas where a wrong decision could make the system unbootable, unreachable, insecure, or inconsistent with application requirements. Then cover the remaining domains systematically. This is a preparation recommendation, not an Oracle weighting claim.
How should you study the Solaris 11 update workflow?
Learn the update workflow as a sequence with decision points: confirm package access, check available versions, preview the operation, perform the update with a meaningful boot-environment name, and validate the resulting environment. Oracle documents that a Solaris 11.4 system upgrade is performed with pkg update and that required software packages must be accessible. Source: https://docs.oracle.com/en/operating-systems/solaris/oracle-solaris/11.4/update-sys-add-sw/how-update-oracle-solaris-11-system.html.
The official procedure includes a preview step before the actual update. This matters because an administrator should discover package, dependency, or target-version problems before changing the running system. In your notes, separate checks that establish readiness from actions that modify the image. That distinction improves both troubleshooting and rollback planning.
Oracle shows the --be-name option with a named boot environment in its example. Reproduce the logic rather than copying a command without understanding it: the name should identify the intended update, and the resulting boot environment should be distinguishable during validation and recovery. A meaningful name is a practical administration recommendation supported by the documented procedure.
Some image upgrades require multiple update steps because a subset of software must be updated before the rest can be updated. Oracle says that, when a one-step upgrade cannot reach the desired end state, the administrator should update as far as possible, reboot to the new boot environment, and update again. Release notes indicate whether a multi-step upgrade is required. Source: https://docs.oracle.com/en/operating-systems/solaris/oracle-solaris/11.4/update-sys-add-sw/how-update-oracle-solaris-11-system.html.
This is a valuable scenario for study because it tests sequencing and judgment. Prepare a written response to four questions: What packages or repository access must be available? What does the preview tell you? Which boot environment will receive the change? What must happen if the target cannot be reached in one update? If you cannot answer those without searching, continue studying the procedure.
Do not reduce the topic to the idea that one command completes every upgrade. Oracle’s page presents pkg update as the core action but explicitly notes prerequisites, previewing, boot environments, and possible additional update steps. Your revision notes should preserve those conditions.
How can the transition documentation become a study system?
Use Oracle’s transition documentation in three passes: first map the change, then perform or mentally rehearse the administration task, and finally verify the post-change state. This approach turns a long reference into decisions you can recall under time pressure without relying on leaked questions or unsupported memorization material.
In the first pass, read the overview and installation-method material before diving into individual commands. Record the starting platform, the intended Solaris 11 result, the transition method, prerequisites, preserved elements, and known incompatibilities. Mark every point that could affect downtime, connectivity, bootability, storage, or user access.
In the second pass, work through one domain at a time. For software, rehearse package access, available-version checks, preview, update, boot-environment selection, and multi-step handling. For networking, map configuration changes to name resolution and reachability checks. For security, identify which accounts, privileges, services, and access paths need validation. For file systems and storage, link the logical layout to boot and application dependencies.
In the third pass, close the documentation and reconstruct the workflow from your own notes. Then reopen the relevant page and correct omissions. This is more useful than highlighting every sentence because it exposes whether you understand the order and purpose of each action.
Create a change matrix with five columns: Solaris 10 expectation, Solaris 11 behavior or method, administrator action, verification, and recovery concern. Populate it only from the official sources or from behavior you have verified in your own authorized lab. The matrix is particularly useful for naming-service configuration, root file-system changes, file-system sharing, default paths, device-driver customization, and user-environment changes identified in the transition reference.
Keep a separate command notebook. For each command, write its purpose, prerequisites, expected effect, and a verification method. Avoid collecting commands without context. An exam question may present a condition or desired result rather than asking for a memorized line, and operational work also depends on knowing when not to run a command.
Use the current Solaris 11.4 update page for update mechanics and the transition reference for broader migration differences. The two documents serve different purposes: one gives a focused update procedure, while the other organizes the broader transition from Solaris 10 and earlier Solaris 11 releases.
Which Oracle preparation options are worth choosing?
Choose training according to the gap you have identified. Oracle labels Transition to Oracle Solaris 11 as optional preparation for 1Z0-820 and describes it as suitable for administrators and IT architects planning and performing transition tasks. Oracle also lists an Oracle IT Infrastructure Learning Subscription as optional preparation, so neither option should be treated as a mandatory exam requirement.
The Oracle Solaris training page lists Transition to Oracle Solaris 11 Ed 3, Oracle Solaris 11 System Administration Ed 5, Oracle Solaris 11 Advanced System Administration Ed 4, Oracle Solaris 11 Zones Administration Ed 3, Oracle Solaris 11 ZFS Administration Ed 2, Shell Programming Ed 1, Perl Programming Ed 3, UNIX and Linux Essentials, and Oracle Security Overview as English training-on-demand offerings. Source: https://www.oracle.com/solaris/technologies/training.html.
For an experienced Solaris 10 administrator, begin with Transition to Oracle Solaris 11. Add system administration training if your Solaris 11 fundamentals are weak, and select ZFS, Zones, or security material only when your diagnostic work shows a gap. This sequence avoids spending equal time on every course when your main need is understanding release differences.
For an administrator who has touched Solaris 11 but has not performed a transition, pair the transition course or documentation with controlled practice. Use the system administration course to fill foundational gaps, then return to the migration chapters and rehearse the consequences of each change.
The Oracle Solaris training page also describes the Oracle Solaris Learning Library as containing free online training content, including OBEs, demos, and tutorials. These resources can support targeted practice when you need to see a task explained or performed. Treat them as learning aids, not as evidence that a particular exam question will appear.
Oracle says its Systems Learning Subscription includes one year of unlimited access to Systems training lessons, product introductions, best practices, and more. Whether that is worthwhile depends on the breadth of your role and your need for structured access. It is a training choice, not a substitute for verifying the certification requirement and current scheduling information on Oracle’s certification page.
What should a practical lab include?
A useful lab should let you observe the effect of a transition decision, verify the result, and recover safely. Build it around authorized systems or a suitable virtual environment, take documented snapshots or backups where appropriate, and never apply an untested upgrade procedure to production merely to gain exam practice.
Start with a baseline record. Capture the Solaris release, installed software, network settings, naming-service behavior, storage and file-system layout, users and groups, services, security settings, and virtual-environment structure that matter to the workload. The point is not to record everything; it is to define what “working” means before a change.
Practice the update sequence from the Oracle procedure. Confirm package access, check available versions, preview the update, create or select a clearly named boot environment, and perform the update in the supported lab context. If the chosen target requires multiple steps, document the intermediate state, reboot behavior, and second update rather than treating the process as a single event. Oracle’s current procedure is at https://docs.oracle.com/en/operating-systems/solaris/oracle-solaris/11.4/update-sys-add-sw/how-update-oracle-solaris-11-system.html.
After each change, test from several perspectives. Check that the system boots into the intended environment, packages are at the expected level, network access and name resolution work, file systems are mounted and usable, required services run, administrative access remains available, and ordinary users can use their expected environment. These are practical validation recommendations; the exact checks depend on the lab workload.
Create failure drills without inventing unsupported product behavior. For example, rehearse how you would respond when package access is unavailable, when the preview indicates that the desired target cannot be reached in one step, or when a post-update service fails. For each drill, identify the evidence you would collect and the official documentation you would consult next.
If you cannot run a Solaris 11 lab, use a paper lab: draw the starting and resulting states, write the command or procedure step, state the expected effect, and list verification evidence. This is weaker than hands-on practice but still exposes gaps in sequencing and assumptions. Do not claim that a simulated exercise proves operational readiness.
How should you schedule the examination?
Schedule only after you have verified eligibility, reviewed Oracle’s current exam page, and confirmed that the available appointment suits your preparation. Oracle lists the 1Z0-820 exam duration as 120 minutes. Oracle’s booking instructions state that candidates select a date, time zone, and time during scheduling, choose an available exam purchase, and accept the terms and conditions. Sources: https://education.oracle.com/oracle-certified-professional-oracle-solaris-11-system-administrator-upgrade/trackp_820 and https://education.oracle.com/file/general/Book%20Oracle%20Certification%20Exams%20-%20Base%20%26%20Delta.pdf.
The research snapshot does not establish the delivery method, available languages, current price, passing score, question count, or appointment availability. Check those details in Oracle’s live booking flow and certification information before committing. Do not rely on an old catalogue entry or a third-party listing for time-sensitive scheduling information.
When choosing a date, use readiness evidence rather than optimism. You should be able to explain the transition sequence, distinguish a preview from an update, describe what happens when an image upgrade needs multiple steps, and work through configuration, software, storage, network, security, user, and virtual-environment scenarios using official references. If one of those areas remains unfamiliar, postpone booking or reserve study time specifically for it.
During scheduling, verify that the credential path recognizes your prior Oracle Certified Professional Oracle Solaris Administrator or Sun Certified Solaris Administrator credential. Keep the confirmation and terms available for reference, but follow Oracle’s current instructions if the booking workflow changes.
Avoid scheduling immediately after completing a course. Course completion demonstrates exposure to material, not necessarily the ability to reason through a transition. Use a final review session to recreate the workflow from memory, consult the source when uncertain, and turn each correction into a short revision note.
What is a realistic study roadmap?
A four-stage roadmap works well for experienced administrators: eligibility and baseline, transition concepts, focused technical practice, and readiness review. Adjust the length of each stage to your background; the order matters more than assigning unsupported calendar promises or fixed study-hour targets.
Stage one, establish the baseline. Confirm the prior credential requirement, read the official certification path, and list the Solaris versions and administration tasks you know. Rate your confidence in each documented domain as strong, working, or unfamiliar. Do not use confidence alone: attach one observable proof to each strong rating, such as explaining a workflow or completing a controlled lab task.
Stage two, learn the transition model. Read the overview and installation-method sections in Oracle’s transition reference. Build the change matrix and identify differences involving devices, storage, file systems, software, networking, system configuration, security, virtual environments, and users. At this stage, aim to understand why a transition step exists before trying to memorize syntax.
Stage three, practice the high-consequence workflows. Use the current update documentation to rehearse package access, version checks, preview, boot-environment naming, and multi-step updates. Then practice post-change validation across the services and configurations relevant to your environment. Add targeted training from Oracle when the diagnostic list shows a real gap.
Stage four, perform a readiness review. Close your notes and explain the complete update workflow in order. Then choose a domain at random and answer three questions: what changes in Solaris 11, what administrator decision is required, and how would you verify the result? Reopen Oracle documentation to correct the answer. Repeat until your corrections are about precision rather than basic understanding.
The final review should include a one-page decision sheet, not a pile of copied text. Put eligibility, exam identity, update sequence, multi-step condition, boot-environment concept, and your domain checklist on it. Add links to the Oracle pages you used so that a disputed or changing detail can be checked at the source.
Book when the readiness review is stable across multiple sessions. If your performance varies sharply, investigate why: missing fundamentals, weak recall of release differences, lack of hands-on practice, or poor note organization require different remedies. More practice questions alone will not repair an unclear migration model.
Which mistakes waste preparation time?
The most damaging mistake is treating an upgrade exam as a compressed list of Solaris 11 commands. The upgrade path assumes prior Solaris administration knowledge, so preparation should concentrate on release differences, transition choices, dependencies, and verification. Memorization may support recall, but it cannot replace understanding the conditions under which an action is appropriate.
Do not assume that the exam has publicly verified percentage weights because a practice site presents them. The supplied official research gives domain names but no blueprint percentages. Keep the official label with each study area and distribute time according to your gaps and operational risk rather than comparing unsupported numbers.
Do not study only the package update command. Oracle’s procedure also requires package access, available-version checking, a preview, a named boot environment, and sometimes multiple update steps with a reboot before continuing. Ignoring those conditions produces a brittle understanding of the workflow.
Do not confuse optional preparation with eligibility. Oracle labels Transition to Oracle Solaris 11 and the Oracle IT Infrastructure Learning Subscription as optional preparation, while the prior Solaris credential is an upgrade-path requirement. Training can strengthen knowledge; it does not replace the prerequisite credential.
Do not use the old transition documentation without checking the current update procedure. The broader transition reference is valuable for organizing differences, but the Solaris 11.4 page provides the current sourced procedure in this research snapshot. When two documents address different scopes, note the scope instead of merging their instructions casually.
Do not treat a successful boot as complete validation. A transition can also affect software, networking, file systems, security, users, and virtual environments. Build checks around the role the system performs and record the evidence that each important function still works.
Finally, do not rely on exam dumps, leaked questions, or claims that memorization guarantees a pass. Use Oracle’s official path, training, and documentation, then practice explaining and validating administration decisions. That approach is both more defensible for certification preparation and more useful in real Solaris work.
What should you do next?
Your next action is to verify the prerequisite credential and open Oracle’s current 1Z0-820 certification page. If you are eligible, download or review the transition documentation, create a domain checklist, and test your knowledge against the update workflow before selecting training or an appointment.
Use this order: confirm the prior Oracle or Sun Solaris administrator credential; record your Solaris 10 and Solaris 11 experience; read the transition overview; study the current pkg update procedure; identify weak domains; choose optional Oracle training only where it addresses those weaknesses; perform controlled practice; then verify current booking details and schedule.
Keep the official URLs in your study notes. The certification path answers what the credential and prerequisite are. The catalogue confirms the exam’s placement under Solaris 11 Administration. The transition reference organizes the migration topics. The current update page explains the update sequence and multi-step condition. The booking document explains the scheduling flow. Using each source for its proper job reduces confusion.
A sensible stopping point is not “I have read every page.” It is “I can explain the transition decision, perform or accurately rehearse the update sequence, account for a possible intermediate boot environment, and validate the system across the domains relevant to its role.” That is the preparation standard this guide recommends; Oracle’s certification page remains the authority for official exam details.
Conclusion
The upgrade path is designed for an already-qualified Solaris administrator, not for replacing foundational administration study. Treat 1Z0-820 as a transition-and-operations examination: understand Solaris 10-to-Solaris 11 differences, study the documented administration domains, rehearse the package and boot-environment workflow, and validate changes across the whole system. Confirm eligibility and current scheduling information with Oracle before booking, then use targeted training and controlled practice to close the gaps your baseline review exposes.