More study resources

About this exam

The EDB PostgreSQL Associate is an early-career certification intended to show that a candidate has a solid working foundation in PostgreSQL - the open-source database that EDB has contributed to since 2006 and builds its commercial products on. It is aimed at database administrators, developers, data engineers and platform engineers who are starting to run Postgres in real environments, and at professionals arriving from another relational platform who need to prove they can transfer their skills. Because the blueprint is deliberately broad rather than deep, it rewards candidates who have actually installed, configured and used a Postgres instance rather than those who have only read about one.

The exam is organized into eight domains of roughly equal weight (12.5% each according to the published blueprint): PostgreSQL architecture and installation; SQL fundamentals and data types; database objects and schema design; data manipulation and querying; backup, restore and recovery; security and access control; performance monitoring and tuning; and replication and high availability. That spread means no single topic can carry a pass on its own, and a weak domain is expensive. Preparation works best as a lab-first routine: install Postgres, work through the official documentation, practise with psql, break and restore a cluster deliberately, and use EDB's published training and product documentation as a structured reading track alongside hands-on exercises.

What you'll study

Common questions

About EDB PostgreSQL Associate preparation

What is the exam format?

The published blueprint lists multiple-choice questions. Question count, time limit, passing score and delivery method are not stated in the source material reviewed for this page, so confirm the current details with EDB before you book a seat rather than relying on second-hand figures.

How difficult is the exam?

It is pitched at associate level, so questions test working familiarity rather than expert depth. The real difficulty is breadth: eight domains of equal weight mean you cannot skip backup, security or replication just because you are strong in SQL. Candidates with a few months of hands-on Postgres use usually find it manageable.

How long should I allow for preparation?

No official preparation time is published. A practical approach is to budget study time per weak domain rather than a single total: if you already administer Postgres daily, focus on the two or three domains you rarely touch; if you are new, plan several weeks of lab work before attempting it.

Is there a retake policy?

Retake rules, waiting periods and any associated costs are not described in the source material reviewed here. Check EDB's certification or training pages, or contact their team directly, so you know your options before exam day instead of after a disappointing result.

What study order makes sense?

Follow the dependency chain: architecture and installation first, because everything else assumes you understand the cluster, WAL and the process model; then SQL and data types, objects and schema design, and querying; then backup and recovery and security; and finally performance tuning and replication, which draw on all the earlier material.

Do I need a lab, or is reading enough?

Build a lab. Reading alone tends to fail on the operational domains - you need to have taken a base backup, replayed WAL, edited pg_hba.conf, read an EXPLAIN plan and set up a streaming replica at least once. Those experiences are what the scenario-style questions are really testing.

Where do common failures cluster?

Watch MVCC and vacuum behaviour, pg_hba.conf rule ordering and authentication methods, privilege inheritance and search_path, recovery target settings, replication slots and lag, and interpreting EXPLAIN output. These are areas where a superficially correct answer is often wrong, so practise them rather than memorising definitions.

Does the exam target a specific PostgreSQL version?

The blueprint does not tie the domains to a version number. Core SQL, object and security behaviour is stable across recent releases, but installation paths, configuration defaults and backup tooling change between majors, so study against a current release and check EDB's platform compatibility documentation for supported versions.

Is it about PostgreSQL generally or EDB products?

The eight published domains are general PostgreSQL topics - architecture, SQL, objects, querying, backup, security, tuning and replication - rather than walkthroughs of a specific commercial product. Knowing EDB's ecosystem helps with context, but expect the questions to test Postgres fundamentals you would use on any deployment.