Sure, here are the top 30 DevSecOps interview questions with answers:

1. What is DevSecOps?

DevSecOps is a combination of development (Dev), security (Sec), and operations (Ops) that works to secure the entire software development lifecycle.

2. What are the benefits of DevSecOps?

The benefits of DevSecOps include:

Increased security: DevSecOps helps to secure the software development lifecycle from the start, which can help to prevent security vulnerabilities.
Improved efficiency: DevSecOps can help to improve the efficiency of the software development lifecycle by automating security checks and by integrating security into the development process.
Reduced costs: DevSecOps can help to reduce the costs of security by preventing security vulnerabilities and by automating security checks.

3. What are the challenges of DevSecOps?

The challenges of DevSecOps include:

Culture change: DevSecOps requires a cultural shift in the way that security is viewed in the organization.
Technical skills: DevSecOps requires a deep understanding of development, security, and operations.
Tools: There are a number of DevSecOps tools available, but it can be difficult to choose the right ones for your organization.
Compliance: DevSecOps teams need to ensure that they are compliant with all applicable security regulations.

4. What are the different stages of the DevSecOps lifecycle?

The DevSecOps lifecycle can be divided into the following stages:

Planning: The planning stage involves defining the security requirements for the software development lifecycle.
Design: The design stage involves incorporating security into the software design.
Development: The development stage involves developing the software with security in mind.
Testing: The testing stage involves testing the software for security vulnerabilities.
Deployment: The deployment stage involves deploying the software to production.
Monitoring: The monitoring stage involves monitoring the software for security vulnerabilities.

5. What are the different roles in DevSecOps?

The different roles in DevSecOps include:

DevSecOps engineer: DevSecOps engineers are responsible for integrating security into the software development lifecycle.
Security engineer: Security engineers are responsible for developing and maintaining security policies and procedures.
Developer: Developers are responsible for developing software with security in mind.
Operations engineer: Operations engineers are responsible for deploying and monitoring software in production.
Product manager: Product managers are responsible for defining the requirements for software products.

6. What are the skills required for a DevSecOps engineer?

The skills required for a DevSecOps engineer include:

Development skills: DevSecOps engineers need to have some skills in development.
Security skills: DevSecOps engineers need to have strong skills in security.
Operations skills: DevSecOps engineers need to have some skills in operations.
Communication skills: DevSecOps engineers need to be able to communicate effectively with stakeholders.
Problem-solving skills: DevSecOps engineers need to be able to identify and solve problems quickly and efficiently.

7. What are the career opportunities for DevSecOps engineers?

The career opportunities for DevSecOps engineers are growing rapidly as more and more organizations adopt DevSecOps solutions. DevSecOps engineers can find jobs in a variety of industries, including:

Technology: DevSecOps engineers can work for technology companies of all sizes, from small businesses to large enterprises.
Finance: DevSecOps engineers can work for financial institutions that are using DevSecOps to secure their systems.
Healthcare: DevSecOps engineers can work for healthcare organizations that are using DevSecOps to protect patient data.
Retail: DevSecOps engineers can work for retailers that are using DevSecOps to secure their e-commerce platforms.
Manufacturing: DevSecOps engineers can work for manufacturers that are using DevSecOps to secure their industrial control systems.

8. How does DevSecOps handle vulnerability assessment and management?

DevSecOps integrates automated vulnerability scanning into the CI/CD pipeline to identify vulnerabilities in the code and libraries.

9. What role does static application security testing (SAST) play in DevSecOps?

SAST analyzes the application’s source code to identify vulnerabilities early in the development process.

10. How can dynamic application security testing (DAST) improve security in DevSecOps?

DAST involves testing running applications for security vulnerabilities and potential exploits, providing real-world insights into application security.

11. Describe the purpose of “container security” in DevSecOps.

Container security focuses on securing applications and their dependencies within containers, ensuring that they are isolated and well-protected.

12. How does DevSecOps handle secrets and credentials management?

DevSecOps employs secure vaults and secrets management tools to protect sensitive data like passwords and API keys.

13. What is “shift-right” security testing in DevSecOps?

Shift-right involves ongoing security testing in production to identify and address vulnerabilities and threats that might emerge after deployment.

14. How does DevSecOps handle compliance and regulatory requirements?

DevSecOps automates compliance checks and ensures that applications adhere to relevant regulations throughout the development lifecycle.

15. Explain the concept of “continuous monitoring” in DevSecOps.

Continuous monitoring involves actively tracking applications and infrastructure for security threats and anomalies to ensure ongoing protection.

16. What are some common security challenges faced in a DevSecOps environment?

Challenges may include finding the right balance between speed and security, integrating security into existing processes, and educating teams about security best practices.

17. How does DevSecOps support the “least privilege” principle?

DevSecOps enforces the principle of least privilege by granting only the necessary permissions to applications, reducing the attack surface.

18. Describe the role of “security champions” in DevSecOps.

Security champions are individuals within development teams who advocate for security practices, help with security-related tasks, and raise awareness.

19. What is “continuous security testing” in DevSecOps?

Continuous security testing involves automatically testing applications for vulnerabilities as part of the CI/CD pipeline, ensuring ongoing security assessment.

20. How can DevSecOps help with incident response and recovery?

DevSecOps integrates incident response processes into the development workflow, facilitating quicker identification and mitigation of security incidents.

21. What is Vagrant?

A vagrant is a tool which can create and manage virtualized environments for testing and developing software.

22. What is the use of PTR in DNS?

Pointer record which is also known as (PTR) is used for reverse DNS lookup.

23. What is Chef?

It is a powerful automation platform which transforms infrastructure into code. In this tool, you can use write scripts that are used to automate processes.

24. What are the prerequisites for the implementation of DevOps?

Following are the useful prerequisites for DevOps Implementation:

At least one Version Control Software

Proper communication between the team members
Automated testing
Automated deployment

25. Name some best practices which should be followed for DevOps success.

Here, are essential best practices for DevOps implementation:

The speed of delivery means time taken for any task to get them into the production environment.
Track how many defects are found in the various
It’s important to measure the actual or the average time that it takes to recover in case of a failure in the production environment.
The number of bugs being reported by the customer also impact the quality of the application.

26. Explain SubGIt tool

SubGit helps you to migrate SVN to Git. It also allows you to build a writable Git mirror of a local or remote Subversion repository.

27. Name some important network monitoring tools

Some most prominent network monitoring tools are:

Splunk
Icinga 2
Wireshark
Nagios
OpenNMS

28. Whether your video card can run Unity how would you know?

When you use a command

