Section 26.249 When to Automate and Orchestrate

Question 1

Automation and Orchestration

Answer 1

Effective automation and orchestration are for repeatable and stable tasks and workflows

■ Identify consistent processes in your organisation for automation and orchestration

Question 2

Decision factors for implementing automation and orchestration

Complexity

Answer 2

Automation and orchestration are suitable for complex, repetitive tasks

● Determine process complexity to decide whether to automate or
orchestrate

● Routine backups are suitable for automation, while complex incident response requires orchestration

Question 3

Cost

Answer 3

Initial investment is a key factor

● Conduct a cost-benefit analysis considering development,
implementation, and maintenance costs

● Include hardware, software, personnel, and support costs in the analysis

● Cost savings often outweigh the initial investment in the long run

Question 4

Single Points of Failure

Answer 4

Implement backup systems or manual processes to mitigate single points of failure

● Redundancy and failover mechanisms, both technical and manual, can ensure uninterrupted operations

Question 5

Technical Debt

Answer 5

Technical debt is the cost and complexity of suboptimal software
solutions

● Regular reviews and updates are necessary to avoid technical debt

● Technical debt can impede efficiency and security

Question 6

Ongoing supportability

Answer 6

Automation and orchestration systems need ongoing maintenance and adaptation

● Teams must possess the necessary skills to maintain and adapt these systems

● Training and skill development are essential

● Most automation depends on the connection of systems via APIs and webhooks