Accenture Delivery Lead System Integration
Practitioner:
Question Practice Exam with Detailed Rationales
Accenture Delivery Lead with this comprehensive question practice
exam on System Integration. Covering strategy, API-led connectivity,
governance, and modernization, each question includes a detailed
rationale to strengthen your architectural and delivery expertise.
INTEGRATION STRATEGY & ARCHITECTURE
1. A client has ERP, CRM, e-commerce, and a data lake with many brittle point-to-point
interfaces. Which architecture change best reduces long-term coupling?
A) Move all transformations into spreadsheets
B) Adopt reusable integration services and canonical contracts where appropriate
C) Create another point-to-point interface for each new consumer
D) Allow every application to define its own incompatible customer model
Correct Answer: B
Rationale: Reusable services and stable canonical contracts significantly reduce duplicated
mappings, centralize logic, and make change impact more manageable. Point-to-point interfaces
(A, C) increase coupling, and allowing incompatible models (D) creates data silos.
2. During discovery, business owners describe outcomes but not interface details. What
should the delivery lead do first?
A) Write production code before confirming requirements
B) Skip stakeholder interviews and infer everything from old interfaces
C) Facilitate requirements workshops and document business capabilities, data flows, and
constraints
D) Select a middleware product immediately
Correct Answer: C
Rationale: Architecture should be driven by understood business and technical requirements
rather than tool-first decisions. Writing code (A) or skipping interviews (B) is premature, and
selecting middleware (D) without requirements often leads to poor fit.
,3. An integration must connect on-premises systems to SaaS applications while the data
center remains in use. Which architecture is most appropriate?
A) A desktop-only integration
B) A single isolated local script with no monitoring
C) A public database shared by all systems
D) A hybrid integration architecture with controlled connectivity and shared governance
Correct Answer: D
Rationale: Hybrid architectures explicitly accommodate on-premises and cloud components
while preserving security and governance. The other options lack scalability, security, or proper
governance.
4. A design review finds that the proposed integration is difficult to test because business
logic, transport, mapping, and error handling are tightly mixed. What principle should guide
redesign?
A) Separate concerns into modular, testable components
B) Increase code duplication
C) Remove logging to simplify the flow
D) Combine all processing into one opaque script
Correct Answer: A
Rationale: Separation of concerns improves maintainability, testing, reuse, and troubleshooting.
Duplication (B) and opaque scripts (D) exacerbate the problem, and removing logging (C)
destroys visibility.
5. A team is choosing between two integration platforms. What should be the strongest
architectural selection criterion?
A) Which tool was used by a developer on a previous project
B) Fit with required capabilities, security, operating model, skills, and total cost
C) Which platform has the most colorful user interface
D) Which vendor has the longest product name
Correct Answer: B
Rationale: Technology selection should reflect business and technical fit, not superficial
preference. Personal preference (A) or UI aesthetics (C) do not justify architectural decisions.
6. A new customer service requires the same customer identity to be shared by six
applications. What should the architect establish early?
A) Manual re-entry by each department
B) A shared password for all applications
C) A governed customer data model and ownership of the authoritative source
D) Six independent customer identifiers with no reconciliation
,Correct Answer: C
Rationale: Clear data ownership and semantics prevent conflicting customer identities and
ambiguous integration behavior. Manual entry (A) and independent identifiers (D) cause data
integrity issues.
7. A legacy interface is scheduled for replacement. What is the best first step for migration
planning?
A) Delete the legacy interface immediately
B) Migrate without identifying consumers
C) Change the data format first and ask users later
D) Inventory dependencies, consumers, data contracts, volumes, and operational behavior
Correct Answer: D
Rationale: Dependency and behavior discovery reduces migration surprises and supports
controlled cutover. Immediate deletion (A) or changing formats (C) without understanding
dependencies causes outages.
8. An integration architecture board asks how a proposed interface will scale. Which evidence
is most useful?
A) Expected transaction rates, payload sizes, concurrency, latency targets, and scaling strategy
B) The number of slides in the design deck
C) Developer preference for a programming language
D) The age of the project manager
Correct Answer: A
Rationale: Capacity and nonfunctional requirements provide measurable evidence for
scalability decisions. Subjective measures like slide count (B) or PM age (D) are irrelevant.
9. A team proposes a shared integration component used by many interfaces. What should be
reviewed before approval?
A) Whether only one developer understands it
B) Its contract stability, ownership, versioning, failure behavior, and reuse value
C) Whether it has the shortest class name
D) Whether it avoids all documentation
Correct Answer: B
Rationale: Shared components become dependencies, so governance around contracts and
failure behavior is essential. Obscurity (A) and lack of documentation (D) increase risk.
10. A business sponsor asks for delivery in half the original time. What should the delivery
lead do?
A) Remove all testing
B) Hide the schedule risk from the sponsor
, C) Reprioritize scope and sequence based on business value and delivery risk
D) Promise the original scope without analysis
Correct Answer: C
Rationale: Transparent scope and risk management protects quality while aligning delivery with
the new constraint. Removing testing (A) or hiding risks (B) guarantees failure.
11. A program spans several teams that each own different interfaces. What governance
mechanism best reduces inconsistent designs?
A) Independent standards for every team
B) No review until production incidents occur
C) A single developer approving every line of code
D) Shared integration standards, reference patterns, and architecture reviews
Correct Answer: D
Rationale: Common standards and lightweight governance create consistency without requiring
one team to implement everything. Independent standards (A) cause fragmentation.
12. A new interface needs a contract that multiple consumers can rely on. Which practice is
strongest?
A) Define and review the interface contract before implementation
B) Let each consumer reverse-engineer behavior
C) Change fields silently after release
D) Document behavior only after production
Correct Answer: A
Rationale: Contract-first thinking makes expectations explicit and supports independent
development and testing. Reverse-engineering (B) and silent changes (C) break consumers.
13. A client wants to modernize a large estate but cannot migrate everything at once. Which
strategy is most pragmatic?
A) Rewrite every system before integrating any
B) Use incremental strangler-style modernization with coexistence and controlled cutovers
C) Perform a single uncontrolled replacement
D) Freeze all changes for several years
Correct Answer: B
Rationale: Incremental modernization reduces risk and allows value to be delivered while legacy
capabilities remain available. Big bang rewrites (A, C) are highly risky.
14. A delivery lead needs to explain architecture to executives. What should be emphasized?
A) Only vendor-specific jargon
B) Unverified technical details
C) Business outcomes, major risks, dependencies, investment choices, and measurable benefits
Practitioner:
Question Practice Exam with Detailed Rationales
Accenture Delivery Lead with this comprehensive question practice
exam on System Integration. Covering strategy, API-led connectivity,
governance, and modernization, each question includes a detailed
rationale to strengthen your architectural and delivery expertise.
INTEGRATION STRATEGY & ARCHITECTURE
1. A client has ERP, CRM, e-commerce, and a data lake with many brittle point-to-point
interfaces. Which architecture change best reduces long-term coupling?
A) Move all transformations into spreadsheets
B) Adopt reusable integration services and canonical contracts where appropriate
C) Create another point-to-point interface for each new consumer
D) Allow every application to define its own incompatible customer model
Correct Answer: B
Rationale: Reusable services and stable canonical contracts significantly reduce duplicated
mappings, centralize logic, and make change impact more manageable. Point-to-point interfaces
(A, C) increase coupling, and allowing incompatible models (D) creates data silos.
2. During discovery, business owners describe outcomes but not interface details. What
should the delivery lead do first?
A) Write production code before confirming requirements
B) Skip stakeholder interviews and infer everything from old interfaces
C) Facilitate requirements workshops and document business capabilities, data flows, and
constraints
D) Select a middleware product immediately
Correct Answer: C
Rationale: Architecture should be driven by understood business and technical requirements
rather than tool-first decisions. Writing code (A) or skipping interviews (B) is premature, and
selecting middleware (D) without requirements often leads to poor fit.
,3. An integration must connect on-premises systems to SaaS applications while the data
center remains in use. Which architecture is most appropriate?
A) A desktop-only integration
B) A single isolated local script with no monitoring
C) A public database shared by all systems
D) A hybrid integration architecture with controlled connectivity and shared governance
Correct Answer: D
Rationale: Hybrid architectures explicitly accommodate on-premises and cloud components
while preserving security and governance. The other options lack scalability, security, or proper
governance.
4. A design review finds that the proposed integration is difficult to test because business
logic, transport, mapping, and error handling are tightly mixed. What principle should guide
redesign?
A) Separate concerns into modular, testable components
B) Increase code duplication
C) Remove logging to simplify the flow
D) Combine all processing into one opaque script
Correct Answer: A
Rationale: Separation of concerns improves maintainability, testing, reuse, and troubleshooting.
Duplication (B) and opaque scripts (D) exacerbate the problem, and removing logging (C)
destroys visibility.
5. A team is choosing between two integration platforms. What should be the strongest
architectural selection criterion?
A) Which tool was used by a developer on a previous project
B) Fit with required capabilities, security, operating model, skills, and total cost
C) Which platform has the most colorful user interface
D) Which vendor has the longest product name
Correct Answer: B
Rationale: Technology selection should reflect business and technical fit, not superficial
preference. Personal preference (A) or UI aesthetics (C) do not justify architectural decisions.
6. A new customer service requires the same customer identity to be shared by six
applications. What should the architect establish early?
A) Manual re-entry by each department
B) A shared password for all applications
C) A governed customer data model and ownership of the authoritative source
D) Six independent customer identifiers with no reconciliation
,Correct Answer: C
Rationale: Clear data ownership and semantics prevent conflicting customer identities and
ambiguous integration behavior. Manual entry (A) and independent identifiers (D) cause data
integrity issues.
7. A legacy interface is scheduled for replacement. What is the best first step for migration
planning?
A) Delete the legacy interface immediately
B) Migrate without identifying consumers
C) Change the data format first and ask users later
D) Inventory dependencies, consumers, data contracts, volumes, and operational behavior
Correct Answer: D
Rationale: Dependency and behavior discovery reduces migration surprises and supports
controlled cutover. Immediate deletion (A) or changing formats (C) without understanding
dependencies causes outages.
8. An integration architecture board asks how a proposed interface will scale. Which evidence
is most useful?
A) Expected transaction rates, payload sizes, concurrency, latency targets, and scaling strategy
B) The number of slides in the design deck
C) Developer preference for a programming language
D) The age of the project manager
Correct Answer: A
Rationale: Capacity and nonfunctional requirements provide measurable evidence for
scalability decisions. Subjective measures like slide count (B) or PM age (D) are irrelevant.
9. A team proposes a shared integration component used by many interfaces. What should be
reviewed before approval?
A) Whether only one developer understands it
B) Its contract stability, ownership, versioning, failure behavior, and reuse value
C) Whether it has the shortest class name
D) Whether it avoids all documentation
Correct Answer: B
Rationale: Shared components become dependencies, so governance around contracts and
failure behavior is essential. Obscurity (A) and lack of documentation (D) increase risk.
10. A business sponsor asks for delivery in half the original time. What should the delivery
lead do?
A) Remove all testing
B) Hide the schedule risk from the sponsor
, C) Reprioritize scope and sequence based on business value and delivery risk
D) Promise the original scope without analysis
Correct Answer: C
Rationale: Transparent scope and risk management protects quality while aligning delivery with
the new constraint. Removing testing (A) or hiding risks (B) guarantees failure.
11. A program spans several teams that each own different interfaces. What governance
mechanism best reduces inconsistent designs?
A) Independent standards for every team
B) No review until production incidents occur
C) A single developer approving every line of code
D) Shared integration standards, reference patterns, and architecture reviews
Correct Answer: D
Rationale: Common standards and lightweight governance create consistency without requiring
one team to implement everything. Independent standards (A) cause fragmentation.
12. A new interface needs a contract that multiple consumers can rely on. Which practice is
strongest?
A) Define and review the interface contract before implementation
B) Let each consumer reverse-engineer behavior
C) Change fields silently after release
D) Document behavior only after production
Correct Answer: A
Rationale: Contract-first thinking makes expectations explicit and supports independent
development and testing. Reverse-engineering (B) and silent changes (C) break consumers.
13. A client wants to modernize a large estate but cannot migrate everything at once. Which
strategy is most pragmatic?
A) Rewrite every system before integrating any
B) Use incremental strangler-style modernization with coexistence and controlled cutovers
C) Perform a single uncontrolled replacement
D) Freeze all changes for several years
Correct Answer: B
Rationale: Incremental modernization reduces risk and allows value to be delivered while legacy
capabilities remain available. Big bang rewrites (A, C) are highly risky.
14. A delivery lead needs to explain architecture to executives. What should be emphasized?
A) Only vendor-specific jargon
B) Unverified technical details
C) Business outcomes, major risks, dependencies, investment choices, and measurable benefits
