> For the complete documentation index, see [llms.txt](https://academy.pentaho.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://academy.pentaho.com/pdi-developer-path-sandbox/pdi-developer/level-3-certified.md).

# Level 3 — Certified

For PDI Developers, Level 3 — Certified is the Solution Architect path: DI Developer, Installation, then the Containers, High Availability and Enterprise Security Speciality courses.

{% hint style="warning" icon="eye" %}
**SANDBOX — draft page.** For review only. Items marked REPLACE-ME need an owner's confirmation.
{% endhint %}

There is no separate Level 3 course on the PDI Developer path. After Level 1 — Practitioner, the route to certification is the **Solution Architect path**: DI Developer, Installation, then the Containers, High Availability and Enterprise Security Speciality courses, leading to the Certified Solution Architect certification.

{% hint style="info" icon="compass-drafting" %}
**The Solution Architect path, in order**

1. DI Developer (the same course as PDI Developer, Level 1 — Practitioner) — this path's Level 1
2. Installation
3. Containers — Speciality
4. High Availability — Speciality
5. Enterprise Security — Speciality

Complete all five and pass the proctored exam to hold the Certified Solution Architect certification. The PDI Speciality courses (Machine Learning, Streaming Data, AI Pipelines and Pipeline Designer) are not part of it; they stand alone.
{% endhint %}

<p align="center"><a href="https://academy.pentaho.com/solution-architect-path-sandbox/solution-architect.md" class="button primary" data-icon="compass-drafting">Go to the Solution Architect path</a></p>

***

<p align="center"><a href="https://academy.pentaho.com/pdi-developer-path-sandbox/pdi-developer.md" class="button secondary" data-icon="arrow-left">Back to the PDI Developer path</a></p>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://academy.pentaho.com/pdi-developer-path-sandbox/pdi-developer/level-3-certified.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
