Who it's for#
Whoever answers for the whole solution, not for one layer of it: the technical lead of an implementation, the consultant who signs the proposal, the partner with a multi-company portfolio, and the IT person who will be the ingestia.io reference inside the company.
It is not the credential for someone starting out: it is the last one in the pyramid. Whoever masters a layer has that layer's certification — and that alone is a career. This one exists to separate whoever masters a layer from whoever answers for the whole.
Prerequisites#
| Requirement | Why |
|---|---|
| Valid ICF — Fundamentals | the platform's shared vocabulary |
| Valid ICED — Data Engineer | without knowing how to bring the data in, there is no solution |
| Valid ICBI — BI Analyst | without knowing how to turn it into a decision, the data is useless |
| Valid ICIA — AI Agent Engineer | AI in the flow is part of the design, not an ornament |
The three must be valid at the moment the ICSA is issued. If one of them expires later, the ICSA stays valid until its own expiry — its recertification checks the current state of all three.
How to earn it#
- Hold the ICF badge and the three certifications valid.
- Complete the Solutions Architect track: ACD-240 → ACD-250 → ACD-260 (~11 h), which comes after the three role tracks.
- Pass the exam (below).
- Pass the hands-on challenge End-to-end Aurora solution.
How to verify it
Once issued, the credential gets a public page with the code and a fingerprint (hash) — and whoever only has the paper in hand verifies it at /academy/validar.
Exam blueprint#
| Domain | Weight |
|---|---|
| D1 Solution architecture (read the problem, choose the design) | 25% |
| D2 From data to dashboard: the whole path and where it breaks | 20% |
| D3 AI in the flow: when it fits, when it does not, under what control | 15% |
| D4 Security, access and LGPD running across the layers | 15% |
| D5 Cost and plan: the financial design of the operation | 15% |
| D6 End-to-end operations and incidents | 10% |
- 50 questions drawn by domain from a bank of 200 · 110 minutes · passing score 75% — the highest in the Academy. Fewer questions and more time, on purpose: a scenario is read before it is answered.
- Feedback by domain. Honor code. Retake: 14 days; at most 3 attempts in 12 months.
Why this exam is mostly scenarios
About 70% of the questions are scenarios (against 15–30% in the other credentials): a 3-to-8-line case — company, budget constraint, deadline, contracted plan, small team, LGPD requirement — and the question is which design or which trade-off.
The reason is simple, and it is the point of the capstone: the mechanics have already been proven. Whoever gets here has already demonstrated, across three exams and three machine-graded challenges, that they can configure an incremental load, write CALCULAR, tag PII, set up RLS, schedule a report and cap an AI budget. Measuring that again would measure what is already measured. What has not been measured is deciding under constraint: choosing between freshness and cost, between one workspace and several, between solving it with a pipeline or with a data mode, between putting AI in the flow and letting the deterministic path handle it. That is what the 50 questions ask.
The other 30% split between multiple answer (what must all be true for the design to work), "what is wrong" (a broken design, find the cause) and "what is the state" (what is Preview, what is Roadmap, what is out of GA) — because an architect who promises what the product does not deliver causes more damage than an architect who gets a formula wrong.
The
icsabank is in transition to this design: it inherits the security, FinOps and integrations domains from the old ICSA (which was the data credential, today ICED) and receives the new cross-cutting questions. While the rewrite is unfinished, the draw uses the published domains and the exam page declares the bank version — no attempt is opened half-built, and no item examines what the product does not deliver.
Recertification#
At the end of 1 year: a delta exam of 25 questions in 40 minutes, cut-off 70%, focused on what changed on the platform in the period (connectors that left Preview, plan limits, new AI capabilities). No challenge. Recertification is not open yet and its price is not decided.
The capstone's recertification is the only one that looks at the credentials below it: if any of the three has expired, the delta includes 5 questions from its domain. Letting the ICSA expire does not invalidate the three; letting the three expire does not invalidate an already-issued ICSA.
What this certification does NOT claim#
It does not claim that the holder operates on your behalf — it is not a license, a power of attorney or a service contract; responsibility for the delivered solution belongs to whoever signs it.
It does not claim availability beyond what is published. The contractual availability of ingestia.io is the plan SLA — 99.5% monthly from Growth up, with service credits, measured at /status (/legal/sla). A certified architect knows — and the exam examines — that the REST query API is out of GA, that keyless BYOC (WIF) is Roadmap, that webhook signing via API does not exist yet, that RPO/RTO and disaster recovery are not part of the published SLA and that ERP/Ads/CRM connectors are in Preview without a completed 30-day operational certification. The credential proves designing precisely around those limits, never denying them.
It does not claim deep operational mastery of each layer beyond what the three base certifications already proved, nor does it replace any of them.
It does not claim competence in customer cloud (BYOC) as a deliverable capability: the multi-project design exists as a document, not as a product, and the exam asks exactly that.