EXIN DevOps Master

Inicio:
17-12-2018 / 09:00
Fin:
19-12-2018 / 18:00
Horas:
16
Días:

lunes a miércoles

Newsletter:
Imagen_Newsletter:

flat/exin.png

Precio:
740€

exindevopsmasterEXIN DevOps Master es una certificación de nivel avanzado que enseña a los candidatos una combinación de principios, conocimientos y habilidades prácticas.

Esto les permite presentar y promocionar DevOps en su organización a fin de administrar mejor los ciclos de vida de las aplicaciones y los servicios, a la vez que se facilita el trabajo en equipo colaborativo.

A quién va dirigido:

DevOps está principalmente asociado con el desarrollo de software, pero sus principios se aplican cada vez más a otros proyectos y procesos.

Esto hace que la certificación DevOps Master sea interesante para los profesionales de TI que deseen ampliar sus conocimientos para cubrir los últimos avances en la gestión de TI.

Los desarrolladores de aplicaciones, los propietarios de productos, los maestros de Agile Scrum, los jefes de proyecto, los jefes de pruebas y los jefes de servicios de TI se beneficiarían de este examen.

Requisitos para la certificación:
Haber completado con exito el examen DevOps Master.
• Haber completado con exito un curso acreditado de EXIN "EXIN DevOps Master™" incluyendo las tareas practicas.

Detalles del examen:

Tipo de examen: Preguntas de opción múltiple en ordenador o en papel
Numero de preguntas: 50
Nota mínima para aprobar: 65%
Libro abierto / notas: No
Equipos electrónicos / asistentes permitidos: No
Tiempo asignado para el examen: 120 minutos

 

Contenidos:

1. DevOps Adoption
1.1 DevOps Mindset and Benefits
1.1.1 analyze DevOps anti-patterns in a scenario
1.1.2 explain the benefits of DevOps
1.1.3 explain why DevOps fits the current software development process so well
1.1.4 explain why DevOps needs a specific mindset to work
1.1.5 explain how DevOps fits with Lean and Agile Scrum practices
1.2 Organizational Culture
1.2.1 explain why the 4 Pillars of Effective DevOps (Collaboration, Affinity, Tools, and Scaling) are so important
1.2.2 analyze a scenario for missing parts of the DevOps mindset
1.2.3 explain how to create a team from a group of people, through fostering collaboration, a DevOps mindset, and empathy and trust
1.2.4 analyze a situation where there is a misconception regarding collaboration and identify the correct troubleshooting method
1.2.5 analyze a situation where there is a need for conflict management and identify the best solution
1.2.6 explain how human resource management can foster diversity and which benefits this brings to the organization
1.3 DevOps Principles and Concepts
1.3.1 explain the use and usefulness of different software development methodologies (Waterfall, Agile, Scrum, etc.) and their basic principles
1.3.2 explain the use and usefulness of different operations methodologies (IT Service Management)
1.3.3 explain the use and usefulness of the Lean systems methodology
2. Planning, Requirements, and Design
2.1 Application or Service Lifecycle Management
2.1.1 explain how DevOps adds value to modern Application Lifecycle Management
2.1.2 explain why DevOps improves customer experience when used for Service Lifecycle Management
2.2 Project Charter and Visual Control
2.2.1 explain how a DevOps project’s scope should be determined
2.2.2 explain why Visual Control over a DevOps project facilitates DevOps practices
2.3 Infrastructure and Architecture Design
2.3.1 explain how DevOps changes or influences the design of IT infrastructure and architecture
2.3.2 explain why Cloud computing and virtualization techniques make integrating Dev and Ops easier
2.4 Service Level Requirements and Agreements
2.4.1 explain how DevOps changes Service Level Requirements and Agreements
2.5 Implementing a Testing Strategy
2.5.1 explain why and how the Testing Strategy needs to be changed when transitioning to DevOps
2.5.2 analyze User Stories for completeness
3. Development and Deployment
3.1 Continuous Delivery and Continuous Integration
3.1.1 explain why Continuous Delivery is essential for Effective DevOps
3.1.2 analyze how to integrate Continuous Delivery in a scenario
3.1.3 analyze how to solve problems with Continuous Delivery in a scenario
3.1.4 explain why Continuous Integration is essential for Effective DevOps
3.1.5 analyze how to achieve Continuous Integration in a scenario with a distributed team or a distributed version control system
3.1.6 analyze how to solve problems with Continuous Integration in a scenario
3.2 Deployment Pipeline
3.2.1 explain the logic of the anatomy of a DevOps deployment pipeline
3.2.2 explain how to use build and deployment scripting
3.3 Continuous Deployment
3.3.1 explain why the iteration plan and the release plan should be changed for effective DevOps
3.3.2 analyze how to implement Continuous Deployment in a scenario
3.4 Ji-Kotei-Kanketsu, Rhythm, Work-in-Progress and One-piece-flow (4%)
3.4.1 explain the concepts Ji-Kotei-Kanketsu, Rhythm, Work-in-Progress and One-piece-flow
3.4.2 analyze a scenario for a problem with Ji-Kotei-Kanketsu, Rhythm, Work-in-Progress or One-piece-flow and find a suitable solution
3.5 Automation, Tools and Testing
3.5.1 explain why automation is important for effective DevOps
3.5.2 explain how to use tools to facilitate DevOps in general
3.5.3 explain how to use tools to support DevOps mindset and culture
3.5.4 explain why it is important that DevOps testing is automated
3.5.5 analyze a scenario and choose the correct way of automating an acceptance test
4. Operation and Scaling
4.1 Managing Data; Infrastructure and Environments; and Components and Dependencies
4.1.1 explain which problems can be encountered when managing data in databases within DevOps
4.1.2 analyze a scenario where a database is used in DevOps and provide the best solution to a problem
4.1.3 analyze a scenario and identify the best way to prepare an infrastructure environment for deployment or manage it after deployment
4.1.4 analyze a scenario and suggest a commonly used strategy to manage components
4.1.5 explain how to manage dependencies
4.2 Configuration Management and Version control
4.2.1 explain why version control is a key to effective DevOps
4.2.2 explain how to keep version control over data, infrastructure and components
4.2.3 analyze a scenario and suggest the best strategy to manage a configuration problem
4.3 Cloud and Immutable Infrastructure
4.3.1 explain when it is and when it is not necessary to move to Cloud-based infrastructure for effective DevOps
4.3.2 explain how Cloud-based infrastructure should be managed within DevOps
4.4 Business Continuity
4.4.1 explain how DevOps can facilitate Business Continuity practices
4.5 Scaling
4.5.1 analyze a scenario, explain if and why it is important to scale up or down in that situation, and identify the best way to do that
4.5.2 analyze a scenario for what went wrong with scaling, and identify a good way to solve the problem
4.5.3 explain how social policy and hiring practices support scaling DevOps
5. End-of-Life
5.1 Conditions for End-of-Life of a product or service (2%)
5.1.1 explain which conditions should be met before terminating a service or product

Utilizamos cookies propias, analizando sus hábitos de navegación en nuestra página web, con la finalidad de garantizar la calidad, seguridad y mejora de los servicios ofrecidos a través de la misma. En los casos en que el usuario no manifieste expresamente si acepta o no la instalación de las cookies, pero continúe utilizando nuestra página web, se entenderá que éste ha dado su consentimiento, informándole expresamente de la posibilidad de bloquear o eliminar las cookies instaladas en su equipo mediante la configuración de las opciones del navegador. Para saber más sobre las cookies, su uso y eliminación, ver política de cookies.

Acepto las cookies para estes sitio.

EU Cookie Directive