/usr/lib/Linux/unity_support_test-p
it will give detailed output about Unity’s requirements, and if they are met, then your video card can run unity.

29. Explain how to enable startup sound in Ubuntu?

To enable startup sound

Click control gear and then click on Startup Applications
In the Startup Application Preferences window, click Add to add an entry
Then fill the information in comment boxes like Name, Command, and Comment
/usr/bin/canberra-gtk-play—id= “desktop-login”—description= “play login sound”
Logout and then login once you are done
You can also open it with shortcut key Ctrl+Alt+T.

30. What is the quickest way to open an Ubuntu terminal in a particular directory?

To open an Ubuntu terminal in a particular directory, you can use custom keyboard short cut.

To do that, in the command field of a new custom keyboard, type genome – terminal – – working – directory = /path/to/dir.

Here are the top 30 AIOps interview questions with answers:

1. What is AIOps?

AIOps stands for Artificial Intelligence for IT Operations. It is a set of technologies and practices that use machine learning and artificial intelligence to automate IT operations tasks, such as monitoring, alerting, and troubleshooting.

2. What are the benefits of AIOps?

The benefits of AIOps include:

Increased efficiency: AIOps can automate many of the manual tasks involved in IT operations, freeing up IT staff to focus on more strategic work.
Improved reliability: AIOps can identify and resolve problems more quickly, before they impact users.
Reduced costs: AIOps can help to reduce the cost of IT operations by automating tasks and by preventing problems from occurring.

3. What are the challenges of AIOps?

The challenges of AIOps include:

Data: AIOps requires a lot of data to train and operate effectively. This data can be difficult and expensive to collect and prepare.
Complexity: AIOps is a complex technology that requires a deep understanding of machine learning and artificial intelligence.
Adoption: AIOps is still a relatively new technology, and there is a lack of understanding and adoption among IT teams.

4. What are the different types of AIOps solutions?

There are two main types of AIOps solutions:

Domain-centric AIOps: These solutions are focused on a specific domain, such as networking, storage, or security.
Domain-agnostic AIOps: These solutions are designed to work across multiple domains.

5. What are the most popular AIOps tools?

The most popular AIOps tools include:

New Relic AIOps: New Relic AIOps is a domain-agnostic AIOps solution that uses machine learning to automate IT operations tasks.
AppDynamics AIOps: AppDynamics AIOps is a domain-centric AIOps solution that focuses on application performance.
IBM Cloud Pak for Watson AIOps: IBM Cloud Pak for Watson AIOps is a domain-agnostic AIOps solution that uses Watson AI to automate IT operations tasks.
Splunk Cloud AIOps: Splunk Cloud AIOps is a domain-agnostic AIOps solution that uses Splunk data to automate IT operations tasks.
Datadog AIOps: Datadog AIOps is a domain-agnostic AIOps solution that uses Datadog data to automate IT operations tasks.

6. What are the different stages of AIOps maturity?

There are four main stages of AIOps maturity:

Reactive: In the reactive stage, IT teams are manually monitoring their systems and responding to incidents as they occur.
Proactive: In the proactive stage, IT teams are using machine learning to identify potential problems before they occur.
Predictive: In the predictive stage, IT teams are using machine learning to predict future problems and take preventive action.
Self-healing: In the self-healing stage, IT systems are able to automatically detect and resolve problems without any human intervention.

7. What are the different use cases for AIOps?

AIOps can be used for a variety of use cases, including:

Monitoring: AIOps can be used to monitor IT systems and identify potential problems.
Alerting: AIOps can be used to automatically generate alerts when problems are detected.
Troubleshooting: AIOps can be used to help IT teams troubleshoot problems.
Root cause analysis: AIOps can be used to identify the root cause of problems.
Predictive maintenance: AIOps can be used to predict when problems are likely to occur and take preventive action.
Self-healing: AIOps can be used to automate the process of detecting and resolving problems.

8. What are the skills required for an AIOps engineer?

The skills required for an AIOps engineer include:

IT operations experience: AIOps engineers need to have a deep understanding of IT operations principles and practices.
Machine learning skills: AIOps engineers need to have strong skills in machine learning and artificial intelligence.
Data analysis skills: AIOps engineers need to be able to analyze large amounts of data to identify problems and trends.
Communication skills: AIOps engineers need to be able to communicate effectively with IT teams and stakeholders.
Problem-solving skills: AIOps engineers need to be able to identify and solve problems quickly and efficiently.

9. What are the career opportunities for AIOps engineers?

The career opportunities for AIOps engineers are growing rapidly as more and more organizations adopt AIOps solutions. AIOps engineers can find jobs in a variety of industries, including:

IT: AIOps engineers can work for IT organizations of all sizes, from small businesses to large enterprises.

10. How can AIOps improve capacity planning?

AIOps analyzes historical and real-time data to predict resource needs, enabling efficient capacity planning and resource allocation.

11. Explain the concept of “proactive monitoring” in AIOps.

Proactive monitoring involves using AI and ML to predict potential issues before they impact the system, allowing IT teams to take preventive measures.

12. What is “self-healing” in the context of AIOps?

Self-healing refers to AIOps systems automatically detecting and addressing issues without human intervention, leading to quicker problem resolution.

13. How does AIOps contribute to business agility?

AIOps provides real-time insights into IT operations, enabling businesses to respond quickly to changing demands and ensure optimal performance.

14. What is the importance of real-time analytics in AIOps?

Real-time analytics enable IT teams to quickly identify and address issues as they occur, minimizing downtime and maintaining service availability.

15. How does AIOps handle data from various sources and formats?

AIOps platforms collect and normalize data from diverse sources, making it easier to analyze and correlate information across the IT environment.

16. What is the role of “algorithmic noise reduction” in AIOps?

Algorithmic noise reduction involves filtering out irrelevant data to improve the accuracy of AI-driven insights and predictions.

17. Explain the concept of “digital experience monitoring” in AIOps.

Digital experience monitoring involves tracking user interactions and feedback to assess the quality of services provided by IT systems.

18. How does AIOps support “automated incident response”?

AIOps can trigger predefined responses to common incidents based on historical patterns, reducing manual intervention and minimizing downtime.

19. Describe the “unsupervised learning” approach in AIOps.

Unsupervised learning involves training AI models without labeled data, allowing them to discover patterns and anomalies independently.

20. What are the challenges of implementing AIOps in an organization?

Challenges may include data integration, model accuracy, change management, and ensuring alignment with business goals.

21. Explain the Hidden Markov Model.

