1Z0-546 StorageTek Tape Libraries Essentials Exam Guide
Oracle identifies 1Z0-546 as StorageTek Tape Libraries Essentials, an exam associated with Oracle’s StorageTek tape-library technologies and listed in an Oracle University catalog under Other Sun Technologies. It is most relevant to professionals who support tape-based backup, archiving, library operations, or related storage infrastructure. This guide helps you decide whether the exam matches your work, which product concepts to study first, how to build a practical preparation sequence, and which Oracle University delivery requirements to verify before scheduling.
What does 1Z0-546 validate?
1Z0-546 is intended to validate foundational knowledge of StorageTek tape libraries and the technologies surrounding them. The supplied Oracle references identify the exam as “StorageTek Tape Libraries Essentials,” but they do not provide a verified blueprint, passing score, question count, exam duration, language list, or prerequisite requirement. Treat the title as the reliable scope signal and confirm live details in Oracle’s certification portal before registering.
The word “Essentials” points to product and operational understanding rather than a narrow command memorization exercise. A sensible candidate should be able to explain why an organization uses automated tape libraries, how library components support backup and archiving, and how availability, scalability, management, analytics, and encryption fit into an overall design. Those are preparation priorities derived from the official StorageTek product material, not a claim that every listed topic appears as a scored exam objective.
Oracle’s certification site describes certification as a way to demonstrate skills and validate knowledge. For this exam, the most useful interpretation is that a candidate should connect product capabilities to storage decisions: capacity growth, throughput, fault tolerance, offline protection, administration, and security. Studying disconnected feature names is less useful than learning the operational problem each feature addresses.
Who should consider it?
The strongest audience is a storage administrator, infrastructure engineer, backup specialist, data-center operator, or technical professional who works with enterprise tape environments or needs a structured introduction to StorageTek libraries. It may also suit someone supporting high-performance computing, cloud archive, or long-term data-protection environments where automated tape is part of the architecture.
Candidates who have only general IT experience should first learn tape-library fundamentals: media, drives, robotics, slots, control paths, data paths, partitions, monitoring, and key management. Candidates already responsible for StorageTek environments can spend less time on terminology and more time mapping architecture choices to failure handling, capacity planning, and administration. Oracle’s catalog context places the exam alongside Sun Storage products, so familiarity with older Sun and StorageTek naming may be useful, but the supplied sources do not define a formal experience threshold.
What is not verified in the supplied material?
Do not rely on an unofficial page for exact exam mechanics. The supplied official research does not verify the number of questions, time allowed, passing score, registration price, delivery language, retirement status, prerequisites, or a current detailed objective list for 1Z0-546. Check the official Oracle exam listing and certification portal immediately before making a scheduling decision.
Which technical areas deserve the most study time?
A practical study model has six connected areas: tape-library architecture, scalability and capacity, availability and networking, library management software, monitoring and analytics, and encryption and access control. This grouping follows the capabilities described on Oracle’s StorageTek page and gives you a way to organize notes even though no verified percentage-weighted blueprint was supplied.
Start with the system model. A tape library is not merely a collection of cartridges; it combines media, drives, robotics, slots, control software, connectivity, and operational policies. Then study how those components behave when capacity grows, a drive or control path fails, media is shared by applications, or encrypted data must be recovered. Each topic becomes easier when you can explain the dependency between components rather than recite a product description.
Tape-library architecture and use cases
Oracle describes StorageTek tape libraries as supporting offline storage, data protection, and petabyte-scale archiving. Study the reasons an organization may choose automated tape: separating protected copies from online systems, retaining data for long periods, controlling archive costs, and operating at enterprise, high-performance-computing, or cloud scale. The exam title does not justify assuming a particular deployment scenario, so prepare across these use cases.
Create a one-page architecture diagram with a host or backup application, library management layer, tape drives, robotics, media slots, network paths, and security components. Annotate each connection with its purpose. For example, distinguish the path used to move data from the path used to control library operations. This exercise exposes confusion that simple flashcards often hide.
Scalability, capacity, and performance
Oracle’s StorageTek material emphasizes modular growth, multiple tape generations, and centralized management. Relevant product examples include the SL150, which Oracle describes as scaling from 30 to 450 tape cartridges and supporting 8.1 PB of uncompressed capacity, and the SL4000, described as providing nondisruptive scalability up to 162 PB of uncompressed capacity. Keep each figure attached to its named product and capacity type.
The same source describes StorageTek designs with up to 57.6 EB of uncompressed tape capacity under a single pane of management and identifies LTO-9 technology as storing up to 18 TB of uncompressed data per cartridge. These are product-context facts, not universal limits for every StorageTek deployment. Learn the distinction between raw or uncompressed capacity, compressed capacity, cartridge count, drive count, and aggregate throughput.
Performance study should focus on trade-offs. More drives can increase parallelism, but a design still depends on host workload, media, network paths, robotics, and management policies. Oracle describes StorageTek tape drives as accessing data at up to 400 MB/sec per drive and describes a StorageTek configuration supporting 1 to 30 tape drives with up to 32.4 TB/hr of uncompressed throughput. Memorize the subject attached to each figure rather than treating them as interchangeable benchmarks.
Use comparison cards with four fields: product or technology, scaling characteristic, capacity or performance measure, and operational implication. A card might state that modularity allows incremental expansion, then explain why incremental expansion can avoid buying a fully sized system at the beginning. This is more useful than copying every marketing sentence into a revision document.
Availability, redundancy, and connectivity
High availability is a central design theme in the supplied StorageTek material. Oracle describes redundant, hot-swappable robotics, power supplies, and drives, along with online servicing and dedicated TCP/IP networking with optional dual or multi-control-path connectivity. Prepare to explain how redundancy, hot swapping, and multiple paths address different failure or maintenance conditions.
Do not collapse all resilience features into the word “redundancy.” A spare or redundant component addresses component failure; hot-swappable design addresses replacement without the same kind of interruption; multiple control paths address a control-path failure. Oracle also describes high-availability clustering for ACSLS and an n-node clustered design for Oracle Key Manager. Study these as separate mechanisms with different responsibilities.
A useful scenario exercise is to ask: what happens if a drive fails, if a power supply requires service, if a control path becomes unavailable, or if a management server fails? For each case, identify the affected function, the relevant resilience feature, and the recovery or continuity objective. Do not invent a product-specific recovery procedure unless Oracle training or documentation explicitly provides it.
ACSLS, partitioning, and shared resources
StorageTek Automated Cartridge System Library Software, or ACSLS, should be studied as a management and resource-sharing concept. Oracle states that ACSLS can share resources with any enabled application and allows customers to manage up to 32 libraries from a single console. Oracle also describes clustered ACSLS design as increasing availability during server failures and maintenance windows.
Partitioning creates logical boundaries within a physical library. Oracle describes partitioning as restricting access to logical libraries so organizations can improve capacity utilization and reduce costs. Sharing and partitioning are related but not identical: sharing aims to use common resources across applications, while partitioning controls how a physical library is presented or allocated. Build a table showing the administrative problem each feature solves.
Oracle also describes any-cartridge/any-slot technology as allowing drives and media to be located in any available location. The practical study question is not simply whether a feature exists; it is why flexible placement and logical allocation can improve consolidation. Consider competing applications, ownership boundaries, utilization, and the risk of creating an access policy that is too broad.
Tape Analytics and operational monitoring
Oracle describes StorageTek Tape Analytics as proactively monitoring and analyzing more than 300 health attributes so administrators can identify and correct errors before they affect data availability. Study this as a preventive-operations capability: telemetry and analysis can support earlier intervention, rather than merely reporting a failure after a backup or restore has already been disrupted.
When reviewing analytics, separate three ideas: what is monitored, what an administrator learns from the information, and what action follows. A health attribute is not the same as a diagnosis, and a warning is not the same as a completed repair. Prepare to explain how monitoring contributes to availability and maintenance decisions without claiming a particular alert workflow that the supplied sources do not document.
Make a fault-prevention worksheet. List a potential media, drive, robotics, or connectivity concern; identify the evidence an administrator would seek; and state the operational decision that evidence could support. Keep the final column conservative. “Investigate before the next protection cycle” is a valid study action; an invented command, threshold, or automatic remediation rule is not.
Encryption, key management, and access control
Oracle’s StorageTek material presents Oracle Key Manager as a security component for encrypted tape environments. It describes a highly available, clustered design with automated failover and dynamic load balancing, role-based management based on six NIST SP800-60 operational roles, and audit logging of all events. Study key lifecycle, availability, authorization, and auditability as connected requirements.
The key-management problem is broader than switching encryption on. A protected archive must remain recoverable when authorized systems need it, while access to keys must be limited and traceable. Oracle describes managing encryption keys for thousands of tape devices and millions of encryption keys as a scalability and administration concern. Use that context to reason about why clustering, role separation, and logging matter.
Practice explaining a secure restore path in plain language: an authorized application requests access, the key-management system validates the relevant authority, the encrypted media is read, and the event is recorded. This is a conceptual exercise, not a claim about the exact implementation sequence or interfaces tested by 1Z0-546.
How should you turn product facts into exam-ready knowledge?
Use a problem-to-capability method. For every major Oracle feature, write the operational problem, the feature or product associated with it, the expected benefit, and one limitation or dependency that must be checked. This forces you to understand why a capability matters and reduces the risk of selecting an answer merely because it contains familiar StorageTek terminology.
A strong study note might read: “Problem: protected data must remain separate from online systems. Capability: offline tape storage. Benefit: protection and long-term archiving. Decision point: plan media, access, recovery, and security operations.” Another might read: “Problem: a growing archive outgrows the initial configuration. Capability: modular expansion. Benefit: incremental capacity growth. Decision point: validate compatibility, throughput, and management requirements.” These are preparation examples, not leaked or reconstructed exam questions.
Use three layers of revision: terminology, relationships, and scenarios. Terminology confirms that you know what ACSLS, Tape Analytics, partitions, drives, slots, control paths, and key management refer to. Relationships show how those elements interact. Scenarios test whether you can select a suitable capability when the requirement changes. Spend most of your later preparation on the second and third layers.
Build a product matrix
Create rows for SL150, SL4000, SL8500, ACSLS, Tape Analytics, tape drives and media, and Oracle Key Manager. Use columns for primary purpose, scaling or availability idea, management implication, and evidence source. Add only claims you can trace to Oracle material. This matrix makes product distinctions visible and gives you a compact review document.
For the SL8500, Oracle describes a highly scalable environment with up to more than 3,200,000 tape cartridge slots under a single pane of management and up to 57.6 EB of uncompressed data in the supplied research. Keep those details tied to the named SL8500 context, and do not generalize them to every StorageTek library.
Explain trade-offs rather than slogans
Tape technology should be studied through design trade-offs. Offline storage can support protection and archiving, but it also requires disciplined media handling, cataloging, access planning, and recovery procedures. Modularity can simplify phased growth, but expansion still needs compatibility and performance planning. Centralized management can reduce administrative fragmentation, but access control and operational ownership must remain clear.
Oracle states that StorageTek tape libraries can lower total cost of ownership compared with disk-only archives by reducing energy usage and using automation to lower administrative costs. Treat that as a stated product value proposition, not as a guaranteed result for every organization. A serious answer considers workload, retention, access frequency, automation, security, and operational processes together.
Use source-linked recall
When a fact includes a product name, capacity, throughput, or count, preserve the complete label in your notes. For example, write “ACSLS: manage up to 32 libraries from a single console” rather than copying “32” onto a generic list. Write “Tape Analytics: more than 300 health attributes” rather than a bare number. This habit prevents inaccurate comparisons during final revision.
What preparation sequence works for a busy candidate?
Study in a deliberate sequence: establish tape and library fundamentals, map the StorageTek product family, learn operations and resilience, add security and analytics, then test yourself with scenarios. A candidate who starts by memorizing capacities usually lacks the architecture needed to interpret them. A candidate who begins with the system model can place each product fact in context and identify remaining gaps.
The sequence below is a practical recommendation, not an Oracle-mandated course plan. Adjust the pace to your existing StorageTek exposure and use the official portal to verify any available training, recommended learning, and certification requirements before committing to a date.
Stage one: establish the vocabulary
First, define the components and the data path. Be able to distinguish a cartridge from a slot, a tape drive from a robotic mechanism, and a data path from a control path. Add the roles of the backup application, library management software, monitoring system, and key-management platform. If you cannot draw the system, delay product memorization and resolve the basic terms.
Next, explain the business purpose of tape: offline protection, archive retention, capacity growth, and cost management. Keep security in the discussion from the beginning because encrypted media, keys, authorization, and recovery are not separate from archive design.
Stage two: organize the product family
Study the product pages in named groups rather than as one large list. Review SL150, SL4000, and SL8500 for library scale and modularity; review ACSLS for management, sharing, partitioning, and clustering; review Tape Analytics for proactive health monitoring; and review Oracle Key Manager for encryption administration, availability, roles, and audit logging.
After each group, close the source and explain the group aloud or in writing. If your explanation uses a feature but cannot state the problem it solves, revisit the material. This is a practical readiness test because it measures understanding without pretending to reproduce live exam content.
Stage three: connect operations to failure handling
Build four scenarios around component failure, maintenance, control-path loss, and management-server disruption. For each, identify the relevant availability design and the operational question that remains unanswered. For example, redundant components may support continuity, but you still need to understand which function is redundant and whether the scenario concerns data movement, robotics, or control.
Then add a utilization scenario involving multiple applications. Decide where sharing, partitioning, any-cartridge/any-slot placement, and centralized administration could help. Note the security or governance question that accompanies each design choice.
Stage four: perform retrieval practice
Replace passive rereading with closed-book retrieval. Write a short explanation of offline protection, modular capacity, high availability, ACSLS, Tape Analytics, Oracle Key Manager, and LTO-9. Then check the official source and correct imprecise wording. Include product labels whenever you record a supported figure.
Use scenario prompts that ask “which capability addresses this requirement and why?” rather than prompts that ask for a memorized definition only. Do not use dumps, leaked questions, or answer keys. They are not a substitute for knowledge and can encourage unsupported assumptions about the exam’s live content.
Stage five: verify the registration decision
Before scheduling, revisit Oracle’s certification portal and the official exam listing. Confirm that 1Z0-546 is available through the route you intend to use, review any current exam topics or preparation resources, and check the delivery instructions attached to your registration. The supplied research identifies the exam and its catalog context but does not establish every current administrative detail.
What should a four-week study roadmap look like?
A four-week roadmap is a planning template, not a promise that every candidate needs the same amount of time. Use the first part for architecture, the middle for product and operational relationships, and the final part for scenario review and delivery readiness. If your work already includes StorageTek administration, compress vocabulary review and expand failure, security, and integration practice.
Week one: build the system model
Read Oracle’s StorageTek overview and create the architecture diagram described earlier. Define offline storage, archiving, automated robotics, drives, media, slots, control paths, and data paths in your own words. End the week by explaining how a backup or archive workload moves through the environment and where an administrator could encounter a bottleneck or failure.
Do not spend this week trying to memorize every product figure. The objective is a coherent model that lets you classify later information correctly. Mark uncertain terms in a separate list and resolve them from Oracle sources rather than filling gaps with forum speculation.
Week two: study scale and administration
Review the SL150, SL4000, and SL8500 material, then study ACSLS, sharing, partitioning, and any-cartridge/any-slot operation. Build the product matrix and attach each verified number to its named product or capability. Compare administrative problems, not bare statistics: phased growth, centralized control, resource sharing, logical separation, and utilization.
At the end of the week, write several short design explanations. One should address a growing archive, another should address multiple applications using a consolidated library, and another should address the need to control access to logical resources. Keep the explanations conceptual unless an official Oracle document supplies implementation details.
Week three: study resilience and security
Focus on redundant and hot-swappable components, multi-path networking, clustering, Tape Analytics, encryption, role-based access, and audit logging. Draw a failure map showing which capability addresses which failure or operational risk. Then write a secure-restore explanation that includes authorization and key availability without inventing product commands or undocumented workflows.
Use this week to correct common category errors. Analytics is not the same as redundancy; partitioning is not encryption; a control path is not a data path; and a large capacity figure does not automatically describe throughput. These distinctions are more valuable than another pass through undifferentiated notes.
Week four: test understanding and prepare the appointment
Begin with a closed-book review of your architecture diagram, matrix, failure map, and source-linked facts. Use scenario questions you create from requirements, not copied or purported live exam items. For each answer, explain why the selected capability fits and why at least one alternative does not. Finish by checking Oracle’s current registration, exam-topic, and delivery information.
Reserve the final study sessions for weak areas, not wholesale rereading. If you repeatedly confuse products or functions, reduce the material to a smaller comparison table and practice reconstructing it. Once the technical review is stable, complete the official readiness check where available and verify your computer, connection, identification, and appointment details.
Which mistakes commonly weaken preparation?
The most damaging mistakes are usually scope and evidence mistakes: studying an assumed blueprint, memorizing isolated product numbers, treating product marketing as a universal guarantee, and ignoring the difference between technical readiness and appointment readiness. Correct these by maintaining a source-linked study file and testing explanations against operational scenarios.
A second problem is preparing only for a product tour. Tape-library knowledge becomes useful when it informs protection, archive, availability, capacity, management, and security decisions. If your notes contain many feature names but few “when would this matter?” explanations, your preparation is too passive.
Mistake: assuming unverified exam mechanics
Do not publish or plan around an unsupported question count, duration, passing score, language, price, prerequisite, or retirement date. Those details are absent from the supplied verified facts. Check the official Oracle listing and your registration confirmation instead. This is particularly important for an older catalog-listed exam whose availability and delivery route should be confirmed rather than inferred.
Mistake: comparing figures without their labels
A capacity figure for the SL150 is not a capacity figure for the SL4000, and uncompressed capacity is not compressed capacity. Likewise, per-drive access speed is not the same measure as aggregate library throughput. Keep the product, measure, and unit together in every note and answer explanation.
Mistake: confusing availability features
Redundant hardware, hot-swappable components, multi-path networking, clustering, and proactive analytics all support operational continuity in different ways. Do not answer a path-failure scenario with a media-capacity feature or a monitoring scenario with a partitioning feature. Build a failure-to-capability table and explain the mechanism behind each match.
Mistake: treating memorization material as preparation
Exam dumps and purported leaked questions do not establish understanding, may be inaccurate, and cannot guarantee a pass. They also encourage candidates to memorize wording rather than learn StorageTek architecture and operational reasoning. Use Oracle’s official product and certification material, your own scenario exercises, and any officially recommended learning instead.
Mistake: forgetting the operational context
A tape library can be highly scalable and automated, but an implementation still depends on administration, media policies, connectivity, monitoring, encryption, and recovery planning. When studying any feature, add one sentence describing the administrator’s decision and one sentence describing what must be verified before deployment.
What Oracle University delivery requirements are evidenced?
The supplied preparation page gives technical and check-in requirements for exams delivered by Oracle University, while explicitly warning that the instructions are not valid for exams scheduled and delivered by Pearson VUE. First identify the delivery route shown in your registration or confirmation email; then apply the matching official instructions instead of assuming that every Oracle exam follows the same process.
Computer and browser checks
For the Oracle University route, Oracle says to use the latest version of Chrome or Edge on Windows 11, Windows 10, or Mac OS X 13 or later, with administrator rights. Oracle states that iOS, Windows CE, Windows RT, Android, Chrome OS, and Linux are not supported, and that developer mode must be turned off. Verify these conditions before purchasing or scheduling if the route applies.
Oracle also states that Chromebooks and mobile devices are not supported, the operating system minimum RAM should be 8 GB or more, and only a single display is allowed. Close other applications and browser tabs before starting, leaving only the MyLearn Exam page tab open. Incognito mode and browser developer mode should be turned off.
Connection, camera, and keyboard
Oracle’s Oracle University instructions specify a consistent and reliable minimum internet speed of at least 3 mb/sec upload and download with a ping of less than 100 ms. They advise against mobile hotspots and tethered phone connections and require proxy and VPN connections to be disabled and disconnected. Test the actual exam computer and network, not merely a different device on the same premises.
The same instructions state that the webcam must have a minimum resolution of 640x490 at 10 fps. Check the webcam, audio, and microphone before exam day. Oracle also specifies an English QWERTY keyboard for this delivery route. These are official requirements, whereas arranging a quiet workspace and testing earlier than the appointment are sensible practical recommendations.
Identification and check-in timing
Oracle requires government-issued identification for the Oracle University exam process. The primary identification must exactly match the first and last name used for registration, be government issued and valid, and include a recent, recognizable photo. Accepted examples listed by Oracle include a passport, driver’s license, military ID, national or state identification card, and certain residency or school IDs.
For proctored exams, Oracle says candidates are required to check in at least 30 minutes before the scheduled start time. Candidates who try to check in after the scheduled exam time may not be admitted. Use the confirmation email and official preparation page to verify the process for your particular appointment, especially if the exam is delivered through another provider.
Cancellation and rescheduling
Oracle’s preparation guidance states that cancellation must be completed at least 24 hours before the appointment time and that rescheduling must also occur at least 24 hours before the appointment time. The page warns that failing to cancel at least 24 hours in advance risks forfeiting the exam attempt. Treat these as scheduling-policy requirements for the applicable Oracle University route and recheck the policy before changing an appointment.
Oracle’s certification page describes a workflow of buying an exam attempt, choosing a date, and scheduling through Oracle MyLearn, and states that you have six months to take your exam. Confirm that this workflow and time window apply to the specific 1Z0-546 registration you are viewing rather than assuming that a catalog reference guarantees identical purchasing terms.
Digital whiteboard and prohibited paper
Oracle states that pen and paper are not allowed during the exam and that a digital whiteboard is available in the exam delivery platform. If you expect to sketch paths or capture a short reminder, practice using the platform’s permitted tool during any official readiness activity. Do not bring physical notes or plan to use unapproved applications.
How should you decide whether to schedule now?
Schedule only after two separate checks pass: a knowledge check and a delivery check. Knowledge readiness means you can explain the architecture, identify the purpose of the named technologies, reason through availability and security scenarios, and preserve product-specific facts accurately. Delivery readiness means the official listing, route, appointment policy, system, connection, identification, and check-in requirements are all understood.
A practical knowledge gate
You are closer to ready when you can draw a StorageTek library environment from memory, explain the distinction between control and data paths, describe why modularity and partitioning matter, and connect ACSLS, Tape Analytics, and Oracle Key Manager to operational needs. You should also be able to identify which facts are verified and which exam details still require confirmation from Oracle.
If your confidence depends on recognizing copied answer wording, postpone scheduling and return to scenarios. A useful self-test is to explain one design for incremental capacity, one for shared applications, one for component or path resilience, one for proactive monitoring, and one for encrypted archive access.
A practical appointment gate
Confirm the exam identity and availability in Oracle’s official portal, identify whether the delivery is through Oracle University or Pearson VUE, and read the instructions attached to that route. If Oracle University delivery applies, complete the readiness check where available, validate the supported operating system and browser, test the connection and camera, prepare acceptable identification, and plan to check in at least 30 minutes before the start time.
If any requirement is uncertain, resolve it before the appointment rather than relying on a last-minute workaround. In particular, do not assume that Linux, a Chromebook, a mobile hotspot, multiple monitors, a VPN, physical paper, or an expired identification document will be accepted under the Oracle University instructions.
What should you do next?
Begin by opening the official Oracle exam listing and the Oracle certification portal to confirm the administrative facts that the supplied research does not verify. Then download or review the StorageTek product material, create the architecture diagram and product matrix, and start the first vocabulary session. Keep a dated checklist of what Oracle confirms for your registration and what remains a personal study recommendation.
For a focused first session, complete these tasks: write a plain-language definition of the exam’s StorageTek scope; draw the library, application, management, monitoring, and security relationships; list the six study areas; mark every unsupported exam mechanic as “verify officially”; and schedule your next review block. That gives you an evidence-led starting point without pretending that unofficial materials reveal the live assessment.
The goal of this guide is not to predict questions. It is to help you build the product understanding and scheduling discipline needed to make a responsible decision about 1Z0-546. Use Oracle’s official sources for registration and delivery facts, and use scenario-based study to turn StorageTek terminology into practical storage reasoning.
Conclusion
1Z0-546 preparation should combine StorageTek architecture, product relationships, operational scenarios, and verified appointment planning. Focus first on how libraries provide offline protection and scalable archiving, then connect ACSLS, availability features, Tape Analytics, and Oracle Key Manager to real administrative requirements. Because the supplied sources do not establish a complete exam blueprint or every current administrative detail, confirm those items through Oracle before scheduling. A source-linked study matrix, failure map, and final readiness check will give you a more reliable preparation basis than memorized claims or exam-dump material.
Related exams
- 1z0-116 exam — Oracle Database Security Administration
- 1z0-202 exam — Siebel 8 Consultant Exam
- 1z0-343 exam — JD Edwards EnterpriseOne Distribution 9.2 Implementation Essentials
- 1z0-516 exam — Oracle EBS R12.1 General Ledger Essentials
- 1z0-518 exam — Oracle EBS R12.1 Receivables Essentials
- 1z0-519 exam — Oracle EBS R12.1 Inventory Essentials
