EX294 Manage automation security and operations Practice Question
Exhibit
Refer to the exhibit. In automation controller, a job template named 'Deploy App' has the following configuration:
- Inventory: Production
- Project: App_Project
- Credential: Machine credential 'prod_ssh'
- Verbosity: 0 (Normal)
- Job Type: Run
- Extra Variables: {"env": "production"}
A member of the Operations team launches this job template and sees the job status as 'pending' for several minutes before it eventually runs. What is the most likely cause?Refer to the exhibit. What is the most likely cause of the job being in 'pending' state?
⚠ Common exam trap
Red Hat often tests the distinction between 'pending' (capacity queue) and 'awaiting approval' (survey or workflow approval), so candidates mistakenly choose the survey option when they see a job not starting immediately.
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
✓
The job is queued because the capacity limit of the automation controller is reached.
In Ansible Automation Platform, when a job is in 'pending' state, it typically indicates that the automation controller has queued the job because the maximum number of concurrent jobs (capacity limit) has been reached. The controller uses a job fork limit and instance group capacity to determine how many jobs can run simultaneously; once that limit is hit, additional jobs are placed in a pending queue until capacity frees up.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
The job is queued because the capacity limit of the automation controller is reached.
Why this is correct
Reaching the automation controller's capacity limit caps concurrent job execution, so the task queues in 'pending' until a running job finishes and frees a slot. This matches the stem's constraint: the exhibit shows no execution errors, only a job awaiting available capacity rather than failing outright.
- ✗
The credential is invalid and the system is attempting to validate it.
Why it's wrong here
An invalid credential causes the job to fail with an authentication error rather than remain pending. It is tempting because credential problems do block job execution, and checking credentials would be correct if the job showed a failed status with an authentication message.
- ✗
The job template is configured with a survey that requires approval.
Why it's wrong here
A survey requiring approval does not place a job in pending; surveys prompt for variables at launch, and approval gates apply to workflow nodes. It is tempting because surveys and approvals both pause execution, and a survey would be correct if the job were waiting for user-supplied extra variables.
- ✗
The project needs to be updated before the job can run.
Why it's wrong here
A stale project does not hold a job in pending; project updates affect which playbooks and inventories are available, not job scheduling. It is tempting because project sync issues can prevent launches, and updating the project would be correct if the job failed immediately with a missing playbook error.
Go deeper
Related to this question
About these practice questions
Courseiva writes every EX294 question from scratch — 392 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or dumps. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
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.