The Hidden Markov model is a probabilistic model which is used to identify the probabilistic character of any event. It says that an observed event is related to a set of probability distributions. If a system is being modeled into a Markov’s chain, then the main goal of HMM is to identify the hidden layers of the Markov’s chain. Hidden means that the particular state is not observable to the observer. It is generally used for temporal data. HMM finds its application in reinforcement learning, temporal pattern recognition, etc.

22. What do you understand by hyperparameters?

Hyperparameters are the parameters that control the entire training process. These variables are adjustable and have a direct impact on how successfully a model trains. They are declared beforehand. Model hyperparameters, which cannot be inferred while fitting the machine to the training set because they refer to the model selection task, and algorithm hyperparameters, which have no effect on the model’s performance but affect the speed and quality of the learning process, are two types of hyperparameters.

The selection of good hyperparameters is crucial for the training process. Activation function, alpha learning rate, hidden layers, number of epochs, number of branches in a decision tree, etc. are some of the examples of hyperparameters.

23. What is Overfitting?

Overfitting is a concept in data science when a data point does not fit against its training model. When the raining model is fed with data, there is a possibility that it might encounter some noise that cannot fit into the statistical model. This happens when the algorithm cannot perform accurately against unseen data.

24. What are the techniques used to avoid overfitting?

If we can detect overfitting at an early stage, it will be very useful for our training model. There are several methods up our sleeves that can be used to avoid overfitting-

Cross-validation: Cross-validation is a resampling technique for evaluating machine learning models on a small sample of data.
Remove features: We can remove the unnecessary features of the models to encompass the outliers.
Early stopping: Early stopping is a type of regularization used in machine learning to minimize overfitting when using an iterative method like gradient descent to train a learner. Early stopping criteria specify how many iterations can be completed before the learner becomes over-fit.
Training with more data: We can train our model with more data to accommodate outliers.
Regularization: In machine learning, regularization is a method to solve the over-fitting problem by adding a penalty term with the cost function.
Ensembling: Ensemble learning refers to combining the predictions from two or more models.

25. What is Natural Language Processing?

Natural Language Processing (NLP) is a field of Artificial Intelligence, concerned with giving computers the ability to understand and interact in human languages in a way humans can.

NLP combines rule-based modeling of human language with statistical, machine learning, and deep learning models. This makes a computer fully understand and comprehend human language in the form of voice or text. Voice-operated GPS systems, speech-to-text systems, customer service chat boxes, etc. use NLP.

26. What is the difference between eigenvalues and eigenvectors?

Eigenvalues are the coefficients given to eigenvectors that determine the length or magnitude of the vectors. Eigenvalues are unit vectors having magnitude 1. A negative eigenvalue, for example, may scale the eigenvector in the opposite way.
Eigenvectors are unit vectors, meaning their length or magnitude is the same as 1.0. They’re also known as right vectors, which simply means “column vectors” (as opposed to a row vector or a left vector). A right-vector is a vector in the traditional sense.

27. What are the different components of an expert system?

An expert system is a computer program that simulates the judgement and behavior of a human or an organization with expert knowledge and expertise in a particular field using artificial intelligence (AI) technologies.

The expert systems belong to an important domain of Artificial Intelligence, which is used to solve complex problems using extraordinary human intelligence and expertise.

The different components used to build an expert system are:

Knowledge base- It is a storage area that contains domain-specific, high-quality knowledge.
Inference engine- The Inference engine uses and manipulates the knowledge from the knowledge base.
User Interface- It provides interaction between the expert system and the user.

28. What are some differences between classification and regression?

Regression and classification are both supervised learning algorithms. Both work on labeled data and are used to predict in machine learning. The difference, however, arises from the manner in which they are used.

29. What is an Artificial Neural Network? What are some commonly used Artificial Neural networks?

Artificial Neural networks, simply called Neural networks, are computer systems based on units called nodes or artificial neurons, which resemble the neurons in human brains. Each node can transmit a signal from one node to another.

30. What Is Game Theory?

Game theory is a branch of AI that attempts to define a strategic game with predefined rules and outcomes between two players of equal rationality. Every player is selfish and tries to maximize the reward to be obtained using a particular strategy. All the players abide by certain rules in order to receive a playoff- which is a reward. Therefore, a game can be defined as a set of players, actions, strategies, and a final reward.

Game theory and AI are related to each other and complement each other. Game theory is used in AI situations where multiple agents are in an environment trying to achieve a goal. Various games are logical and have a set of pre-decided rules like chess, poker, etc., which can be made available digitally with the help of Artificial Intelligence and Game Theory.

Here are the top 30 DataOps interview questions with answers:

1. What is DataOps?

DataOps is a set of practices that combines data science, DevOps, and agile development to deliver data products and services more quickly and reliably.

2. What are the key principles of DataOps?

The key principles of DataOps include:

• Collaboration: DataOps requires collaboration between data scientists, engineers, and operations teams.
• Automation: DataOps relies heavily on automation to streamline processes and reduce manual errors.
• Continuous delivery: DataOps teams release data products and services continuously and frequently to ensure that they are always working on the latest version.
• Monitoring: DataOps teams use monitoring tools to track the performance of their data pipelines and identify any problems early on.
• Agility: DataOps teams are able to adapt quickly to change and respond to customer needs in a timely manner.

3. What are the benefits of DataOps?

The benefits of DataOps include:

• Increased speed and agility: DataOps teams can deliver data products and services more quickly and with fewer errors.
• Improved quality: DataOps teams can continuously monitor their data pipelines and identify problems early on.
• Reduced costs: DataOps can help to reduce the cost of data science and analytics.
• Increased customer satisfaction: DataOps teams can deliver data products and services that meet the needs of customers more quickly and with fewer problems.

3. What are the challenges of DataOps?

The challenges of DataOps include:

• Culture change: DataOps requires a cultural shift in the way that data teams work together.
• Technical skills: DataOps requires a deep understanding of data science, DevOps, and agile development.
• Tools: There are a number of DataOps tools available, but it can be difficult to choose the right ones for your organization.
• Data governance: DataOps teams need to ensure that data is governed and managed effectively.

4. What are the most popular DataOps tools?

The most popular DataOps tools include:

• Version control systems: Git, Subversion, Mercurial
• Continuous integration (CI) tools: Jenkins, Bamboo, TeamCity
• Continuous delivery (CD) tools: Docker, Kubernetes, Ansible
• Configuration management tools: Chef, Puppet, SaltStack
• Monitoring tools: Nagios, Prometheus, Grafana

5. What is the difference between DataOps and ETL?

ETL (Extract, Transform, Load) is a process for moving data from one system to another. DataOps is a broader term that encompasses the entire data lifecycle, from data collection to data analysis.

