IBM Cloud Professional Certification Program Study Guide Series Exam C5050-300 - Foundations of IBM DevOps V1 PURPOSE OF EXAM OBJECTIVES ................................................. - 3 - HIGH-LEVEL EXAM OBJECTIVES .................................................. - 4 - DETAILED EXAM OBJECTIVES ...................................................... - 6 - Section 1 - DevOps Principles ................................................................................ - 6 - Section 2 - Adopting DevOps ............................................................................... - 34 - Section 3 - IBM DevOps Reference Architecture & Methods ............................... - 50 - Section 4 - Open Source, Open Standard & Other Open Components ............... - 64 - Section 5 - IBM Solutions for DevOps .................................................................. - 70 - NEXT STEPS .................................................................................. - 78 - Purpose of Exam Objectives When an exam is being developed, the Subject Matter Experts work together to define the role the certified individual will fill. They define all of the tasks and knowledge that an individual would need to have in order to successfully implement the product. This creates the foundation for the objectives and measurement criteria, which are the basis for the certification exam. The Cloud certification item writers use these objectives to develop the questions that they write and which will appear on the exam. It is recommended that you review these objectives. Do you know how to complete the task in the objective? Do you know why that task needs to be done? Do you know what will happen if you do it incorrectly? If you are not familiar with a task, then go through the objective and perform that task in your own environment. Read more information on the task. If there is an objective on a task there is about a 95% chance that you WILL see a question about it on the actual exam. After you have reviewed the objectives and completed your own research, then take the assessment exam. While the assessment exam will not tell you which question you answered incorrectly, it will tell you how you did by section. This will give you a good indication as to whether you are ready to take the actual exam or if you need to further review the materials. Note: This is the high-level list of objectives. As you review these objectives, click for a more detailed level of how to perform the task. High-level Exam Objectives Section 1 - DevOps Principles 1.1 Summarize different development approaches 1.2 Explain and identify delivery pipelines 1.3 Explain lean principles 1.4 Explain DevOps practices 1.5 Describe Collaborative Development 1.6 Describe Continuous Integration 1.7 Advantages to Continuous integration 1.8 Describe Continuous Delivery 1.9 Describe Continuous Deployment 1.10 Describe Continuous Availability / Service Management / Monitoring 1.11 Describe Continuous Security / Security for DevOps 1.12 Explain Shift-Left Test /Continuous Test 1.13 Explain Shift Left Ops 1.14 Explain Multi-speed IT 1.15 Explain Continuous Feedback Explain the implications of the “12 Factor app” design principles for 1.16 DevOps 1.17 ITIL and DevOps Section 2 - Adopting DevOps 2.1 Describe business and IT drivers of DevOps 2.2 Explain the barriers to adoption of DevOps 2.3 Explain how to build a roadmap for DevOps adoption 2.4 Explain how to adopt DevOps in Multi-speed IT environment 2.5 Explain other continuous improvement approaches Illustrate the cultural & organizational differences when transforming 2.6 from traditional to DevOps processes 2.7 Planning & Organization 2.8 Performance & Culture 2.9 Measure 2.10 Explain the benefits of Design Thinking for DevOps process adoption Section 3 - IBM DevOps Reference Architecture & Methods 3.1 Describe IBM DevOps Reference Architecture pattern 3.2 Explain the IBM point of view on DevOps 3.3 Explain DevOps for Microservices 3.4 Explain DevOps for Cloud Native 3.5 Explain DevOps for Cloud Ready 3.6 Explain Cloud Service Management Operations 3.7 Describe the IBM Bluemix Garage Method 3.8 Define and identify the common components of a DevOps Tool chain 3.9 Describe the key architectural decisions made to adopt DevOps Section 4 - Open Source, Open Standard & Other Open Components 4.1 Identify tools for Build & Deploy 4.2 Identify tools for Collaboration & Notification 4.3 Identify other common tools and their uses 4.4 Describe common container technology 4.5 Explain the applicability of open standards for DevOps Section 5 - IBM Solutions for DevOps 5.1 Describe the IBM solutions for the THINK phase in DevOps 5.2 Describe the IBM solutions for the CODE phase in DevOps 5.3 Describe the IBM solutions for the DELIVER phase in DevOps 5.4 Describe the IBM solutions for the RUN phase in DevOps 5.5 Describe the IBM solutions for the MANAGE phase in DevOps 5.6 Describe the IBM solutions for the LEARN phase in DevOps 5.7 Describe the IBM solutions for the CULTURE phase in DevOps 5.8 Describe the IBM solutions for Security in DevOps Describe the IBM solutions for transformation and connectivity in 5.9 DevOps Detailed Exam Objectives Section 1 - DevOps Principles DevOps Principles This section focusses upon the core principles, definitions and practices of DevOps that recognised across the industry, and are vendor and solution agnostic. Essentially, this is about the WHAT is DevOps? It will cover the end to end process of DevOps, the common methods and terminology that a DevOps practitioner will regularly encounter during a DevOps solution implementation. Define DevOps DevOps is an approach that promotes closer collaboration between lines of business, development and IT operations. It is an enterprise capability that enables the continuous delivery, continuous deployment and continuous monitoring of applications. It reduces the time needed to address customer feedback. Development, testing, operations and lines of business were often siloed in the past. DevOps brings them together to improve agility. DevOps started as a culture and set of practices to support collaboration and communication across development and operations, and to apply automation to key phases of the software delivery process. It has been popularized by successful new companies developing business models and related applications empowered by the cloud (cloud-native applications). More recently, large, established enterprises have recognized the need to deliver innovation faster to stay relevant and capitalize on industry disruption, while also improving operational metrics for application quality and cost. DevOps and cloud have emerged as essential parts of their IT strategy as they improve core competency in continuous delivery of software-driven innovation. https://www.ibm.com/cloud-computing/learn-more/what-is-devops/ https://www- 01.ibm.com/common/ssi/cgi- bin/ssialias?subtype=WH&infotype=SA&htmlfid=RAW14389USEN&attachment=RA W14389USEN.PDF https://en.wikipedia.org/wiki/DevOps 1.1. Summarize different development approaches 1.1.1. Define the different development approaches In any enterprise you will see a number of development approaches, and often more than one including ,but not limited to: 1.1.1.1. Traditional waterfall 1.1.1.2. V-Model 1.1.1.3. Incremental 1.1.1.4. Agile 1.1.1.5. SAFe® 1.1.1.6. Disciplined Agile Delivery 1.1.2. Briefly describe traditional waterfall In a waterfall process all the requirements need to be defined in detail and signed off before design can start. Then the design has to be agreed before development can start. Next low level design, code and unit test complete (sometimes known as DCUT) needs to be shown before independent testing can start, and finally release into production only happens when testing is complete. In practice very often these phases overlap, but the feedback loop between the phases is minimal. 1.1.3. Briefly describe the V-Model V- model means Verification and Validation model. Just like the waterfall model, the V-Shaped life cycle is a sequential path of execution of processes. Each phase must be completed before the next phase begins. Testing of the product is planned in parallel with a corresponding phase of development in V-model. 1.1.4. Briefly describe incremental method In incremental model requirements are identified up front and then divided into various builds or iterations. Each iteration passes through the requirements, design, implementation and testing phases in a mini-waterfall way. A working version of software is produced during the first iteration, so you have working software early on during the software life cycle. Each subsequent release of the module adds function to the previous release. The process continues till the complete system is achieved. 1.1.5. Briefly describe agile development Agile development is typically defined by the 12 principles outlined in the Agile Manifesto below 1.1.5.1. The highest priority is to satisfy the customer through early and continuous delivery of valuable software. 1.1.5.2. Welcome changing requirements, even late in development. Agile processes harness change for the customer’s competitive advantage. 1.1.5.3. Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale. 1.1.5.4. Business people and developers must work together daily throughout the project. 1.1.5.5. Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job