Certification is a conversation as much as a count. Oracle will probe how you measured, where you deployed, and what you can prove. Knowing the questions ahead of time lets you answer from a prepared position rather than improvise under pressure.
By Daniel Voss · Ex Oracle LMS · 4 June 2026
At ULA certification Oracle commonly asks how you measured your deployment, which tools or scripts produced the numbers, where the products run including virtualised and cloud environments, whether every in scope entity is included, and what evidence supports each figure. The questions test the basis of your count rather than the count itself. The way to win the exchange is to have already measured independently, reconciled to the contract, and assembled an evidence file, so each question meets a prepared answer.
It is tempting to picture certification as the act of submitting a number and receiving a confirmation. In practice it is an exchange. You present your count, and Oracle tests how you arrived at it. The questions are rarely hostile, but they are purposeful, and each one is an opportunity for the conversation to move in your favour or against it. An organisation that has thought about its answers before the questions arrive controls the pace and the framing. One that improvises gives ground it did not need to give.
The single most useful preparation is to understand what each question is actually testing. Oracle is not collecting trivia. It is probing the soundness of your measurement, the completeness of your scope, and the strength of your evidence, because those are the three things that determine whether your declared number stands. When you can see the intent behind a question, you can answer the intent rather than the surface, and you avoid volunteering detail that opens new lines of inquiry.
The questions vary by engagement, but they cluster around a handful of themes. The table below sets out the questions you should expect, what each is really testing, and the posture that answers it cleanly.
| The question | What it tests | The prepared posture |
|---|---|---|
| How did you measure? | Soundness of method | A documented methodology you can explain |
| Where does it run? | Virtualisation and cloud scope | A clear map of environments and how each counts |
| Are all entities included? | Customer definition and scope | Reconciliation to the contract scope |
| What is your evidence? | Defensibility of the count | An assembled evidence file per figure |
Indicative. The exact questions and their emphasis depend on your products, your deployment, and the wording of your agreement.
Every question Oracle asks at certification has a right answer that was prepared weeks earlier. The exchange is not where you build your position. It is where you present a position already built. Surprises in the room favour the vendor.
One question deserves separate treatment because it is so often misunderstood. Oracle may ask you to run its License Management Services measurement scripts to produce the deployment data. Many organisations treat this as a requirement and comply automatically. In most agreements it is not a requirement. Running the scripts is a choice, and it is a choice that shapes what Oracle sees and how the certification conversation unfolds. You are generally entitled to present your own independent measurement and evidence instead.
This does not mean the scripts are always the wrong answer. It means the decision deserves analysis rather than reflex. The scripts produce output on Oracle's terms, in Oracle's format, surfacing whatever Oracle's methodology surfaces. An independent measurement lets you present a count you understand and can defend, framed around your contract. Which approach serves you depends on your estate, your evidence, and your contractual position. The mistake is not choosing one or the other. The mistake is not realising there was a choice.
The pattern across every question is the same. Strength comes from preparation, and preparation means three things complete before the conversation starts. First, an independent measurement of your deployment, so you know your own number and how it was derived. Second, a reconciliation of that number to your contract scope, so you can confirm every included entity and environment belongs. Third, an evidence file behind each figure, so that when Oracle asks what supports a number you can produce it rather than promise it.
With those three in place, the questions become straightforward to answer because you have already answered them for yourself. Without them, each question is a small crisis, answered on the spot, often by conceding rather than defending. The work that makes certification calm is not done in the room. It is done in the weeks before, and it is the same work that makes the certified number complete and the post certification audit position strong.
The questions at certification reward the organisation that prepared and expose the one that did not. Ground your preparation in our Oracle ULA certification guide, get the declaration itself right with what the certification letter must contain, and avoid the errors that come back later in the certification mistakes that haunt you later.
Book a ULA assessment and we will measure your estate, build the evidence, and prepare you for the exchange so Oracle's questions meet your prepared position.