• DataOps includes ETL: DataOps teams use ETL as part of their data pipelines.
• DataOps is more than ETL: DataOps also includes data governance, data quality, and data security.
• What is the role of a DataOps engineer?
• A DataOps engineer is a role that combines the skills of a data scientist, a software engineer, and a DevOps engineer.
• DataOps engineers are responsible for automating the data science and analytics process, monitoring the performance of data pipelines, and responding to incidents.

6. What are some of the tasks that a DataOps engineer might perform?

Some of the tasks that a DataOps engineer might perform include:

• Setting up and configuring version control systems
• Automating the data science and analytics process
• Configuring and monitoring data pipelines
• Responding to incidents
• Troubleshooting problems
• Working with other teams to improve the data science and analytics process

7. What are some of the skills that a DataOps engineer should have?

Some of the skills that a DataOps engineer should have include:

• Strong programming skills
• Experience with version control systems
• Experience with cloud computing technologies
• Experience with automation tools
• Strong problem-solving skills
• Excellent communication skills
• Ability to work independently and as part of a team

8. What are some of the certifications that a DataOps engineer can get?

Some of the certifications that a DataOps engineer can get include:

• Certified DataOps Engineer – Foundation Level (CDOps-FL)
• Certified DataOps Engineer – Expert Level (CDOps-EL)
• Certified Cloud Data Engineer (CCDE)
• Certified Data Science Professional (CDS)
• Certified Data Scientist – Associate (CDS-A)

9. How does DataOps handle data security and access controls?

DataOps employs role-based access controls, encryption, and masking techniques to ensure data security and privacy.

10. What is version control in the context of DataOps?

Version control in DataOps involves tracking changes to data pipelines, configurations, and scripts to maintain a history of modifications and facilitate collaboration.

11. What is data lineage, and why is it important?

Data lineage traces the path of data from source to destination, helping to understand data transformations and dependencies, and ensuring data accuracy.

12. How does DataOps handle data quality issues?

DataOps employs automated data quality checks, monitoring, and alerting mechanisms to identify and rectify data quality issues.

• **13. What is the role of containers in DataOps?
• Containers provide a consistent environment for running data applications and processes, ensuring portability and reproducibility across different stages of the data lifecycle.

14. How does DataOps improve collaboration between data and development teams?

DataOps encourages shared ownership, communication, and collaboration between data engineers, data scientists, and developers through standardized processes and tools.

15. Explain the concept of “Data Catalog.”

A data catalog is a centralized repository that stores metadata about available data sources, schemas, and their relationships, aiding discovery and understanding of data assets.

16. What is data wrangling, and why is it important in DataOps?

Data wrangling involves cleaning, transforming, and preparing raw data for analysis. It’s crucial in DataOps to ensure high-quality and consistent data inputs.

17. Describe the “fail-fast” principle in DataOps.

The fail-fast principle encourages identifying issues early in the data pipeline to prevent problems from propagating downstream, thus minimizing impact.

18. What is the significance of “schema evolution” in DataOps?

Schema evolution addresses the changes in data structure over time and ensures that data pipelines and applications can handle these changes seamlessly.

19. How does DataOps support continuous data integration?

DataOps integrates data from diverse sources by automating the process of data ingestion, transformation, and loading in a repeatable and consistent manner.

20. Explain the concept of the “DataOps Maturity Model.”

The DataOps Maturity Model defines stages of DataOps adoption, from ad hoc practices to fully optimized and automated processes, allowing organizations to assess their DataOps capabilities.

21. Describe the “fail-fast” principle in DataOps.

The “fail-fast” principle involves detecting issues early in the data pipeline to prevent errors from propagating downstream and causing larger problems.

22. How can DataOps help in regulatory compliance efforts?

DataOps supports compliance by ensuring data security, privacy, and traceability, making it easier to demonstrate adherence to regulations.

23. What are “DataOps Tools,” and why are they important?

DataOps tools are software applications that automate and facilitate various aspects of data integration, quality, transformation, and management, improving efficiency and consistency.

24. How does DataOps enable faster time-to-insights?

DataOps automates data processes, reducing manual delays and errors, resulting in quicker availability of clean and accurate data for analysis.

25. Explain the concept of “DataOps Pipeline as Code.”

DataOps Pipeline as Code involves representing data pipelines using code, making pipeline definitions version-controlled, repeatable, and automated.

26. How does DataOps address data silos and integration challenges?

DataOps breaks down data silos by encouraging cross-functional collaboration, standardized processes, and automated integration.

27. What is a “DataOps Dashboard”?

A DataOps dashboard provides a visual representation of key metrics and performance indicators related to data pipelines, processes, and data quality.

28. How does DataOps support A/B testing with data?

DataOps enables seamless deployment of different data sets for A/B testing, helping to evaluate the impact of changes accurately.

29. Describe the concept of “DataOps Feedback Loop.”

The DataOps feedback loop involves gathering insights from data processes and pipeline performance to identify areas for improvement and optimize operations.

30. How can DataOps improve collaboration between data and business teams?

DataOps provides standardized processes, documentation, and self-service access to data, fostering better communication and understanding between technical and business stakeholders.

Here are the top 50 DevOps interview questions with answers:

1. What is DevOps?

Ans: DevOps is a set of practices that combines software development (Dev) and IT operations (Ops) to shorten the systems development life cycle while delivering high-quality software.

2. What are the key principles of DevOps?

Ans: The key principles of DevOps include:

• Culture: DevOps is about creating a culture of collaboration and communication between Dev and Ops teams.
• Automation: DevOps relies heavily on automation to streamline processes and reduce manual errors.
• Continuous delivery: DevOps teams release software changes continuously and frequently to ensure that they are always working on the latest version.
• Monitoring: DevOps teams use monitoring tools to track the performance of their systems and identify any problems early on.
• Agility: DevOps teams are able to adapt quickly to change and respond to customer needs in a timely manner.

3. What are the benefits of DevOps?

Ans: The benefits of DevOps include:

• Increased speed and agility: DevOps teams can release software changes more frequently and with fewer errors.
• Improved quality: DevOps teams can continuously monitor their systems and identify problems early on.
• Reduced costs: DevOps can help to reduce the cost of software development and operations.
• Increased customer satisfaction: DevOps teams can deliver software that meets the needs of customers more quickly and with fewer problems.

4. What are the challenges of DevOps?

Ans: The challenges of DevOps include:

