mirror of
https://github.com/bregman-arie/devops-exercises.git
synced 2026-02-04 15:49:11 +00:00
Fix various typos in topics/certificates (#10275)
This commit is contained in:
parent
895ac0f155
commit
9318b9bd68
@ -165,8 +165,8 @@ Read more about instance types [here](https://docs.aws.amazon.com/AWSEC2/latest/
|
||||
<details>
|
||||
<summary>True or False? The following are instance types available for a user in AWS:
|
||||
|
||||
* Compute optimizied
|
||||
* Network optimizied
|
||||
* Compute optimized
|
||||
* Network optimized
|
||||
* Web optimized</summary><br><b>
|
||||
|
||||
False. From the above list only compute optimized is available.
|
||||
|
||||
@ -188,8 +188,8 @@ Read more about instance types [here](https://docs.aws.amazon.com/AWSEC2/latest/
|
||||
<details>
|
||||
<summary>True or False? The following are instance types available for a user in AWS:
|
||||
|
||||
* Compute optimizied
|
||||
* Network optimizied
|
||||
* Compute optimized
|
||||
* Network optimized
|
||||
* Web optimized</summary><br><b>
|
||||
|
||||
False. From the above list only compute optimized is available.
|
||||
|
||||
@ -947,7 +947,7 @@ Launch configuration is a legacy form of Launch Template that must be recreated
|
||||
In addition, launch template has the clear benefits of:
|
||||
* Provision both On-Demand and Spot instances
|
||||
* supporting multiple versions
|
||||
* support creating parameters subsets (used for re-use and inheritance)
|
||||
* support creating parameters subsets (used for reuse and inheritance)
|
||||
</b></details>
|
||||
|
||||
#### ENI
|
||||
|
||||
@ -2739,7 +2739,7 @@ Istio is an open source service mesh that helps organizations run distributed, m
|
||||
<details>
|
||||
<summary>Name two controllers you are familiar with</summary><br><b>
|
||||
|
||||
1. Node Contorller: manages the nodes of a cluster. Among other things, the controller is responsible for monitoring nodes' health - if the node is suddenly unreachable it will evacuate all the pods running on it and will mark the node status accordingly.
|
||||
1. Node Controller: manages the nodes of a cluster. Among other things, the controller is responsible for monitoring nodes' health - if the node is suddenly unreachable it will evacuate all the pods running on it and will mark the node status accordingly.
|
||||
2. Replication Controller - monitors the status of pod replicas based on what should be running. It makes sure the number of pods that should be running is actually running
|
||||
</b></details>
|
||||
|
||||
|
||||
@ -1649,7 +1649,7 @@ There are 2 configuration files, which stores users information
|
||||
<details>
|
||||
<summary>Which file stores users passwords? Is it visible for everyone?</summary><br>
|
||||
|
||||
`/etc/shadow` file holds the passwords of the users in encryted format. NO, it is only visible to the `root` user
|
||||
`/etc/shadow` file holds the passwords of the users in encrypted format. NO, it is only visible to the `root` user
|
||||
</details>
|
||||
|
||||
<details>
|
||||
|
||||
@ -42,7 +42,7 @@ The principle of least privilege refers to the practice of providing minimal per
|
||||
* Subject name
|
||||
* Subject Public Key info
|
||||
|
||||
Every certificates must be signed by a trusted authority, a certificate chain is a concatenation of mutilple certificates signed by a more trusted authority from the one delivered by the website to the root Certificate Authority (CA). The root Certificate Authority is the top most trusted authority and every browsers embark their certificate natively.
|
||||
Every certificates must be signed by a trusted authority, a certificate chain is a concatenation of multiple certificates signed by a more trusted authority from the one delivered by the website to the root Certificate Authority (CA). The root Certificate Authority is the top most trusted authority and every browsers embark their certificate natively.
|
||||
|
||||
</b></details>
|
||||
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user