Add a couple of questions

topics/devops/README.md

@@ -1,4 +1,8 @@
-## DevOps
+# DevOps
+
+## Questions
+
+### General 
 
 <details>
 <summary>What is DevOps?</summary><br><b>
@@ -69,7 +73,7 @@ A couple of thoughts:
 3. You might want to set a possibly better goal such as "be able to deploy whenever we need to deploy"
 </b></details>
 
-#### Tooling
+### Tooling
 
 <details>
 <summary>What do you take into consideration when choosing a tool/technology?</summary><br><b>
@@ -120,7 +124,7 @@ Things to think about:
 * What does the switch from one platform to another will require from the organization? For example, training users who use the platform? How much time the team has to invest in such move?
 </b></details>
 
-#### Version Control
+### Version Control
 
 <details>
 <summary>What is Version Control?</summary><br><b>
@@ -179,7 +183,7 @@ to a server will result in a new server instead of updating it. Terraform is an
 which follows the immutable infrastructure paradigm.
 </b></details>
 
-#### Software Distribution
+### Software Distribution
 
 <details>
 <summary>Explain "Software Distribution"</summary><br><b>
@@ -414,6 +418,8 @@ Note: cross-dependency is when you have two or more changes to separate projects
 <summary>What is Distributed Tracing?</summary><br><b>
 </b></details>
 
+### GitOps
+
 <details>
 <summary>What is GitOps?</summary><br><b>
 
@@ -422,6 +428,20 @@ GitLab: "GitOps is an operational framework that takes DevOps best practices use
 Read more [here](https://about.gitlab.com/topics/gitops)
 </b></details>
 
+<details>
+<summary>What are some of the advantages of applying GitOps?</summary><br><b>
+
+* It introduces limited/granular access to infrastructure
+* It makes it easier to trace who makes changes to infrastructure
+</b></details>
+
+<details>
+<summary>What are some practical implementations or practices of GitOp?</summary><br><b>
+
+* Store Infra files in a version control repository (like Git)
+* Apply review/approval process for changes
+</b></details>
+
 #### SRE
 
 <details>