• Culture change: DevOps requires a cultural shift in the way that Dev and Ops teams work together.
• Technical skills: DevOps requires a deep understanding of both software development and IT operations.
• Tools: There are a number of DevOps tools available, but it can be difficult to choose the right ones for your organization.
• Security: DevOps can introduce new security risks, so it is important to have a strong security culture in place.

5. What are the most popular DevOps tools?

Ans: The most popular DevOps tools include:

• Version control systems: Git, Subversion, Mercurial
• Continuous integration (CI) tools: Jenkins, Bamboo, TeamCity
• Continuous delivery (CD) tools: Docker, Kubernetes, Ansible
• Configuration management tools: Chef, Puppet, SaltStack
• Monitoring tools: Nagios, Prometheus, Grafana

6. What is the difference between Agile and DevOps?

Ans: Agile and DevOps are both approaches to software development that focus on delivering value to customers quickly and efficiently. However, there are some key differences between the two approaches.

• Agile is a methodology: Agile is a set of principles and practices that guide software development. DevOps is a broader term that encompasses the entire software development lifecycle, from development to operations.
• Agile is focused on individuals and interactions: Agile emphasizes the importance of communication and collaboration between team members. DevOps also emphasizes collaboration, but it also focuses on the automation of processes and the continuous delivery of software.
• Agile is incremental: Agile projects are delivered in increments, or sprints. DevOps teams release software changes continuously.

7. What is the role of a DevOps engineer?

Ans: A DevOps engineer is a role that combines the skills of a software developer and a system administrator. DevOps engineers are responsible for automating the software development and deployment process, monitoring the performance of systems, and responding to incidents.

8. What are some of the tasks that a DevOps engineer might perform?

Ans: Some of the tasks that a DevOps engineer might perform include:

• Setting up and configuring version control systems
• Automating the build and deployment process
• Configuring and monitoring infrastructure
• Responding to incidents
• Troubleshooting problems
• Working with other teams to improve the software development process

09. What are some of the skills that a DevOps engineer should have?

Ans: Some of the skills that a DevOps engineer should have include:

• Strong programming skills
• Experience with version control systems
• Experience with cloud computing technologies
• Experience with automation tools
• Strong problem-solving skills
• Excellent communication skills
• Ability to work independently and as part of a team

10. What are some of the certifications that a DevOps engineer can get?

Ans: Some of the certifications that a DevOps engineer can get include:

• Certified DevOps Engineer – Foundation Level (CDevOps-FL)
• Certified DevOps Engineer – Expert Level (CDevOps-EL)
• Certified Kubernetes Administrator (CKA)
• Certified Cloud DevOps Engineer (CCDE)
• Certified Cloud Solution Architect – Professional (CCSA-P)

11. Explain Blue-Green Deployment.

Ans: Blue-Green Deployment involves maintaining two identical environments: one for production (blue) and one for staging/testing (green). You switch traffic from one to the other to perform a deployment without downtime.

12. What is a microservices architecture?

Ans: Microservices architecture is an approach where a complex application is built as a collection of small, loosely coupled services that communicate over the network.

13. What is Jenkins?

Ans: Jenkins is an open-source automation server used for continuous integration and continuous delivery.

14. How does a Load Balancer work?

Ans: A Load Balancer distributes incoming network traffic across multiple servers to ensure efficient utilization and prevent overload.

15. What is monitoring in DevOps?

Ans: Monitoring involves tracking the performance and availability of applications and infrastructure to identify issues and ensure optimal functioning.

16. Explain the concept of “Infrastructure as Code” (IaC).

Ans: IaC is the practice of managing and provisioning infrastructure using code and automation tools, making infrastructure setup reproducible and version-controlled.

17. What is the role of configuration management tools in DevOps?

Ans: Configuration management tools help automate the management of software configurations, ensuring consistency across different environments.

18. Describe the concept of “Immutable Infrastructure.”

Ans: Immutable Infrastructure is an approach where infrastructure components are never modified after they are deployed; instead, they are replaced with new instances when changes are needed.

19. How can you ensure security in a DevOps environment?

Ans: Security can be ensured through code reviews, vulnerability scanning, access controls, and automated security testing integrated into the CI/CD pipeline.

20. What is the “Three-Way Handshake” in networking?

Ans: The Three-Way Handshake is a three-step process (SYN, SYN-ACK, ACK) used to establish a reliable connection between a client and a server in a TCP/IP network.

20. What is a Puppet Module?

Ans: A Puppet Module is a set of manifests and data, such as files, templates, and facts, that are organized in a certain directory structure.

21. What role do Dockers play in DevOps?

Ans: Dockers are used in DevOps to design, deploy, and run container-based applications. Developers may use Dockers to generate all components of containers, store them in libraries or other dependencies, and then distribute them out as a single package.

22. What is the difference between Git rebase and Git merge?

Ans: Git rebase differs from Git merge in that the feature branch is migrated to the master branch’s finishing point in Git rebase. In the case of Git merge, however, the merging creates a new commit in the history, which does not modify the history but does affect the master branch.

23. Is it possible to copy or transfer Jenkins from one server to another?

Ans: Yes, Jenkins may be moved or copied from one server to another. The Jenkins jobs directory, for example, maybe copied from the old server to the new server. By copying in the correct job directory, an installation may be relocated from one installation to another.

24). What distinguishes the Puppet Module from the Puppet Manifest?

Ans: The .pp extension is used by Puppet Manifests. They’re Puppet programs made out of the Puppet Code. Puppet Modules, on the other hand, collect numerous types of Puppet Manifests that may be used to separate Puppet code.

25. What makes Ansible and Puppet so different?

Ans: DevOps experts nowadays are responsible for managing and controlling a large number of servers, necessitating an exponential increase in computing as well as new technologies such as virtualization and cloud computing. As a result, Puppet and Ansible are the tools used to manage a huge number of servers.

26. Define git Stash

Ans: It is used to temporarily save changes in the working directory. This provides a clean working environment for developers. They may use the git procedure to merge the modifications. The changes in the tracked files are merged in the working directory when this command is performed. In the git directory, the stash command can be used several times.

27. What types of web applications may be launched using Azure?

Ans: The web apps that can be launched using Azure are PHP, WCF, and ASP.NET.

28. Microservices are an essential component of DevOps. Which two prominent Java development frameworks for constructing microservices can you name?

Ans: Microservices may be built with a variety of Java frameworks. However, Eclipse MicroProfile and Spring Boot stand out as the two most popular Java development frameworks for building microservices in DevOps.

29. What’s the difference between fetch and pull in Git?

Ans: Git pull is a typical command that updates the target branch with any new commits from a branch of the central repository. On the other hand, Git fetch fetches any new commits from only the specified branch and puts them in a new local repository brand.

