├── .github ├── ISSUE_TEMPLATE │ ├── bug_report.md │ ├── feature_request.md │ └── task.md └── PULL_REQUEST_TEMPLATE.md ├── CODE_OF_CONDUCT.md ├── CONTRIBUTING.md ├── LICENSE ├── README.md ├── devops_with_aws └── README.md ├── devops_with_azure └── README.md ├── devops_with_gcp └── README.md ├── devops_with_sre ├── 5+yrs_DevopswithSRE.md └── README.md └── devops_without_cloud ├── README.md └── questions.txt /.github/ISSUE_TEMPLATE/bug_report.md: -------------------------------------------------------------------------------- 1 | ## Bug Report 2 | 3 | **Description:** 4 | 5 | 6 | **DevOps Category:** 7 | 8 | - [ ] DevOps with AWS 9 | - [ ] DevOps with Azure 10 | - [ ] DevOps with GCP 11 | - [ ] DevOps without Cloud 12 | - [ ] DevOps with SRE 13 | 14 | **Expected Behavior:** 15 | 16 | 17 | **Current Behavior:** 18 | 19 | 20 | **Steps to Reproduce:** 21 | 22 | 23 | **Screenshots (if applicable):** 24 | 25 | 26 | **Additional Information:** 27 | 28 | 29 | **Checklist:** 30 | 31 | - [ ] My bug report adheres to the [Code of Conduct](CODE_OF_CONDUCT.md) of this repository. 32 | - [ ] I have read and followed the [Contribution Guidelines](CONTRIBUTING.md) of this repository. 33 | - [ ] I have searched the existing issues and confirmed that this is not a duplicate. 34 | -------------------------------------------------------------------------------- /.github/ISSUE_TEMPLATE/feature_request.md: -------------------------------------------------------------------------------- 1 | ## Feature Request 2 | 3 | **Description:** 4 | 5 | 6 | **DevOps Category:** 7 | 8 | - [ ] DevOps with AWS 9 | - [ ] DevOps with Azure 10 | - [ ] DevOps with GCP 11 | - [ ] DevOps without Cloud 12 | - [ ] DevOps with SRE 13 | 14 | **Expected Behavior:** 15 | 16 | 17 | **Current Behavior:** 18 | 19 | 20 | **Reasoning:** 21 | 22 | 23 | **Additional Context:** 24 | 25 | 26 | **Checklist:** 27 | 28 | - [ ] My feature request adheres to the [Code of Conduct](CODE_OF_CONDUCT.md) of this repository. 29 | - [ ] I have read and followed the [Contribution Guidelines](CONTRIBUTING.md) of this repository. 30 | - [ ] I have searched the existing issues and confirmed that this is not a duplicate. 31 | -------------------------------------------------------------------------------- /.github/ISSUE_TEMPLATE/task.md: -------------------------------------------------------------------------------- 1 | ## Task 2 | 3 | **Description:** 4 | 5 | 6 | **DevOps Category:** 7 | 8 | - [ ] DevOps with AWS 9 | - [ ] DevOps with Azure 10 | - [ ] DevOps with GCP 11 | - [ ] DevOps without Cloud 12 | - [ ] DevOps with SRE 13 | 14 | **Steps to Complete:** 15 | 16 | 17 | **Additional Information:** 18 | 19 | 20 | **Checklist:** 21 | 22 | - [ ] My task adheres to the [Code of Conduct](CODE_OF_CONDUCT.md) of this repository. 23 | - [ ] I have read and followed the [Contribution Guidelines](CONTRIBUTING.md) of this repository. 24 | - [ ] I have searched the existing issues and confirmed that this task is not already assigned or in progress. 25 | -------------------------------------------------------------------------------- /.github/PULL_REQUEST_TEMPLATE.md: -------------------------------------------------------------------------------- 1 | ## Pull Request Description 2 | 3 | 4 | 5 | ## Type of Contribution 6 | 7 | 8 | - [ ] Interview Experience 9 | - [ ] Interview Questions 10 | - [ ] Scenario-Based Questions and Answers 11 | - [ ] Improvements and Updates 12 | 13 | ## DevOps Category 14 | 15 | 16 | - [ ] DevOps with AWS 17 | - [ ] DevOps with Azure 18 | - [ ] DevOps with GCP 19 | - [ ] DevOps without Cloud 20 | - [ ] DevOps with SRE 21 | 22 | ## Details 23 | 24 | 25 | 26 | ## Checklist 27 | 28 | 29 | 30 | - [ ] My contribution adheres to the [Code of Conduct](CODE_OF_CONDUCT.md) of this repository. 31 | - [ ] I have read and followed the [Contribution Guidelines](CONTRIBUTING.md) of this repository. 32 | - [ ] I have tested my changes (if applicable) and they do not cause any issues. 33 | - [ ] My contribution does not violate any intellectual property rights, trademarks, or copyrights. 34 | -------------------------------------------------------------------------------- /CODE_OF_CONDUCT.md: -------------------------------------------------------------------------------- 1 | # DevOps Interview Questions and Experiences - Code of Conduct 2 | 3 | ## Our Pledge 4 | 5 | In the DevOps Interview Questions and Experiences repository, we are committed to creating a welcoming, inclusive, and respectful community. We value diversity and are dedicated to providing a harassment-free environment for everyone, regardless of their background, identity, or experience level. 6 | 7 | ## Expected Behavior 8 | 9 | To foster a positive and collaborative environment, we expect all contributors and users to: 10 | 11 | 1. Be respectful and considerate of others' opinions, experiences, and ideas. 12 | 13 | 2. Refrain from any form of harassment, discrimination, or offensive language, both in interactions and content contributions. 14 | 15 | 3. Participate in discussions constructively and professionally. 16 | 17 | 4. Be open to feedback and willing to learn from others in the community. 18 | 19 | 5. Respect the guidelines and rules of the repository while contributing or engaging in discussions. 20 | 21 | ## Unacceptable Behavior 22 | 23 | The following behaviors are deemed unacceptable and will not be tolerated within the DevOps Interview Questions and Experiences repository: 24 | 25 | 1. Harassment: Any form of offensive, intimidating, or hostile behavior, including but not limited to, verbal comments, written messages, imagery, or any other content. 26 | 27 | 2. Discrimination: Treating individuals differently based on attributes such as race, ethnicity, gender, sexual orientation, age, religion, disability, or any other personal characteristic. 28 | 29 | 3. Trolling and Offensive Language: Engaging in disruptive or provocative behavior, or using offensive language that undermines the positive environment of the community. 30 | 31 | 4. Violation of Intellectual Property: Submitting content that infringes on intellectual property rights, trademarks, or copyrights. 32 | 33 | 5. Spamming: Flooding the repository with irrelevant, promotional, or unsolicited content. 34 | 35 | ## Reporting and Enforcement 36 | 37 | If you encounter behavior that violates this code of conduct, please report it immediately to the repository maintainers by emailing [your_email@example.com]. All reports will be reviewed and treated with confidentiality. The maintainers reserve the right to take appropriate actions, including warning, moderating, or banning individuals who violate the code of conduct. 38 | 39 | ## Acknowledgment 40 | 41 | This Code of Conduct is adapted from the Contributor Covenant, version 2.0, available at https://www.contributor-covenant.org/version/2/0/code_of_conduct.html. 42 | 43 | ## Contact 44 | 45 | If you have any questions or concerns regarding this code of conduct or the repository in general, please contact [your_email@example.com]. 46 | 47 | We value your contribution and cooperation in maintaining a friendly and inclusive community for everyone. 48 | 49 | Thank you for being part of the DevOps Interview Questions and Experiences community! 50 | -------------------------------------------------------------------------------- /CONTRIBUTING.md: -------------------------------------------------------------------------------- 1 | # Contributing to DevOps Interview Questions and Experiences 2 | 3 | Thank you for your interest in contributing to the DevOps Interview Questions and Experiences repository! Your contributions play a vital role in building a valuable resource for the DevOps community. To ensure a smooth and collaborative experience, please read and follow the guidelines below. 4 | 5 | ## Table of Contents 6 | 7 | - [How to Contribute](#how-to-contribute) 8 | - [Types of Contributions](#types-of-contributions) 9 | - [Contribution Guidelines](#contribution-guidelines) 10 | - [Code of Conduct](#code-of-conduct) 11 | - [License](#license) 12 | 13 | ## How to Contribute 14 | 15 | Contributing to this repository is straightforward. Follow these steps to share your DevOps interview experiences and questions: 16 | 17 | 1. Fork this repository to your GitHub account. 18 | 19 | 2. Clone the forked repository to your local machine. 20 | 21 | 3. Create a new Markdown file in the appropriate category folder that best represents your interview. Choose from one of the following categories: 22 | - DevOps with AWS 23 | - DevOps with Azure 24 | - DevOps with GCP 25 | - DevOps without Cloud 26 | - DevOps with SRE 27 | 28 | 4. Use the provided PR template to structure your interview experience. Be detailed in your responses to provide valuable insights to others. 29 | 30 | 5. Commit your changes and create a Pull Request (PR) to this repository. 31 | 32 | 6. Our team will review your PR, and upon approval, your interview experience will be added to the repository, benefiting the DevOps community. 33 | 34 | ## Types of Contributions 35 | 36 | You can contribute to this repository in the following ways: 37 | 38 | 1. **Interview Experiences**: Share your personal experiences from DevOps interviews. Include the company name, interview date, position applied for, interview format, questions asked, and your answers. 39 | 40 | 2. **Interview Questions**: Provide a list of relevant interview questions for a specific DevOps category or technology. 41 | 42 | 3. **Scenario-Based Questions and Answers**: Share scenario-based interview questions and your responses for specific DevOps roles or technologies. 43 | 44 | 4. **Improvements and Updates**: Help improve the existing content, update outdated information, fix formatting, etc. 45 | 46 | ## Contribution Guidelines 47 | 48 | To ensure consistency and quality in contributions, please adhere to the following guidelines: 49 | 50 | 1. Use Markdown format for your interview experiences and questions. 51 | 52 | 2. Clearly specify the DevOps category or technology (e.g., AWS, Azure, GCP, etc.) in your contribution. 53 | 54 | 3. Be detailed and informative while sharing your interview experiences. 55 | 56 | 4. Ensure your contribution is relevant and appropriate for the DevOps community. 57 | 58 | 5. Avoid submitting content that violates any intellectual property rights, trademarks, or copyrights. 59 | 60 | 6. Respect the [Code of Conduct](CODE_OF_CONDUCT.md) while participating in discussions and interactions. 61 | 62 | ## Code of Conduct 63 | 64 | Please familiarize yourself with our [Code of Conduct](CODE_OF_CONDUCT.md). We expect all contributors and users to follow these guidelines to maintain a welcoming and inclusive environment for everyone. 65 | 66 | ## License 67 | 68 | By contributing to this repository, you agree to license your contributions under the [MIT License](LICENSE). 69 | 70 | Thank you for your interest in contributing to the DevOps Interview Questions and Experiences repository. We look forward to your valuable contributions! 71 | 72 | Happy interviewing and learning! 73 | -------------------------------------------------------------------------------- /LICENSE: -------------------------------------------------------------------------------- 1 | Apache License 2 | Version 2.0, January 2004 3 | http://www.apache.org/licenses/ 4 | 5 | TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION 6 | 7 | 1. Definitions. 8 | 9 | "License" shall mean the terms and conditions for use, reproduction, 10 | and distribution as defined by Sections 1 through 9 of this document. 11 | 12 | "Licensor" shall mean the copyright owner or entity authorized by 13 | the copyright owner that is granting the License. 14 | 15 | "Legal Entity" shall mean the union of the acting entity and all 16 | other entities that control, are controlled by, or are under common 17 | control with that entity. For the purposes of this definition, 18 | "control" means (i) the power, direct or indirect, to cause the 19 | direction or management of such entity, whether by contract or 20 | otherwise, or (ii) ownership of fifty percent (50%) or more of the 21 | outstanding shares, or (iii) beneficial ownership of such entity. 22 | 23 | "You" (or "Your") shall mean an individual or Legal Entity 24 | exercising permissions granted by this License. 25 | 26 | "Source" form shall mean the preferred form for making modifications, 27 | including but not limited to software source code, documentation 28 | source, and configuration files. 29 | 30 | "Object" form shall mean any form resulting from mechanical 31 | transformation or translation of a Source form, including but 32 | not limited to compiled object code, generated documentation, 33 | and conversions to other media types. 34 | 35 | "Work" shall mean the work of authorship, whether in Source or 36 | Object form, made available under the License, as indicated by a 37 | copyright notice that is included in or attached to the work 38 | (an example is provided in the Appendix below). 39 | 40 | "Derivative Works" shall mean any work, whether in Source or Object 41 | form, that is based on (or derived from) the Work and for which the 42 | editorial revisions, annotations, elaborations, or other modifications 43 | represent, as a whole, an original work of authorship. For the purposes 44 | of this License, Derivative Works shall not include works that remain 45 | separable from, or merely link (or bind by name) to the interfaces of, 46 | the Work and Derivative Works thereof. 47 | 48 | "Contribution" shall mean any work of authorship, including 49 | the original version of the Work and any modifications or additions 50 | to that Work or Derivative Works thereof, that is intentionally 51 | submitted to Licensor for inclusion in the Work by the copyright owner 52 | or by an individual or Legal Entity authorized to submit on behalf of 53 | the copyright owner. For the purposes of this definition, "submitted" 54 | means any form of electronic, verbal, or written communication sent 55 | to the Licensor or its representatives, including but not limited to 56 | communication on electronic mailing lists, source code control systems, 57 | and issue tracking systems that are managed by, or on behalf of, the 58 | Licensor for the purpose of discussing and improving the Work, but 59 | excluding communication that is conspicuously marked or otherwise 60 | designated in writing by the copyright owner as "Not a Contribution." 61 | 62 | "Contributor" shall mean Licensor and any individual or Legal Entity 63 | on behalf of whom a Contribution has been received by Licensor and 64 | subsequently incorporated within the Work. 65 | 66 | 2. Grant of Copyright License. Subject to the terms and conditions of 67 | this License, each Contributor hereby grants to You a perpetual, 68 | worldwide, non-exclusive, no-charge, royalty-free, irrevocable 69 | copyright license to reproduce, prepare Derivative Works of, 70 | publicly display, publicly perform, sublicense, and distribute the 71 | Work and such Derivative Works in Source or Object form. 72 | 73 | 3. Grant of Patent License. Subject to the terms and conditions of 74 | this License, each Contributor hereby grants to You a perpetual, 75 | worldwide, non-exclusive, no-charge, royalty-free, irrevocable 76 | (except as stated in this section) patent license to make, have made, 77 | use, offer to sell, sell, import, and otherwise transfer the Work, 78 | where such license applies only to those patent claims licensable 79 | by such Contributor that are necessarily infringed by their 80 | Contribution(s) alone or by combination of their Contribution(s) 81 | with the Work to which such Contribution(s) was submitted. If You 82 | institute patent litigation against any entity (including a 83 | cross-claim or counterclaim in a lawsuit) alleging that the Work 84 | or a Contribution incorporated within the Work constitutes direct 85 | or contributory patent infringement, then any patent licenses 86 | granted to You under this License for that Work shall terminate 87 | as of the date such litigation is filed. 88 | 89 | 4. Redistribution. You may reproduce and distribute copies of the 90 | Work or Derivative Works thereof in any medium, with or without 91 | modifications, and in Source or Object form, provided that You 92 | meet the following conditions: 93 | 94 | (a) You must give any other recipients of the Work or 95 | Derivative Works a copy of this License; and 96 | 97 | (b) You must cause any modified files to carry prominent notices 98 | stating that You changed the files; and 99 | 100 | (c) You must retain, in the Source form of any Derivative Works 101 | that You distribute, all copyright, patent, trademark, and 102 | attribution notices from the Source form of the Work, 103 | excluding those notices that do not pertain to any part of 104 | the Derivative Works; and 105 | 106 | (d) If the Work includes a "NOTICE" text file as part of its 107 | distribution, then any Derivative Works that You distribute must 108 | include a readable copy of the attribution notices contained 109 | within such NOTICE file, excluding those notices that do not 110 | pertain to any part of the Derivative Works, in at least one 111 | of the following places: within a NOTICE text file distributed 112 | as part of the Derivative Works; within the Source form or 113 | documentation, if provided along with the Derivative Works; or, 114 | within a display generated by the Derivative Works, if and 115 | wherever such third-party notices normally appear. The contents 116 | of the NOTICE file are for informational purposes only and 117 | do not modify the License. You may add Your own attribution 118 | notices within Derivative Works that You distribute, alongside 119 | or as an addendum to the NOTICE text from the Work, provided 120 | that such additional attribution notices cannot be construed 121 | as modifying the License. 122 | 123 | You may add Your own copyright statement to Your modifications and 124 | may provide additional or different license terms and conditions 125 | for use, reproduction, or distribution of Your modifications, or 126 | for any such Derivative Works as a whole, provided Your use, 127 | reproduction, and distribution of the Work otherwise complies with 128 | the conditions stated in this License. 129 | 130 | 5. Submission of Contributions. Unless You explicitly state otherwise, 131 | any Contribution intentionally submitted for inclusion in the Work 132 | by You to the Licensor shall be under the terms and conditions of 133 | this License, without any additional terms or conditions. 134 | Notwithstanding the above, nothing herein shall supersede or modify 135 | the terms of any separate license agreement you may have executed 136 | with Licensor regarding such Contributions. 137 | 138 | 6. Trademarks. This License does not grant permission to use the trade 139 | names, trademarks, service marks, or product names of the Licensor, 140 | except as required for reasonable and customary use in describing the 141 | origin of the Work and reproducing the content of the NOTICE file. 142 | 143 | 7. Disclaimer of Warranty. Unless required by applicable law or 144 | agreed to in writing, Licensor provides the Work (and each 145 | Contributor provides its Contributions) on an "AS IS" BASIS, 146 | WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or 147 | implied, including, without limitation, any warranties or conditions 148 | of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A 149 | PARTICULAR PURPOSE. You are solely responsible for determining the 150 | appropriateness of using or redistributing the Work and assume any 151 | risks associated with Your exercise of permissions under this License. 152 | 153 | 8. Limitation of Liability. In no event and under no legal theory, 154 | whether in tort (including negligence), contract, or otherwise, 155 | unless required by applicable law (such as deliberate and grossly 156 | negligent acts) or agreed to in writing, shall any Contributor be 157 | liable to You for damages, including any direct, indirect, special, 158 | incidental, or consequential damages of any character arising as a 159 | result of this License or out of the use or inability to use the 160 | Work (including but not limited to damages for loss of goodwill, 161 | work stoppage, computer failure or malfunction, or any and all 162 | other commercial damages or losses), even if such Contributor 163 | has been advised of the possibility of such damages. 164 | 165 | 9. Accepting Warranty or Additional Liability. While redistributing 166 | the Work or Derivative Works thereof, You may choose to offer, 167 | and charge a fee for, acceptance of support, warranty, indemnity, 168 | or other liability obligations and/or rights consistent with this 169 | License. However, in accepting such obligations, You may act only 170 | on Your own behalf and on Your sole responsibility, not on behalf 171 | of any other Contributor, and only if You agree to indemnify, 172 | defend, and hold each Contributor harmless for any liability 173 | incurred by, or claims asserted against, such Contributor by reason 174 | of your accepting any such warranty or additional liability. 175 | 176 | END OF TERMS AND CONDITIONS 177 | 178 | APPENDIX: How to apply the Apache License to your work. 179 | 180 | To apply the Apache License to your work, attach the following 181 | boilerplate notice, with the fields enclosed by brackets "[]" 182 | replaced with your own identifying information. (Don't include 183 | the brackets!) The text should be enclosed in the appropriate 184 | comment syntax for the file format. We also recommend that a 185 | file or class name and description of purpose be included on the 186 | same "printed page" as the copyright notice for easier 187 | identification within third-party archives. 188 | 189 | Copyright [yyyy] [name of copyright owner] 190 | 191 | Licensed under the Apache License, Version 2.0 (the "License"); 192 | you may not use this file except in compliance with the License. 193 | You may obtain a copy of the License at 194 | 195 | http://www.apache.org/licenses/LICENSE-2.0 196 | 197 | Unless required by applicable law or agreed to in writing, software 198 | distributed under the License is distributed on an "AS IS" BASIS, 199 | WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. 200 | See the License for the specific language governing permissions and 201 | limitations under the License. 202 | -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 | # DevOps Interview Preparation Guide 2 | 3 | ## Introduction 4 | 5 | Welcome to the DevOps Interview Preparation repository! This repository aims to provide aspiring DevOps and cloud engineers with a valuable resource to prepare for interviews and gain insights from real interview experiences shared by the community. 6 | 7 | ## Goal and Aim 8 | 9 | The goal of this repository is to create a common point of reference where DevOps aspirants can find interview questions, experiences, and scenario-based questions and answers from various companies and roles. We aim to foster a supportive and engaging community that helps individuals in their journey to becoming successful DevOps professionals. 10 | 11 | 12 | ## Folder Structure 13 | 14 | The repository is organized into folders based on different DevOps categories: 15 | 16 | - DevOps with AWS 17 | - DevOps with Azure 18 | - DevOps with GCP 19 | - DevOps without Cloud 20 | - DevOps with SRE 21 | 22 | ## Code of Conduct 23 | 24 | To maintain a friendly and inclusive environment, we have established a [Code of Conduct](CODE_OF_CONDUCT.md). We expect all contributors and users to adhere to these guidelines while participating in discussions and contributing to the repository. 25 | 26 | ## How to Contribute 27 | 28 | We encourage contributions from everyone in the DevOps community. If you've recently had a DevOps interview, we invite you to share your interview experience and questions with others. To contribute, follow these simple steps: 29 | 30 | 1. Fork this repository to your GitHub account. 31 | 32 | 2. Clone the forked repository to your local machine. 33 | 34 | 3. Create a new Markdown file in the appropriate category folder that best represents your interview (e.g., DevOps with AWS, DevOps with Azure, DevOps with GCP, DevOps without Cloud, or DevOps with SRE). 35 | 36 | 4. Use the provided PR template to structure your interview experience. Be as detailed as possible to provide valuable insights to others. 37 | 38 | 5. Commit your changes and create a Pull Request (PR) to this repository. 39 | 40 | 6. Our team will review your PR, and upon approval, your interview experience will be added to the repository, benefiting the DevOps community. 41 | 42 | For complete details about contributing, please refer [CONTRIBUTING.md](CONTRIBUTING.md) 43 | 44 | 45 | ## License 46 | 47 | This repository is licensed under the [Apache License](LICENSE). By contributing to this repository, you agree to license your contributions under the same license. 48 | 49 | ## Community and Feedback 50 | 51 | We encourage community engagement through GitHub Issues and Discussions. Feel free to ask questions, provide feedback, or suggest improvements. Let's collaborate and make this repository a valuable resource for the DevOps community! 52 | 53 | Happy contributing and good luck with your DevOps journey! 54 | -------------------------------------------------------------------------------- /devops_with_aws/README.md: -------------------------------------------------------------------------------- 1 | # DevOps with AWS 2 | 3 | To share your interview experience and questions, Add a new file with name in the below format. 4 | 5 | -- 6 | 7 | company-name is optional. -------------------------------------------------------------------------------- /devops_with_azure/README.md: -------------------------------------------------------------------------------- 1 | # DevOps with Azure 2 | 3 | To share your interview experience and questions, Add a new file with name in the below format. 4 | 5 | -- 6 | 7 | company-name is optional. -------------------------------------------------------------------------------- /devops_with_gcp/README.md: -------------------------------------------------------------------------------- 1 | # DevOps with GCP 2 | 3 | To share your interview experience and questions, Add a new file with name in the below format. 4 | 5 | -- 6 | 7 | company-name is optional. -------------------------------------------------------------------------------- /devops_with_sre/5+yrs_DevopswithSRE.md: -------------------------------------------------------------------------------- 1 | I have recently attended an interview for SRE Engineer (Face to Face), They majorly focused on below areas 2 | 3 | ## Monitoring: 4 | Prometheus,Grafana & Splunk 5 | 6 | How do you Scrape the application data using Prometheus 7 | They shared the Grafana Dashboard, asked me few scenario based questions like 8 | what is your obeservations on this dashboard 9 | is there anything you can see critical based on dashboard 10 | is application health ok 11 | how do you create alerts based on this dashboard> 12 | 13 | When do you use Splunk, in what scenarions you have used splunk 14 | 15 | 16 | ## Jenkins 17 | 18 | Explain about differet types of piplines 19 | how do you schedule a pipeline 20 | how do you ensure pipeline keeps running though there is an error in one stage 21 | 22 | ## Docker 23 | 24 | Difference between CMD & ENTRYPOINT 25 | Multistage Docker file 26 | 27 | ## SRE: 28 | How do you achieve 100% SLA for an application 29 | What are the metrics you consider while setting up SLA,SLO 30 | 31 | -------------------------------------------------------------------------------- /devops_with_sre/README.md: -------------------------------------------------------------------------------- 1 | # DevOps with SRE 2 | 3 | To share your interview experience and questions, Add a new file with name in the below format. 4 | 5 | -- 6 | 7 | company-name is optional. -------------------------------------------------------------------------------- /devops_without_cloud/README.md: -------------------------------------------------------------------------------- 1 | # DevOps without Cloud 2 | 3 | To share your interview experience and questions, Add a new file with name in the below format. 4 | 5 | -- 6 | 7 | company-name is optional. -------------------------------------------------------------------------------- /devops_without_cloud/questions.txt: -------------------------------------------------------------------------------- 1 | Ansible jinja template 2 | Jenkins pipeline linking with SonarQube 3 | SonarQube setup 4 | Groovy script in Jenkins and running it 5 | Ansible 6 | EC2 Instance creation using Ansible 7 | Recommending the right tools to the client 8 | Dockerfile usage for creating custom images 9 | Process of DevOps 10 | Kubernetes setup 11 | Helm chart 12 | Cloud infrastructure 13 | Install Kubernetes 14 | Kubernetes cluster setup 15 | Web-based deployment in JFrog Tomcat Artifactory 16 | 17 | Prometheus, Grafana, Logging: 18 | 19 | Logging in Prometheus and Grafana 20 | 21 | Git and Version Control: 22 | 23 | Git stash 24 | Merging all commits to the main branch via one command 25 | Git clone and git remote 26 | Git stash drop 27 | List of files changes in a particular commit 28 | Git diff free -or # 29 | How to fix a broken commit 30 | How to check the history of merged branches 31 | 32 | Jenkins and CI/CD: 33 | 34 | How to Run Jenkins 35 | Automated tests in Jenkins 36 | Pipeline failure and how to deal with it 37 | Agent Directive in Jenkins 38 | Restart Jenkins manually 39 | Types of Pipelines in Jenkins 40 | If you don't mention an agent in a scripted pipeline, what will happen to the job? 41 | How to execute declarative pipeline 42 | Groovy Sandbox use 43 | 44 | Docker and Containerization: 45 | 46 | Docker swarm 47 | Docker namespace 48 | Base image changing and committing to form a new image 49 | Docker system 50 | Can a container restart by itself? 51 | How to start a container every time we log in 52 | Can you delete a paused container? 53 | 54 | Kubernetes: 55 | 56 | Kubernetes architecture 57 | What is Kube proxy 58 | Basic elements in Kubernetes 59 | How do you check the log of pods for troubleshooting purposes? 60 | Kube Proxy is down. What will be the effect? 61 | Types of Services in Kubernetes 62 | Controller function in Kubernetes 63 | Persistent volume 64 | Stateful set 65 | Headless service 66 | 67 | AWS and Cloud Infrastructure: 68 | 69 | Merging my corporate data center to AWS 70 | Private IP Address in VPC 71 | Subnets in AWS 72 | Best practices of EC2 Instances 73 | EC2 failure-prone: which kind of instance to build 74 | EC2 -create -group securitygroup: What does this command do? 75 | Horizontal auto-scaling 76 | Removing pods 77 | Removing nodes 78 | User base in India and the US: where should the data be stored? 79 | Lost the private key, how will you get it back? 80 | Security group in AWS 81 | 82 | Linux and System Administration: 83 | 84 | Soft and Hard link difference 85 | Significance or use of inode 86 | How to check files older than 20 days 87 | How to check open ports in Linux 88 | Check the total number of inodes 89 | What does the df command do? 90 | What are the types of files in Linux? 91 | How to check open ports 92 | Default Network types in Docker - Have you heard about bridge host? 93 | How to check container logs 94 | How to check open ports 95 | Docker port command 96 | Docker system prune 97 | 98 | Miscellaneous: 99 | 100 | How do you define the pipeline? 101 | Which pipeline do you use: Scripted or declarative? 102 | Are you using JFrog for Artifactory storage? 103 | How do you create the deployment? 104 | How do you check if the previous command is successful or not? 105 | I am executing some command, how will I know if the command I executed is successful or not? 106 | What is etcd's purpose? 107 | While executing a bash script, I am passing F1.sh 1 2 3 4 5. Within the script, I want to read the parameters. 108 | How Prometheus works and what are the key components in Prometheus? 109 | How do you take your jar file from Artifactory? 110 | How do you deploy the application? What is the purpose? Step by step deployment. --------------------------------------------------------------------------------