When DevOps practices are integrated into an existing organization, which two characteristics are positive indicators of DevOps maturity? (Choose two.)

Mean time between success is not a standard DevOps metric; common metrics include Mean Time Between Failures (MTBF) for reliability, but 'success' is ambiguous here.

Mean time to recover (MTTR) measures how quickly an organization can restore service after an outage or incident, reflecting the resilience and efficiency of operations, which is a key aspect of DevOps maturity. A shorter MTTR indicates a more mature and responsive system.

Cone testing is not a standard or recognized DevOps metric for maturity; it might be a specific testing methodology but not a general indicator of maturity.

Change lead time, also known as lead time for changes, measures the time it takes for a commit to be deployed to production, indicating the speed and efficiency of the development and delivery pipeline. Shorter lead times are a hallmark of mature DevOps practices.

The age of a codebase does not directly indicate DevOps maturity; an old codebase can still be managed with mature DevOps practices, and a new one can be managed poorly.