Final Exam: SRE DevOps Engineer

DevOps    |    Intermediate
  • 1 Video | 32s
  • Includes Assessment
  • Earns a Badge
Likes 1 Likes 1
Final Exam: DevOps Engineer will test your knowledge and application of the topics presented throughout the DevOps Engineer track of the Skillsoft Aspire Network Admin to Site Reliability Engineer Journey.


  • define the concept of software complexity
    demonstrate how to use Kubernetes to deploy applications with high availability, scalability, and resilience
    describe continuous integration with Docker
    describe how automation can reduce the meantime to repair for common faults
    describe how automation consistency can add value
    describe the importance of continuous testing as it relates to the Rapid release model
    describe the release management cycle and each step in the cycle
    differentiate between complex and complicated code
    differentiate between containers and virtual machines and list container benefits such as consistent environment, isolation, run anywhere
    differentiate between continuous delivery, continuous deployment, and continuous integration
    differentiate between essential complexity vs. accidental complexity and recognize how simple, "boring" software is ideal
    differentiate between Git and Github and recognize how they can be used for revision control and to support the collaborative development
    differentiate between release engineering and release management
    differentiate between scripts and programs as they relate to automation
    differentiate between simple and complex releases
    distinguish between complex and complicated code
    identify how APIs can lead to a path of simplicity
    identify when to implement a public cloud model and list key advantages for SREs
    list common challenges surrounding release management
    list considerations when implementing container security
    list potential challenges of automation such as integration, ROI, complexity, and security
    list the advantages of using a hybrid cloud model and list key advantages for SREs
    list the four major principles of release engineering - self-service model, high velocity, hermetic builds, and enforcement of policies and procedures
    list the goals of writing a post-mortem such as documenting the incident, root causes, and preventative actions
    list Windows features that can automate aspects of software rollouts such as Windows Deployment Services and Volume Activation Management Tool
    outline software development agility and how it relates to SREs
    outline software development stability and how it relates to SREs
    outline the importance of simple code, e.g., having fewer bugs
    provide an overview of a premortem approach including its benefits
    provide an overview of blameless post-mortems
  • provide an overview of branching as it relates to the Rapid release model
    provide an overview of containers
    provide an overview of Docker
    provide an overview of how automation has evolved at a company such as Google
    provide an overview of infrastructure as a service (IaaS) and list key advantages for SREs
    provide an overview of Kubernetes
    provide an overview of release engineering
    provide an overview of release management and recognize its key terms
    provide an overview of setting up a bulk enrollment of devices to be managed by the mobile device management
    provide an overview of software as a solution (SaaS) and list key advantages for SREs
    provide an overview of the community cloud model and list key advantages for SREs
    provide an overview of the platform as a service (PaaS) and list key advantages for SREs
    provide an overview of the private cloud model
    provide an overview of the release management process
    provide examples of a poor bad post-mortem including potential areas to improve such as missing context, omitted details, missing action items, finger-pointing, animated language
    recognize how containers enable a more efficient continuous delivery system and why they are needed for SRE
    recognize how simple systems and software are easy to understand, maintain, and test
    recognize how to automate Active Directory user creation and user provisioning
    recognize how to automate tasks such as patching and Windows updating
    recognize how to do a premortem on a project as well as best practices to follow
    recognize how to use Jenkins Pipeline to implement and integrate continuous delivery pipelines
    recognize how to use PowerShell for automation tasks in Windows
    recognize key steps and factors of a code review
    recognize the benefits of implementing a content as a service (CaaS) solution
    recognize the importance of reviewing post-mortems
    recognize the importance of sharing post-mortems as widely as possible
    recognize the value of collaboration and knowledge sharing throughout the post-mortem workflow
    recognize ways to determine software usage difficulty, e.g., is it functional and usable?
    recognize when to implement a public cloud model and list key advantages for SREs
    understand differences between Git/Github and DVCS for version control


  • Playable
    DevOps Engineer


Skillsoft is providing you the opportunity to earn a digital badge upon successful completion of this course, which can be shared on any social network or business platform

Digital badges are yours to keep, forever.