Rename repository

Unforunately, It came to my knowledge that this repository
promoted a phenomenon where DevOps interviews became a trivia game
where people think it's normal to throw 20 random short questions
like "what is fork()" or "which tools would you use for each
of the following areas?" and this was not my intention.

To explcitly state this repository doesn't represents real DevOps
interview questions I've decided to rename it.

README.md

@@ -1,16 +1,14 @@
-# DevOps Interview Questions
+# DevOps Questions & Exercises
 
-:information_source:  This repository contains questions on various DevOps and SRE related topics
+:information_source:  This repo contains questions and exercises on various technical topics, sometimes related to DevOps and SRE :)
 
-:bar_chart:  There are currently **804** questions
+:bar_chart:  There are currently **819** questions
 
-:warning:  The purpose of this repo is to help you test your knowledge and prepare for interviews. It doesn't represents a DevOps interview. Please read [Q&A](common-qa.md) for more details
+:warning:  These are not interview questions and most of them shouldn't be used as interview questions. Please read [Q&A](common-qa.md) for more details
 
-:thought_balloon:  If you wonder how to prepare to your DevOps Interview, we added a couple of suggestions [here](prepare_for_interview.md)
+:thought_balloon:  If you wonder "How to prepare for a DevOps interview?", you might want to read some of my suggestions [here](prepare_for_interview.md)
 
-:pencil:  You can add more questions & answers by submitting pull requests :) You can read more about it [here](CONTRIBUTING.md)
+:pencil:  You can add more questions and exercises by submitting pull requests :) You can read more about it [here](CONTRIBUTING.md)
-
-:cn:  You can find a [中文](README-zh_CN.md) Chinese translation right [here](README-zh_CN.md)
 
 ****
 
@@ -63,7 +61,7 @@
     <td align="center"><a href="#databases"><img src="images/databases.png" width="75px;" height="75px;" alt="Databases"/><br /><b>Databases</b></a></td>
     <td align="center"><a href="#design"><img src="images/design.png" width="110px;" height="75px;" alt="Design"/><br /><b>Design</b></a></td>
     <td align="center"><a href="#questions-you-ask"><img src="images/you.png" width="110px;" height="75px;" alt="you"/><br /><b>Questions you ask</b></a></td>
-    <td align="center"><a href="#challenges"><img src="images/challenges.png" width="110px;" height="75px;" alt="Challenges"/><br /><b>Challenges</b></a></td>
+    <td align="center"><a href="#exercises"><img src="images/exercises.png" width="110px;" height="75px;" alt="Exercises"/><br /><b>Exercises</b></a></td>
   </tr>
 </table>
 </center>
@@ -1853,18 +1851,36 @@ wait() is used by a parent process to wait for the child process to finish execu
 If wait is not used by a parent process then a child process might become a zombie process.
 </b></details>
 
+<details>
+<summary>What execve() does?</summary><br><b>
+
+Executes a program. The program is passed as a filename (or path) and must be a binary executable or a script.
+</b></details>
+
 <details>
 <summary>What happens when you execute <code>ls -l</code>?</summary><br><b>
 
 * Shell reads the input using getline() which reads the input file stream and stores into a buffer as a string
 * The buffer is broken down into tokens and stored in an array this way: {"ls", "-l", "NULL"}
 * Shell checks if an expansion is required (in case of ls *.c)
+
+* Once the program in memory, its execution starts. First by calling readdir()
+
+Notes:
+
+* getline() originates in GNU C library and used to read lines from input stream and stores those lines in the buffer
 </b></details>
 
 <details>
 <summary>What happens when you execute <code>ls -l *.log</code>?</summary><br><b>
 </b></details>
 
+<details>
+<summary>What readdir() system call does?</summary><br><b>
+
+
+</b></details>
+
 #### Linux Filesystem & Files
 
 <details>
@@ -5987,31 +6003,30 @@ Instead of working in "push mode", the consumers can pull tasks only when they a
 <summary>How would you scale the architecture from the previous question to hundreds of users?</summary><br><b>
 </b></details>
 
-## Challenges
+## Exercises
 
-Challenges require you one of the following:
+Exercises are all about:
 
-  * Set up environments
+  * Setting up environments
-  * Write scripts
+  * Writing scripts
-  * Design and/or develop infrastructure projects
+  * Designing and/or developing infrastructure apps
-  * Fix existing applications
+  * Fixing existing applications
 
-These type of questions usually given as an home task to the candidate and they can combine several topics together.
+Below you can find several exercises
-Below you can find several challenges:
 
-* [Writing a Dockerfile and running a container](challenges/write_dockerfile_run_container.md)
+* [Writing a Dockerfile and running a container](exercises/write_dockerfile_run_container.md)
-* [Elasticsearch & Kibana on AWS](challenges/elk_kibana_aws.md)
+* [Elasticsearch & Kibana on AWS](exercises/elk_kibana_aws.md)
-* [Ansible, Minikube and Docker](challenges/ansible_minikube_docker.md)
+* [Ansible, Minikube and Docker](exercises/ansible_minikube_docker.md)
-* [Cloud Slack bot](challenges/cloud_slack_bot.md)
+* [Cloud Slack bot](exercises/cloud_slack_bot.md)
-* [Jenkins: writing scripts](challenges/jenkins_scripts.md)
+* [Jenkins: writing scripts](exercises/jenkins_scripts.md)
-* [Jenkins: writing pipelines](challenges/jenkins_pipelines.md)
+* [Jenkins: writing pipelines](exercises/jenkins_pipelines.md)
-* [CI for open source project](challenges/ci_for_open_source_project.md)
+* [CI for open source project](exercises/ci_for_open_source_project.md)
-* [Flask, Containers and CI](challenges/flask_container_ci/README.md)
+* [Flask, Containers and CI](exercises/flask_container_ci/README.md)
 
 
 ## Credits
 
