3. What is the use of SSH?
SSH stands for Secure Shell and is an administrative protocol that lets users have access and control the remote servers over the Internet to work using the command line.
SSH is a secured encrypted version of the previously known Telnet which was unencrypted and not secure. This ensured that the communication with the remote server occurs in an encrypted form.
SSH also has a mechanism for remote user authentication, input communication between the client and the host, and sending the output back to the client.
4. What is configuration management?
Configuration management (CM) is basically a practice of systematic handling of the changes in such a way that system does not lose its integrity over a period of time. This involves certain policies, techniques, procedures, and tools for evaluating change proposals, managing them, and tracking their progress along with maintaining appropriate documentation for the same.
CM helps in providing administrative and technical directions to the design and development of the appreciation.
5. What is the significance of DevOps configuration management?
Configuration management (CM) assists the team in automating time-consuming and repetitive operations, improving the organization's performance and agility.
It also aids in the consistency and improvement of the product development process by utilising design streamlining, detailed documenting, control, and change implementation throughout the project's many phases/releases.
6. In DevOps, what does CAMS stand for?
Culture, Automation, Measurement, and Sharing (CAMS) are acronyms for Culture, Automation, Measurement, and Sharing. It encapsulates the essence of DevOps.
7. What is Continuous Integration (CI) and how does it work?
Continuous Integration (CI) is a software development practice that makes sure developers integrate their code into a shared repository as and when they are done working on the feature. Each integration is verified by means of an automated build process that allows teams to detect problems in their code at a very early stage rather than finding them after the deployment.
8. What is the necessity for Continuous Integration?
The software quality has increased and the time taken to provide the features of the product has been considerably lowered by implementing Continuous Integration for both development and testing.
Because every commit to the shared repository is produced automatically and performed against the unit and integration test cases, the development team can find and fix mistakes early on.
9. What is Continuous Testing (CT) and how does it work?
Continuous Testing (CT) is a DevOps phase that entails running automated test cases as part of an automated software delivery pipeline with the sole purpose of receiving immediate feedback on the quality and validation of business risks associated with the automated build of code developed by developers.
This phase will assist the team in continuously testing each build (as soon as the code developed is pushed), allowing the development teams to receive immediate feedback on their work and ensuring that these issues do not arise later in the SDLC cycle.
10. What are the three most crucial DevOps KPIs?
The following are some DevOps KPIs:
Reduce the time it takes to recover from a failure on average.
Increase The frequency with which the deployment takes place.
The percentage of deployments that fail has decreased.