EX294 Deploy Ansible Automation Platform Practice Question
An administrator deploys AAP 2.4 with an external PostgreSQL database. After the installation completes, the automation controller web UI is reachable, but jobs fail immediately with database connection errors. The administrator confirms the database host is reachable on port 5432 and the credentials in the inventory are correct. Which action should be taken to resolve the issue?
⚠ Common exam trap
The trap here is equating network reachability with database readiness, overlooking that extensions and pg_hba.conf rules are also required for an external PostgreSQL deployment.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Verify that the external database has been configured with the required extensions and that the pg_hba.conf allows connections from the controller node's IP address.
When using an external PostgreSQL database with AAP, the database must be prepared with specific extensions and the pg_hba.conf must allow the controller host to authenticate. Port reachability and correct credentials in the inventory are necessary but not sufficient. The other options either target the wrong host, introduce an unrelated change, or re-run the installer without fixing the underlying database configuration.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Change the database port in the inventory to 5433 and re-run the installer.
Why it's wrong here
The administrator already confirmed the database listens on 5432 and is reachable, so changing the port is unnecessary and would break the configuration. This distractor misdirects toward a port issue when the real problem lies in database preparation or access rules.
- ✗
Open port 5432 in firewalld on the controller node.
Why it's wrong here
The controller node initiates connections to the database, so the relevant firewall is on the database host, not the controller. Opening 5432 on the controller would not affect outbound connections and would not resolve authentication or extension failures.
- ✗
Re-run setup.sh with the --force flag to regenerate the controller configuration.
Why it's wrong here
Re-running the installer does not fix an external database that lacks required extensions or proper pg_hba.conf entries. The --force flag is not a documented remedy for this scenario, and it could disrupt a working deployment without addressing the root cause.
- ✓
Verify that the external database has been configured with the required extensions and that the pg_hba.conf allows connections from the controller node's IP address.
Why this is correct
For an external database, PostgreSQL must have the necessary extensions (such as hstore and pg_trgm) and pg_hba.conf must permit the controller's IP with the correct authentication method. A reachable port alone does not guarantee authentication or extension availability, so these are the likely missing pieces.
Visual reference
Go deeper
Related to this question
About these practice questions
This EX294 question is part of Courseiva's 392-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →
JA
Written and reviewed by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
Last reviewed September 2026 · checked against the official Red Hat exam blueprint
This EX294 practice question is part of Courseiva's free Red Hat certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the EX294 exam.