-Thanks to all of our amazing [contributors](https://github.com/bregman-arie/devops-interview-questions/graphs/contributors) who make it easy for everyone to learn and prepare to their interviews.
+Thanks to all of our amazing [contributors](https://github.com/bregman-arie/devops-exercises/graphs/contributors) who make it easy for everyone to learn and prepare to their interviews.
 
 Logos credits can be found [here](credits.md)
 

common-qa.md

@@ -2,40 +2,23 @@
 
 ### What is the purpose of repository?
 
-To learn, of course :)
+1. Learn - asking questions or doing exercises is a great way to learn
-Or more specifically, any of the following:
+2. Share - sharing knowledge is a great experience, give it a try
 
-* Test your knowledge
+It is also used sometimes (from what I've been told) to prepare for interviews but a note for interviewers: most of the questions in this repository shouldn't be used as interview questions. A DevOps interview (or any technical interview) is not a trivia game :)
-* Prepare for interviews
-* Simply learning something new :)
 
-### Are these real DevOps interview questions?
+### My goal is to prepare for a DevOps interview. How to do that?
 
-The answer is no. While the name of the repository indicates it should include only (or mainly) DevOps Interview Questions in reality, this repository includes many questions on many different topics - Linux, Git, Python, ... Only small subset of the questions are actually DevOps questions.
+I've added a couple of suggestions here [here](prepare_for_interview.md)
-
+Feel free to contribute any ideas and insights
-If you wonder why then it quite simple. DevOps is still, after many years, a controversial topic. If you ask different people what is DevOps, you'll get different answers and DevOps interviews are not an exception in this case. Different DevOps interviews will include different questions on various topics. Some of the questions you'll be asked might be included in this repository, some might none. It's even possible you'll be asked none of the questions in this repository but in my opinion it's still decent test of your knowledge.
-
-Also, I can rename the project name to better represent its content but "coding-operations-HR-...-interview-questions" is too long name for a repository :)
-
-### Should I be familiar with all the tools/platforms/... listed in this repository?
-
-NO NO NO! :)<br>
-"DevOps is a culture, not a role" is BS. Same goes for "DevOps is not about tools". And yet, one thing is for sure, DevOps is not about being familiar with all the existing tools.
-
-With that being said, there are some concepts, tools, platforms, ... that are quite common in jobs requirements. Take Linux for example. While Linux is not a requirement of every DevOps position out there, it's still quite a desired skill and probably appear as a requirement in more than 90% of the DevOps positions if I had to guess. So it will be wise to be familiar with Linux as well as some other concepts/tool/projects...
-
-### How should I prepare for my DevOps interview?
-
-Excellent question. This repository alone might not be enough in some cases. We are exploring the answer to this question [here](prepare_for_interview.md)
-If you have any ideas, insights, questions, ... please contribute :)
 
 ### How do I become a better DevOps Engineer?
 
-That's even a better question than the previous one.<br>
+That's a great question.<br>
 I don't have a definitive answer for this question, but what I feel works for me is to:
 
+  * Practice - doing DevOps tasks/work is probably the best way to gain experience and knowledge
   * Read - Read blogs, books, ... anything that can enrich you about DevOps
-  * Practice - Some practical DevOps work at work and/or home
   * Share - This is one of the reasons I created this project. Primary goal was to help others but a secondary goal quickly became to learn more. By asking questions, you actually learn better a certain topic. Try it out, take a certain subject and try to come up with questions you would ask someone to test his/her skills.
 
 ### Why most of the questions don't have answers?
@@ -66,22 +49,15 @@ You can but:
 * Not without attribution. Many people worked hard on adding these questions and they deserve a proper credit for their work
 * Not if you plan to make money out of it. Directly or indirectly (e.g. ADS) as this is a free content and we would like it to stay this way :)
 
-### If there are already many interview questions sites why creating this repository?
-
-Good question. When a friend asked me to help him with learning for an interview, I was curious what the Internet has to offer as an help for people, like my friend, who want to prepare for their DevOps interviews and to be honest, I was pretty shocked to find out questions like the following:
-
-* How to install Git/Jenkins/...?
-* How do you open the terminal in Linux?
-
-These, in my opinion, are questions no one should ever ask in an interview and so, I decided to start my own interview questions project to help others (and yes, also myself) to test their knowledge.
-
 ### Can I add questions and/or answers to this project?
 
 I'll simply imagine you didn't ask that on an open source project... :)
 
-### Why can't I add installation interview questions?
+### Why can't I add installation questions?
 
-Personally, I don't think installation questions are interview questions. Yes, I know many sites and sources advertise them as such but personally I think we should have the responsibility to not encourage or even create a phenomenon where interviewers will think it's normal or has any benefit to ask such questions. If you think there is value in this, please create an issue and I'll be happy to discuss this with you.
+Because these is one of the worst types of questions out there.
+
+Some sites claim "How to install Jenkins?" or "What is the home directory of Jenkins?" are proper interview questions but personally I think we should have the responsibility to not encourage or even create a phenomenon where interviewers will think it's normal or has any benefit to ask such questions.
 
 ### Where can I practice coding?
 

scripts/count_questions.sh

@@ -2,4 +2,4 @@
 
 # We dont care about non alphanumerics filenames so we just ls | grep to shorten the script.
 
-echo $(( $(ls ./challenges/ | grep ".*md" -c) + $(grep \</summary\> -c README.md) ))
+echo $(( $(ls ./exercises/ | grep ".*md" -c) + $(grep \</summary\> -c README.md) ))