30. What is Azure DevOps Release?

Ans: Releases, also known as Release Pipelines, allow you to provide software to clients quickly while reducing risk. Release pipelines will enable you to fully automate the testing and distribution of your software at several phases before it is released to the public. Approvals or on-demand deployments can be used to govern these automated processes.

31. What is the meaning of forks?

Ans: Forks allow you to separate sensitive, risky, or innovative changes from the source codebase. A fork creates a new copy of the code repository, including branches, commits, and files. A fork seems to be a cloned repository that has been pushed to a new, empty repository. Once you’ve established a fork, you can’t exchange fork files or branches with the original codebase unless you use a pull request.

32. What are the main areas where DevOps tools are used?

Ans: DevOps technologies have a stronghold in planning, code management, development and testing, and release management. In the DevOps ecosystem, DevOps technologies also contain functionality for deployment and monitoring activities.

33. What are some of the most widely used DevOps technologies for continuous integration and deployment?

Ans: Jenkins, GitLab CI, TeamCity, Bamboo, Codeship, CircleCI, and Travis CI are the most well-known DevOps tools for continuous integration. Azure Pipelines for Deployment, Jenkins, Bamboo, DeployBot, Shippable, ElectricFlow, and TeamCity are the most popular DevOps technologies for continuous deployment.

34. Describe IaC in detail.

Ans: Infrastructure as Code is abbreviated as IaC. It enables improved and scalable infrastructure setup by managing and tracking infrastructure settings in files. It guarantees that changes are tracked transparently using the versioning system.

35. What exactly is a chef?

Ans: Chef is a powerful platform for automating the transformation of infrastructure into code, and it also aids in the creation of scripts for the automation of IT activities.

36. What role does QA testing play in DevOps?

Ans: Before submitting the codes to the codebase, QA testing functions as a bridge between the developers and operations by completing many tests in each process or step. They actively test each phase and fix the code as needed along the process.

37. What exactly do you mean by configuration drift?

Ans: Configuration drift is when a set of servers or virtual machines running on an identical server grow progressively dissimilar over time due to updates or manual modifications to each node.

38. In DevOps, what does “shift leave” mean?

Ans: In DevOps, the term “shift left” refers to authorizing application testing at an earlier stage, before the DevOps process cycle begins.

39. Can you describe the role of Git branching strategies?

Ans: You can use Git branching in the following scenarios:

• In which condition should a new branch be created?
• From which of the previous branch will the new branch be generated?
• When will the newly established branch’s updates be merged?
• What should be the target branch for the modifications to be merged into?

40. What exactly is Docker Swarm?

Ans: A Docker swarm is a collection of virtual or physical computers on which Docker apps are executing in a cluster.

41. What are the key differences between git fetch and git pull?

Ans: Git fetch and git pull are two important commands in GitHub that are often confused with each other. Git fetch retrieves the latest data from the remote repository, but without integrating this data into the working branches. Git pull, on the other hand, retrieves and updates local branches with the new information from their corresponding remote branches.

42. What are the key differences between git merge and git rebase?

Ans: Git merge and git rebase are two commands in GitHub used to integrate changes from one branch into another. However, they integrate these changes in different ways.

A git merge creates a new commit from the head branch, whereas a git rebase rewrites the changes of one branch onto another without creating a new commit.

43. What are the key differences between containerization and virtualization?

Ans: Containerization and virtualization are the two most popular methods for hosting applications in a computer system.

Virtualization allows developers to run multiple operating systems on the hardware of a single physical server. Containerization enables developers to deploy multiple applications under the same operating system on a single virtual machine or server.

44. How is regression testing implemented?

Ans: Regression testing assesses how an application behaves after a new change has been implemented. It should be performed between integration testing and user testing.

Regression testing can be implemented by checking the original code after new changes have been made or by evaluating how updates affect performance. It can also be automated.

45. What are the key differences between cloud and on-premises services in DevOps?

Ans: Cloud and on-premises services are the two main data hosting pathways available to DevOps teams. With on-premises services, data is stored on in-house servers. With cloud services, data is hosted remotely by a third-party provider.

There are strengths and weaknesses to both strategies, which can be summarized as:

• Cloud services offer less security control over data and infrastructure, but they scale better, offer extra services, and typically incur lower costs
• On-premises services come with large maintenance costs and unique security threats, but they provide greater control and customization scope

46. What is load balancing?

Ans: Load balancing is the process of evenly distributing incoming network traffic across a group of backend servers. It occurs during the deployment phase of the DevOps lifecycle and is usually automated by developers.

47. How can the DevOps troubleshooting process be optimized?

Ans: Every DevOps team should have an established troubleshooting framework. Some of the best practices for troubleshooting are to:

• Set troubleshooting responsibilities within the team
• Gather relevant information including metrics, logs, and errors
• Hypothesize potential causes and tick them off one by one
• Closely monitor behavior after the issue has been fixed
• Report on issue resolution

48. What are the three main types of cloud computing services?

Ans: The three main types of cloud services are:

• Infrastructure-as-a-Service (IaaS), which provides internet-based access to storage and computing power, while the developer is responsible for managing everything else
• Platforms-as-a-Service (PaaS), which helps developers build web applications without needing to manage the underlying infrastructure, such as networks, servers, and storage
• Software-as-a-Service (SaaS), which hosts all components of the software application, including servers, storage, data, and the application itself

49. What is the difference between monitoring and observability?

Ans: Monitoring is a process of tracking and data collection that helps DevOps teams better understand the current state of their systems. Observability, on the other hand, uses these findings to diagnose problems and actively resolve them through debugging.

50. What are the key differences between centralized version control and distributed version control?

Ans: With centralized version control, the server’s remote repository provides the latest code to client machines. With decentralized, or distributed, version control, the complete codebase is made available on each computer’s own local repository.

Most Important JIRA Interview Questions with Answers

JIRA Alternatives were explained in detail in our previous tutorial.

This tutorial covers the most frequently asked Atlassian JIRA interview questions with detailed answers.

Defect management tools or say Bug tracking tools have been a part of software testing and development cycles for years. “JIRA” is an incident management tool, developed by Atlassian, which is commonly used for defect/issue tracking as well as project management.

Continue Reading => Training tutorials on Altlassian JIRA

This defect tracking tool is not only used for convenience-related features like recording, reporting but is also integrated directly with code development environment.

JIRA is an efficient tool and has the capability to track any kind of defects/issues. Agile projects are also supported by JIRA.

Now, above was the basic description of Atlassian JIRA, defect tracking tool. Through this article, we will discuss multiple interview question and answers which will help you understand this tool much better as well as on the other hand will help prepare for your interview.

