orchestrate-multi-agent-coordination

GitHub Certified: Agentic AI Developer (GH-600) · 55 questions

• Two agent instances are running in parallel on the same repository. Agent A is refactoring the payment module, and Agent B is adding new features to the same module. What configuration is required to prevent them from interfering with each other?
• In a multi-agent workflow, Agent A and Agent B are both assigned tasks that involve modifying the shared configuration file config/settings.json. What mechanism should detect this overlap before the agents begin execution?
• In a three-agent pipeline where Agent A researches requirements, Agent B implements code, and Agent C reviews the implementation, which documentation practice best captures the handoffs and key decisions across all three agents?
• After a multi-agent workflow completes, a developer wants to understand why Agent B produced unexpected output. The workflow system logs all agent inputs, outputs, tool calls, and timestamps. Which analysis approach is most effective for diagnosing the root cause?
• An orchestrator monitors a multi-agent workflow and notices that Agent C has been in 'running' status for 45 minutes with no log output and no tool calls recorded in the last 30 minutes, while all other agents completed within 10 minutes. Which conclusion is most appropriate?
• In a multi-agent workflow, one of five parallel agents stops producing output and its assigned tasks remain incomplete. The other four agents have completed their tasks and are waiting. How should the system respond?
• A team's existing multi-agent workflow has a security scanning agent that consistently produces false positives, causing downstream agents to unnecessarily halt. The team wants to replace it with a more accurate scanning tool. What is the correct sequence of steps to safely replace the agent within the workflow?
• In a multi-agent pipeline, Agent A produces a structured JSON artifact and hands it off to Agent B. Agent B expects a specific schema but receives a malformed artifact. What design practice prevents this handoff failure?
• In a multi-agent deployment pipeline, the testing agent fails to complete its task after 3 retries. The deployment must not proceed without passing tests. What should the orchestrator do?
• A compliance audit requires a complete record of which agent performed which action, in what order, and what the inputs and outputs were for a multi-agent deployment pipeline. What design practice enables this audit trail?
• A platform team needs an agent system to apply a security patch to 20 independent microservices simultaneously. Each microservice has its own repository and independent test suite. The changes in each repository do not depend on the outcome of any other repository. Which orchestration pattern is MOST appropriate for this task?
• A team runs two agents in parallel to refactor a large service. Agent A is assigned to the authentication module and Agent B is assigned to the API routing module. Both agents are working on the same feature branch. After their changes are committed, the team discovers merge conflicts in src/api/auth.ts because both agents modified the same file. What configuration change would have prevented these conflicts?
• In a multi-agent system, Agent A generates a parseTimestamp() utility function in src/utils/time.ts, while Agent B independently generates a nearly identical formatTimestamp() function in src/helpers/dates.ts. Neither agent knew the other was generating similar code. This duplication leads to inconsistent behavior across the codebase. What mechanism should be added to the multi-agent system to detect and prevent this type of duplicated effort?
• An orchestrator agent delegates a data processing module to two subagents. Subagent 1 implements the module using async/await with Promises, while Subagent 2 implements the same module using callback patterns. When the orchestrator receives both outputs, they are architecturally contradictory and cannot both be merged. What is the correct resolution strategy for the orchestrator?
• A compliance audit team requires a complete, verifiable record of every code change made during a multi-agent refactoring workflow, including which specific agent produced each change and when. The audit team needs this to satisfy SOC 2 change management requirements. What should the multi-agent workflow produce to satisfy this requirement?
• In a multi-agent pipeline, Agent A designs a database schema and completes its work. Agent B is then triggered to generate the data access layer using that schema. However, Agent B produces an incompatible data access layer because it was not given Agent A's schema output — it designed a schema independently from the task description alone. What should have been configured to prevent this handoff failure?
• An orchestrator agent triggered a subagent 45 minutes ago to refactor a complex service module. The subagent's assigned GitHub Issue has not been updated, no commits have been pushed to its branch, and the orchestrator has received no status messages. The subagent appears to be completely unresponsive. What should the orchestrator do?
• A multi-agent system has five coordinating agents. One subagent begins returning malformed JSON in its inter-agent messages. The other four agents are consuming this malformed JSON, failing to parse it, and propagating the error by passing partial data to their own downstream consumers. The cascading failure is spreading across the system. What is the correct immediate response?
• A team wants to upgrade their documentation agent (v1) to a newer version (v2) that uses a different output format. Five other agents currently depend on the documentation agent's output. A direct cutover to v2 would break all five downstream agents simultaneously. What approach BEST minimizes risk during this lifecycle transition?
• Two parallel agents in a GitHub Actions workflow are both assigned to update a shared configuration file, config/settings.yaml. After both agents complete, the file contains only one agent's changes — the other agent's changes are silently overwritten. What is the PRIMARY architectural fix to prevent this overlapping-change conflict?
• An orchestrator assigns a refactoring task to two subagents simultaneously: Agent A is tasked with updating function signatures in apiclient.py and Agent B is tasked with updating callers of those functions in the same file. Both agents complete their tasks and commit their changes. When the commits are merged, the file contains conflicting edits and broken function calls because both agents modified overlapping sections without knowledge of each other. What coordination mechanism was missing?
• After deploying a multi-agent pipeline on GitHub Actions, you notice that Agent B consistently stalls indefinitely after Agent A completes its step. Agent B is waiting for a signal that never arrives. Logs show Agent B entered a waiting state but there are no timeout or error entries. What is the MOST LIKELY root cause of this stalled execution?
• An orchestrator dispatches five subagents to process five independent modules of a codebase in parallel. Four subagents complete within 10 minutes and report results. The fifth subagent stalls due to an internal deadlock but never reports failure — it remains running indefinitely. The orchestrator waits indefinitely for the fifth result, blocking the entire workflow from completing. What mechanism was missing?
• A team building a multi-agent research pipeline reports that downstream agents are producing irrelevant outputs. After investigation, you discover that each agent only receives the raw task description but not the decisions, reasoning, or intermediate results from previous agents. Which practice BEST addresses this handoff documentation failure?
• A multi-agent pipeline processes pull requests in stages: Agent A reviews code style, Agent B checks security, and Agent C generates the final review summary. Agent A and B complete and pass the PR to Agent C. Agent C produces a summary that contradicts findings from Agent A, misses a critical security note from Agent B, and asks questions that Agent A already answered. The orchestrator passed only the PR URL between agents, not the prior agents' findings. What was missing?
• An orchestrator agent delegates a security assessment task to a subagent. The subagent returns a report stating 'No vulnerabilities found,' but a separate verification agent had already flagged three critical CVEs in the same codebase. The orchestrator accepts the subagent's report and marks the task complete. Which control is MISSING that allowed this contradictory output to be accepted?
• After a multi-agent workflow produces an incorrect output, the engineering team tries to reconstruct which agents ran, in what order, what each agent decided, and why. The orchestrator has no coordination log — only the final output exists. The team cannot determine whether the failure originated in Agent A's analysis, Agent B's transformation, or the orchestrator's routing. What should have been built into the orchestrator?
• In a three-agent pipeline (Agent 1: parse requirements, Agent 2: generate code, Agent 3: write tests), Agent 1 returns a malformed requirements object due to an upstream data issue. Agent 2 uses this data to generate code, and Agent 3 writes tests for the broken code. All three agents report success. The team later finds the entire output is unusable. What pattern would have contained this cascading failure?
• A team reports that their multi-agent code review pipeline is taking twice as long as expected. Investigation shows that Agent A (assigned to 'security review') and Agent B (assigned to 'code quality review') are both independently scanning the same set of files for the same OWASP Top 10 vulnerability patterns and producing nearly identical reports. What orchestration failure is occurring and what is the correct fix?
• A team decides to replace Agent V1 with a new Agent V2 that has been tested and validated. Agent V1 is currently mid-task on three long-running workflows. The team immediately stops Agent V1 and deploys Agent V2. Agent V2 is not given the in-progress workflow state, context from prior steps, or any record of what Agent V1 had completed. All three workflows must restart from scratch. What process should have been followed?
• A team uses two agents to generate code for different modules of the same service. When the modules are integrated, developers find they use completely different naming conventions, error handling patterns, and code structure — one uses camelCase with try/catch blocks, the other uses snakecase with result tuples. No conflicts occur during generation. What coordination element is missing?
• A multi-agent pipeline partially completes a production database migration before Agent 3 fails mid-task. The team attempts to recover, but discovers there is no mechanism to reverse Agent 1's and Agent 2's already-completed changes. The database is now in a partially migrated, inconsistent state. Which recovery pattern was MISSING from this pipeline's design?
• An orchestrator dispatches a subagent to analyze 200 files in a repository. The subagent successfully analyzes 180 files but times out before completing the remaining 20. The subagent discards all results because its implementation returns only when all 200 files are complete. The orchestrator receives no output and treats the entire analysis as failed. What design would have produced a better outcome?
• A team reports that their orchestrator's human-in-the-loop (HITL) approval gate consistently triggers after irreversible actions have already been taken — for example, cloud resources are deleted before the human approver is notified. Which design principle was violated, and what is the correct fix?
• A platform needs to independently refactor 5 separate modules (auth, payments, notifications, reporting, search). An orchestrator agent should assign each module to its own subagent for parallel processing. Which coordination pattern and GitHub mechanism best implements this fan-out?
• In a pipeline where a test-writing agent passes its output to a code-review agent, the code-review agent receives a handoff artifact with a malformed schema — the required testCoverage field is missing. What is the correct behavior for the receiving agent?
• Five subagents are working in parallel on different modules of the same repository. Without coordination, two agents modifying the same files would cause conflicts. What branching strategy best isolates each agent's work?
• After a multi-agent pipeline run, an audit team requests the pipeline's audit artifact to reconstruct what happened. The artifact exists but is missing the worker agents' individual decision rationales, retaining only the final coordinator output. What critical information gap does this create?
• After five parallel subagents complete their module refactoring work, the orchestrator needs to create a unified artifact that summarizes all changes for human review and final approval before merging. What is the best approach?
• Two worker agents independently review the same pull request and produce mutually contradictory suggestions for the same function: Worker A recommends extracting the function into a utility module, while Worker B recommends inlining it for performance. The coordinator must produce a single review. How should it handle the conflict?
• A multi-agent pipeline that generates API documentation produced an incorrect output three days ago. The pipeline included a research agent, a drafting agent, and a formatting agent. Logs exist but are unstructured. Audit artifacts were not created during the run. What limitation does this create for post-hoc analysis?
• Three worker agents are running in parallel to analyze different modules of a large codebase. The coordinator wants them to be fully independent. Which design decision best enforces parallel isolation?
• A coordinator loses network connectivity to Worker Agent 2 mid-task. Worker Agents 1 and 3 continue running. When connectivity is restored 8 minutes later, the coordinator discovers Worker 2 completed its task during the outage and wrote results to its designated artifact store. What is the correct coordinator recovery action?
• An organization decides to retire a GitHub App-based agent that has been operating for 18 months. Compliance policy requires that all actions the agent took must remain auditable for 7 years. What steps must be taken when retiring the agent to ensure historical auditability is preserved?
• In a multi-agent system, Agent A (an orchestrator) needs to invoke Agent B (a specialized executor) via an internal API. A developer proposes that Agent B should accept requests from Agent A by checking a shared API key stored in both agents' environment. A security architect objects. Which authentication approach is more secure for agent-to-agent communication?
• A security team identifies that in the current multi-agent system, the orchestrator passes its own GitHub authentication token to sub-agents in environment variables so they can perform API operations. What security risk does this pattern introduce, and what is the correct alternative?
• A platform team is automating a software release pipeline: (1) run unit tests for 8 independent microservices, (2) build container images for each passing service, (3) generate a combined release manifest once ALL images are built, and (4) deploy the manifest to staging. Steps 1-2 are independent per service but step 3 has a hard join dependency on all 8 step-2 outputs. Which orchestration pattern BEST reflects this dependency structure?
• An orchestrator runs 5 parallel documentation-writing agents, each assigned to document a different API endpoint. All 5 agents write their output to a shared JSON file (api-docs.json) by reading the current file, adding their section, and writing the file back. During testing, the team observes that the final api-docs.json sometimes contains only 2 or 3 of the 5 sections — the rest are silently overwritten. Which root cause and fix BEST addresses this?
• An orchestrator runs 3 parallel feature-development agents, each working on a separate Git branch. Agent 1 modifies utils/validation.py, Agent 2 modifies utils/validation.py and models/user.py, and Agent 3 modifies models/user.py. When their branches are ready to be merged, the orchestrator needs to detect potential merge conflicts before attempting the merge. Which approach BEST enables proactive conflict detection in this scenario?
• A financial services company runs multi-agent pipelines that autonomously process customer data change requests. Their compliance team requires that every agent action must be auditable: each action must record who authorized it, what was done, when, to which data, and be tamper-evident. An engineer proposes writing audit logs to the application's standard logging system (e.g., a centralized log aggregator). A compliance officer argues this approach is insufficient. Which audit artifact design would BEST meet the compliance requirement?
• A multi-agent pipeline processes large-scale data transformation tasks. Agent A (Extractor) retrieves data from an upstream source and passes control to Agent B (Transformer). In production, Agent A occasionally fails mid-run, and the pipeline must be restarted with Agent B picking up from where Agent A left off. Currently, Agent B receives only the raw output of Agent A, but when Agent A fails mid-run, Agent B does not know which records were successfully extracted and which were not. Which handoff documentation design would BEST enable Agent B to resume accurately?
• An orchestrated multi-agent pipeline that typically completes in 45 minutes ran for 6 hours before being manually terminated. The team wants to perform post-hoc analysis to determine where the pipeline stalled and why. The orchestration system logged start/end timestamps for each agent invocation and each tool call. Which analysis approach would MOST efficiently identify the stall point and its likely cause?
• An orchestrator manages a pipeline where Agent B typically completes in under 10 minutes. On a production run, the orchestrator does not receive a completion signal from Agent B after 45 minutes. The orchestrator cannot determine if Agent B is still working slowly, has crashed silently, or is stuck in an infinite loop. Which detection mechanism would enable the orchestrator to reliably identify and respond to a stalled Agent B?
• An orchestrator fans out to 3 parallel agents to prepare a release: Agent 1 runs security scans, Agent 2 runs performance benchmarks, and Agent 3 generates release notes. Agent 1 and Agent 3 complete successfully. Agent 2 fails with an unrecoverable error after exhausting all retries. The release has a time-critical deadline. Which degraded coordination response BEST balances the deadline constraint with the governance requirement that releases must pass security and performance validation?
• Two agents from different teams in the same organization need to coordinate: Agent A (owned by the Platform team) generates infrastructure change plans, and Agent B (owned by the Security team) must approve those plans before they are executed. Neither team controls the other's agent. Which coordination design MOST effectively enables this cross-team agent coordination?