Which TWO of the following are BEST described as traditional escalation paths? 1. Functional 2. Hierarchical 3. Cyclical 4. Logical

Traditional IT operations models commonly rely on two primary escalation paths. The first is hierarchical, where an issue is passed up the chain of command from junior staff to senior staff and then to management. The second is functional, where an issue is passed between different specialized teams (silos) based on the required expertise, such as from a general help desk to the network team, then to the database team. These paths are often rigid and can introduce delays, which SRE models aim to reduce through shared ownership and automation. Why IncorrectOptions are Wrong:
3. Cyclical: This is not a standard term for an escalation path. An effective escalation process should lead to resolution, not a repeating cycle.
4. Logical: While an escalation path should be logical, "logical" is a quality of a path, not a type of path itself like hierarchical or functional.

B. Cyclical escalation is not a recognised ITIL/DevOps term.
C. See above; cyclical & logical are non-standard in incident escalation literature.
D. Logical escalation is not defined in service-management frameworks.

Kim, G., et al. (2016). The DevOps Handbook: How to Create World-Class Agility, Reliability, & Security in Technology Organizations. IT Revolution Press. Part II, "The First Way: The Principles of Flow," discusses the negative impact of functional silos and handoffs, which are characteristic of functional escalation.

Coury, D. & Joseph, K. (2019). What is SRE?. ACM Queue, 17(3), pp. 60-79. https://doi.org/10.1145/3338533.3339131. The article contrasts SRE with traditional operations, implicitly referencing the siloed (functional) and tiered (hierarchical) structures that SRE seeks to improve.