JIRA Interview Questions and Answers

Given below is the list of most frequently asked JIRA interview questions and answers.

Q #1) Why is JIRA used?

Answer: Atlassian JIRA is basically an issue and project tracking tool which allows us to track any project related work by following a proper workflow. Enlisted below are few reasons which determine the usage of JIRA:

• Able to track project progress from time to time.
• JIRA use-cases include project management, feature implementation, bug tracking, etc.
• Work-flow can be easily customized as per our requirement.
• Along with issue tracking, history of the work done on issues, when, what and by whom can also be tracked.
• JIRA is platform independent and can run anywhere.

Q #2) Explain JIRA workflow.

Answer: Workflow defines the series of steps or stages an issue/ bug goes through during its lifecycle from creation to the closing of the issue.

The workflow here includes the creation of an issue, series of actions performed to fix the issue and the last step includes the closing or say completion of the issue after verification. This can also be understood by the below diagram:

Q #3) Enlist the report types generated by JIRA.

Answer: There are multiple reports available in JIRA which are used to show the project statistics throughout the project life cycle.

There are general reports available for analyzing issues as well as different reports for Scrum projects and Kanban projects.

Following are the general reports generated as and when required for analyzing issues:

• Average Age Report
• Created vs Resolved issue Report
• Pie Chart Report
• Recently created Issue Report
• Resolution Time Report
• Time Tracking Report
• User Work load Report
• Version Work load Report
• Workload Pie chart Report

Following are the examples of reports generated for Scrum projects:

• Sprint Report
• Control chart
• Burndown chart
• Cumulative Flow diagram
• Epic Report
• Release Burndown
• Velocity chart
• Version Report

Following are the examples of reports generated for Kanban projects:

• Control chart
• Cumulative Flow diagram.

For generating reports for your project, follow the below steps;

• Navigated to desired project dashboard.
• Click on Reports tab from left-hand side to view different reports.
• Click on Switch report to view the different report.

(Note: Click on the image for enlarged view)

Q #4) Explain the step by step procedure of how an issue is created in JIRA.

Answer: Whenever an issue or defect is encountered while testing, it needs to be reported so that the developers can work on it and take the necessary action to fix it.

We will see step by step as how an issue is created in Atlassian JIRA.

1) Log in to your JIRA account by using valid credentials and get directed to the dashboard.
2) Click on ‘Create’ button displayed and you will be navigated to a window for creating an issue.
3) Enter all the necessary details as required to create an issue. As you can see in the below image:

In Project field, project for which we are creating an issue is selected. In this example: STH_Learning(STHL) is selected from the dropdown containing all the available projects.

In Issue type field, the nature of the issue is selected from the dropdown which contains option like Bug, Task, Improvement, Story, New Feature, etc. In this example, ‘Bug’ is the nature of the issue.

Summary field contains the one line title of the issue which imparts the critical information about the issue in a summarized way. The more effective the issue headline, the more you can show the criticality of the issue. Of course, the headline should be easily understood without any chances of misinterpretation.

The example I have taken here, however is not much critical.

The Reporter is the one who reports the issue. In most of the cases, the name of the Project manager is selected in this field.

In Description field, the detailed description of the issue is written. As you can see in the below example screenshot, Steps to reproduce the issue, Actual result, Expected result are included in the description.

In Affect Version field, the current build version the project is selected in which the issue has been encountered.

Fix version field is basically selected by the concerned developer people, who choose the version as and when the work for the particular issue has been finished and the issue has been fixed.

Priority field defines which issue should be considered first to be fixed. Tester selects the priority of the issue from the dropdown based on its effect on the application. This example issue is basically of a Medium priority.

In Attachment field, any video or screenshot related to the issue is being uploaded.

In Environment field, operating system and browser details are mentioned on which issue has been encountered.

4) After all the details have been completed, Click on ‘Create’ button displayed on the window to create the new issue.

5) Issue id is generated which can be used in future reference for tracking the progress of the issue.

Q #5) Explain the three color indicators and their significance.

Answer: For any particular issue in JIRA, 3 colors like Blue, Green and Orange is used to denote the amount of time spent on any particular issue. This information is displayed under ‘Time Tracking’ section. Each colour has its own significance like;

• Blue: This color is to denote the ‘Original Estimate’ i.e. the time estimate to be invested in resolving the issue. This field has been labeled as ‘Estimated’.
• Orange: This color determines the time left for resolving the issue. This field has been labeled as ‘Remaining’.
• Green: This color defines the actual time that has been used or say spent in resolving the issue so far. This field has been labeled as ‘logged’.

Q #6) For any particular issue, what all are included under change history?

Answer: Change history section displays the activities of changing any records with information regarding the person who has made the change as well as the time at which the changes have been made.

The change history also displays the information about the old and new field values in the case of the change in any field.

Basically,  change history includes the following records of the changes:

• Creation and deletion of a comment.
• Creation and deletion of an issue link.
• Deletion of a worklog.
• File attachment changes
• Issue field changes

The change history for any issue can be viewed in JIRA by following steps:

• Open any particular issue.
• Click on ‘History’ tab present in the ‘Activity’ section.

Q #7) Mention a way with which an issue can be shared with other users in JIRA.

Answer: An issue can be shared with other users in JIRA by using the share option available on the issue description page.

When share option for any particular issue is clicked, it contains the link to the issue to be shared along with ‘Username or Email’ and ‘Note’ field that has to be filled.

Q #8) What is the importance of labeling issue?

Answer: Labeling an issue is basically done to categorize an issue within a particular section which in turn can be easily searched with the help of labels.

Label for a particular issue can be initially set at the time of creating the issue, while it can edit also within the issue. Label field is displayed under the ‘Details’ section as shown below in the figure:

Q #9) How is an issue linked in JIRA?

Answer: As the name itself defines, Linking means the association between the two.

In the same way, in JIRA issue is linked with any other issue in cases like:

• Relate to another issue
• Duplicate to another issue
• Block another issue.

For displaying the details of the Linked issues, there are two fields available in JIRA: ‘Linked issues’ and ‘Issues’.

Linked issue section contains the dropdown for the options to be selected as the reason for linking the issue. As per the selected option, the suggestion of the issues to be linked in displayed in ‘Issue’ dropdown.

Linking of issues can be done either on the same or different JIRA servers.

Q #10) What is the purpose of JIRA dashboard?

Answer: The first page which is displayed whenever we get logged in to JIRA application is ‘Dashboard’ which is basically the default or system dashboard.

