Repos-que-me-gustan/devops-exercises
1
0
Fork 0
Code Pull Requests Activity

Add questions and answers

Browse Source
This commit is contained in:
abregman 2019-12-12 00:00:40 +02:00
parent 265fb49cf9
commit a8c2888738
1 changed files with 21 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

23
README.md
View File

@ -2,7 +2,7 @@
:information_source:  This repository contains questions on various DevOps and SRE related topics :information_source:  This repository contains questions on various DevOps and SRE related topics
:bar_chart:  There are currently **612** questions :bar_chart:  There are currently **615** questions
:books:  To learn more about DevOps check the resources in [DevOpsBit.com](https://devopsbit.com) :books:  To learn more about DevOps check the resources in [DevOpsBit.com](https://devopsbit.com)
@ -1209,6 +1209,10 @@ Zombie (z)
<details> <details>
<summary>What is a zombie process?</summary><br><b> <summary>What is a zombie process?</summary><br><b>
A process which has finished to run but has not exited.
One reason it happens is when a parent process is programmed incorrectly. Every parent process should execute wait() to get the exit code from the child process which finished to run. But when the parent isn't checking for the child exit code, the child process can still exists although it finished to run.
</b></details> </b></details>
<details> <details>
@ -1509,6 +1513,10 @@ There are a couple of ways to do that:
* fallocate -l 2097152 new_file.txt * fallocate -l 2097152 new_file.txt
</b></details> </b></details>
<details>
<summary>Explain the fork() system call</summary><br><b>
</b></details>
<details> <details>
<summary>What are the differences between the following system calls?: exec(), fork(), vfork() and clone()?</summary><br><b> <summary>What are the differences between the following system calls?: exec(), fork(), vfork() and clone()?</summary><br><b>
</b></details> </b></details>
@ -1578,8 +1586,11 @@ False. It was true in the past but today's operating systems perform lazy loadin
<details> <details>
<summary>What are different states of a process?</summary><br><b> <summary>What are different states of a process?</summary><br><b>
</b></details>
* Running - it's executing instructions
* Ready - it's ready to run but for different reasons it's on hold
* Blocked - it's waiting for some operation to complete. For example I/O disk request
</b></details>
## Virtualization ## Virtualization
@ -3066,6 +3077,10 @@ Logging
<summary>Describe Prometheus architecture and components</summary><br><b> <summary>Describe Prometheus architecture and components</summary><br><b>
</b></details> </b></details>
<details>
<summary>Have you set up Prometheus? How did you do it? Describe the process</summary><br><b>
</b></details>
<details> <details>
<summary>Can you compare Prometheus to other solutions like InfluxDB for example?</summary><br><b> <summary>Can you compare Prometheus to other solutions like InfluxDB for example?</summary><br><b>
</b></details> </b></details>
@ -3106,6 +3121,10 @@ Alert manager is responsible for alerts ;)
<summary>How to get total requests in a given period of time?</summary><br><b> <summary>How to get total requests in a given period of time?</summary><br><b>
</b></details> </b></details>
<details>
<summary>What HA in Prometheus means?</summary><br><b>
</b></details>
<a name="prometheus-advanced"></a> <a name="prometheus-advanced"></a>
#### :star: Advanced #### :star: Advanced