Add a couple of questions
This commit is contained in:
parent
a278bd90b2
commit
d156460b4c
93
README.md
93
README.md
@ -71,6 +71,7 @@
|
||||
<td align="center"><a href="#docker"><img src="images/docker.png" width="70px;" height="75px;" alt="Docker"/><br /><b>Docker</b></a></td>
|
||||
<td align="center"><a href="#sql"><img src="images/sql.png" width="75px;" height="75px;" alt="sql"/><br /><b>SQL</b></a></td>
|
||||
<td align="center"><a href="#openshift"><img src="images/openshift.png" width="75px;" height="75px;" alt="OpenShift"/><br /><b>OpenShift</b></a></td>
|
||||
<td align="center"><a href="#storage"><img src="images/storage.png" width="75px;" height="75px;" alt="Storage"/><br /><b>Storage</b></a></td>
|
||||
<td align="center"><a href="#HR"><img src="images/HR.png" width="110px;" height="75px;" alt="HR"/><br /><b>HR</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>
|
||||
@ -1967,6 +1968,14 @@ A three-way handshake is primarily used to create a TCP socket connection. It wo
|
||||
- The client node receives the SYN/ACK from the server and responds with an ACK packet.
|
||||
</b></details>
|
||||
|
||||
<details>
|
||||
<summary>What is round-trip delay or round-trip time?</summary><br><b>
|
||||
|
||||
From [wikipedia](https://en.wikipedia.org/wiki/Round-trip_delay): "the length of time it takes for a signal to be sent plus the length of time it takes for an acknowledgement of that signal to be received"
|
||||
|
||||
Bonus question: what is the RTT of LAN?
|
||||
</b></details>
|
||||
|
||||
<details>
|
||||
<summary>How does SSL handshake work?</summary><br><b>
|
||||
</b></details>
|
||||
@ -6709,6 +6718,34 @@ as key-value pair, document-oriented, etc.
|
||||
<summary>Explain what is Downward API</summary><br><b>
|
||||
</b></details>
|
||||
|
||||
## Storage
|
||||
|
||||
<details>
|
||||
<summary>What is a storage device? What storage devices are there?</summary><br><b>
|
||||
|
||||
* Hard Disks
|
||||
* SSD
|
||||
* USB
|
||||
* Magnetic Tape
|
||||
</b></details>
|
||||
|
||||
<details>
|
||||
<summary>Explain the following:
|
||||
|
||||
* Block Storage
|
||||
* Object Storage
|
||||
* File Storage</summary><br><b>
|
||||
</b></details>
|
||||
|
||||
<details>
|
||||
<summary>What is Random Seek Time?</summary><br><b>
|
||||
|
||||
The time it takes for a disk to reach the place where the data is located and read a single block/sector.
|
||||
|
||||
Bones question: What is the random seek time in SSD and Magnetic Disk?
|
||||
Answer: Magnetic is about 10ms and SSD is somewhere between 0.08 and 0.16ms
|
||||
</b></details>
|
||||
|
||||
## Shell Scripting
|
||||
|
||||
<details>
|
||||
@ -7093,7 +7130,7 @@ An availability set is a logical grouping of VMs that allows Azure to understand
|
||||
<summary>Explain Azure managed disks</summary><br><b>
|
||||
</b></details>
|
||||
|
||||
#### Network
|
||||
#### Azure Network
|
||||
|
||||
<details>
|
||||
<summary>What's an Azure region?</summary><br><b>
|
||||
@ -7103,7 +7140,7 @@ An availability set is a logical grouping of VMs that allows Azure to understand
|
||||
<summary>What is the N-tier architecture?</summary><br><b>
|
||||
</b></details>
|
||||
|
||||
#### Storage
|
||||
#### Azure Storage
|
||||
|
||||
<details>
|
||||
<summary>What storage options Azure supports?</summary><br><b>
|
||||
@ -8720,10 +8757,6 @@ These are not DevOps related questions as you probably noticed, but since they a
|
||||
<summary>What was most challenging part in the project you worked on?</summary><br><b>
|
||||
</b></details>
|
||||
|
||||
<details>
|
||||
<summary>Why do you want to work here?</summary><br><b>
|
||||
</b></details>
|
||||
|
||||
<details>
|
||||
<summary>How did you hear about us?</summary><br><b>
|
||||
|
||||
@ -8809,6 +8842,24 @@ You can use and elaborate on one or all of the following:
|
||||
* Creativity (be able to support it with some actual examples)
|
||||
</b></details>
|
||||
|
||||
#### Pointless Questions
|
||||
|
||||
<details>
|
||||
<summary>Why do you want to work here?</summary><br><b>
|
||||
</b></details>
|
||||
|
||||
<details>
|
||||
<summary>Why are you looking to leave your current place?</summary><br><b>
|
||||
</b></details>
|
||||
|
||||
<details>
|
||||
<summary>What are your strengths and weaknesses?</summary><br><b>
|
||||
</b></details>
|
||||
|
||||
<details>
|
||||
<summary>Where do you see yourself in five years?</summary><br><b>
|
||||
</b></details>
|
||||
|
||||
#### Team Lead
|
||||
|
||||
<details>
|
||||
@ -9042,6 +9093,14 @@ Bonus: extract the last word of each line
|
||||
[This article](https://www.redhat.com/en/topics/microservices/what-is-a-service-mesh) provides a great explanation.
|
||||
</b></details>
|
||||
|
||||
<details>
|
||||
<summary>Explain "Loose Coupling"</summary><br><b>
|
||||
</b></details>
|
||||
|
||||
<details>
|
||||
<summary>What is a message queue? When is it used?</summary><br><b>
|
||||
</b></details>
|
||||
|
||||
#### Scalability
|
||||
|
||||
<details>
|
||||
@ -9070,12 +9129,34 @@ High Availability - Being able to access a resource (in some use cases, using di
|
||||
Vertical Scaling is the process of adding resources to increase power of existing servers. For example, adding more CPUs, adding more RAM, etc.
|
||||
</b></details>
|
||||
|
||||
<details>
|
||||
<summary>What are the disadvantages of Vertical Scaling?</summary><br><b>
|
||||
|
||||
With vertical scaling alone, the component still remains a single point of failure.
|
||||
In addition, it has hardware limit where if you don't have more resources, you might not be able to scale vertically.
|
||||
</b></details>
|
||||
|
||||
<details>
|
||||
<summary>Explain Horizontal Scaling</summary><br><b>
|
||||
|
||||
Horizontal Scaling is the process of adding more resources that will be able handle requests as one unit
|
||||
</b></details>
|
||||
|
||||
<details>
|
||||
<summary>What is the disadvange of Horizontal Scaling? What is often required in order to perform Horizontal Scaling?</summary><br><b>
|
||||
|
||||
A load balancer. You can add more resources, but if you would like them to be part of the process, you have to serve them the requests/responses.
|
||||
Also, data inconsistency is a concern with horizontal scaling.
|
||||
</b></details>
|
||||
|
||||
<details>
|
||||
<summary>Explain Resiliency and what ways are there to make a system more resilient</summary><br><b>
|
||||
</b></details>
|
||||
|
||||
<details>
|
||||
<summary>Explain "Consistent Hashing"</summary><br><b>
|
||||
</b></details>
|
||||
|
||||
<details>
|
||||
<summary>How would you update each of the services in the following drawing without having app (foo.com) downtime?<br>
|
||||
<img src="images/design/cdn-no-downtime.png" width="300x;" height="400px;"/>
|
||||
|
@ -17,3 +17,4 @@ Testing logo by [Flatart](https://www.iconfinder.com/Flatart)<br>
|
||||
Google Cloud Plataform Logo created by <a href="https://about.google/">Google®</a><br>
|
||||
VirtualBox Logo created by <a href="http://www.iconarchive.com/artist/dakirby309.html">dAKirby309</a>, under the <a href="https://creativecommons.org/licenses/by-nc/4.0/">Creative Commons Attribution-Noncommercial 4.0 License</a>.
|
||||
Certificates logo by <a href="https://www.iconfinder.com/Flatart">Flatart</a><br>
|
||||
Storage icon by <a href="https://www.iconfinder.com/iconic_hub">Dinosoftlab</a><br>
|
||||
|
BIN
images/storage.png
Normal file
BIN
images/storage.png
Normal file
Binary file not shown.
After Width: | Height: | Size: 4.4 KiB |
Loading…
Reference in New Issue
Block a user