A personal dashboard can also be created and designed by adding different gadgets and can be edited also as and when required. These gadgets are the means to display the project progress in terms of issues, etc.

Let us understand the steps as how a personal dashboard can be created:

1) Enter valid credentials and get navigated to JIRA dashboard.
2) Click on “…” displayed on the upper right hand side and choose option ‘Create dashboard’. You can also choose ‘Copy dashboard’ in the case of copying the currently viewed dashboard.

5) After creating a dashboard, you get navigated to a page where there are multiple options to select and add gadgets to your dashboard.

6) There is also an option available to choose and edit the layout of your dashboard.

Any particular Dashboard can be edited, copied, shared, delete from the Manage dashboard section.

Q #11) What do you mean by Scheduling an issue?

Answer: Scheduling the issue means scheduling the work of issue for a particular ‘due date’.

For this function to work, one must have ‘Schedule issue permission’ by JIRA Administrator. In this case, a field with ‘Due Date’ is being populated.

Q #12) Explain how particular project details are listed in JIRA.

Answer: Every project has some main attributes which have to be displayed in the project summary.

This attributes include:

• Name of the project
• Key
• Components
• Versions (if present)

Please refer below screenshot of Project ‘STH_L’ summary page as your reference. Although not much activity has been done in this project but this image will give you a clear idea.

As you can see from the image, the middle display area of the page shows the ‘Activity’ screen containing details on the activities done on issues or project.

The right hand side section displays the basic information about the Project like Project Lead, Key, Issue Status, etc.

The left hand side contains various options like Components, issues, Reports, Active Sprints, etc. The related information is displayed as per the selection from the option.

For Example: If I select the ‘Issue’ option, the below displayed screen will appear.

Q #13) What are issues types that are created and tracked via JIRA?

Answer: JIRA has some defined set of default issue types which are displayed under ‘Issue Type’ section.

Other issue types can be added, edited and deleted as per requirement of the project. Some of the common issue types are Bug, Task, Sub-task, Epic, Story, etc.

Their details can also be seen under Issue type section as shown in the below figure.

As the definition of ‘Issue Type Schema’ mentioned in JIRA application,

An issue type scheme determines which issue types will be available to a set of projects. It also allows specifying the order in which the issue types are presented in the user interface. There are two types of issue type schema:

• Default Issue type schema
• Scrum Issue type schema

Q #14) How is a sub-task created in JIRA?

Answer: Sub-task is the way of splitting up of parent issue into a number of small tasks which are tracked and worked on separately.

The parent issue contains the information of all its sub-tasks which can be only of the same project. A parent issue cannot be closed unless and until all its sub-tasks are closed. A sub-task has the same fields as that of any standard issue but their issue types are different.

Now, let us see step by step how a sub-task is created. I have created an issue in the below example for the understanding creation of sub-task.

1) Open a parent issue by searching with an issue id or create any new issue id.
2) On the right hand side of the issue description screen, you will see “…” . Click on it and options are displayed.
3) Click on Create Sub-task from the displayed dropdown option.

4) Create sub-task window is displayed.
5) Enter all the mandatory details and click on ‘Create’ button.

6) Now the created sub task gets added to the parent issue under sub-task section as shown below in the figure:

7) There are also options available to convert an issue into a sub task as well as sub task into an issue.

Q #15) Explain the term Cloning an issue.

Answer: Cloning an issue means copying an issue.

In this condition, a clone of the original issue is created which consist of same information as is present for the original issue. Cloning of the issue is done so that multiple users can work on the same issue, however, the operation done either on the original issue or clone issue has no effect on each other.

All the information of the original issue are cloned expect few as mentioned below:

• Time tracking
• Comments’
• Issue history
• Status and Resolution

Let us see how to create a clone of an issue:

1) Open any issue by searching with an issue id or create any new issue id.
2) On the right hand side of the issue description screen, you will see “…” . Click on it and options are displayed.
3) Click on Clone from the displayed dropdown option.

4) Clone issue window is displayed.
5) If required, you can edit the summary of the issue and click on ‘Create’ button.

6) Another issue is created with ‘CLONE’ added in the summary.

Q #16) Explain Kanban board.

Answer: Kanban boards are created for the projects where the team has their prime focus on visualizing the workflow and managing the project’s work in progress.

The most important feature of Kanban board is that it is found in work mode because the projects do not have their work as planned.

Let us see how Kanban board is created in JIRA step by step.

1) Log In to the JIRA application using valid credentials and get navigated to the dashboard.
2) Click on Project dropdown and select option ‘Create Project’.
3) Select ‘Kanban Software development’ and click on Next button.

4) Enter all the necessary details and click on Create button.
5) Kanban board is created as shown in below example.

Note: I have just taken a basic example of creation

In the case of Kanban, the incoming task is given more priority and hence it is considered as the best methodology for cases like bug fixing and maintenance release.

Q #17) Mention one similarity and one difference between JIRA Scrum and JIRA Kanban.

Answer:

Similarity: Both JIRA Scrum and Kanban is considered as the most powerful process tool for optimization of work and the processes as both processes focus is on continuous optimization and visualizing the workflow. In these cases, large and the complex tasks are broken down and each individual tasks are worked on and completed efficiently.

Difference: Scrum board is the work mode where progress of sprints and tracking of its work is done. Here the team determines the list of issues that has become backlog and then these issues are moved to sprints as per team plan.

In the case of Kanban board, the work in progress activities is being maintained and their process flow is tracked. Here the team decides the increase and decrease of the number of issues that is to be displayed in each status of the workflow.

Q #18) What are the most useful JIRA add-ons.

Answer: Some of the most useful JIRA add-ons are listed below:

• Jenkins-CI
• Usersnap
• Slack
• HipChat
• GitHub
• PagerDuty
• Tempo Timesheets

Q #19) What comes under JIRA Schema?

Answer: JIRA Schema consists of the following:

• Workflows
• Issue types
• Custom fields
• Screens
• Field configurations
• Notifications
• Permissions

Q #20) How is security setting helpful in JIRA?

Answer: Security setting for any issue is defined or say set either at the time of creation of the issue or while editing the issue.

The basic reason for security setting is to restrict the user access to the issue so that not all users are able to work on that issue. Security setting also allows the access of the issue to the member of chosen security level.

Conclusion

Through this article, I have covered everything which is necessary to know as a part of understanding and learning this famous and most useful issue tracking tool i.e. JIRA.

Although it was not possible to take any ongoing project as an example to make things clear, I have created a new id and new project in JIRA, so that I can provide my answers with screenshots for better understanding. Hope this article proves helpful for your preparation for interviews.