Upload questions.csv
Browse files- questions.csv +41 -41
questions.csv
CHANGED
@@ -3,236 +3,236 @@
|
|
3 |
- a. Network policy enforcement
|
4 |
- b. Visibility into traffic at L3/L4 and L7
|
5 |
- c. Networking between Kubernetes pods
|
6 |
-
- d. Kubernetes secrets management"
|
7 |
"What is the name of the Cilium component that provides visibility into network traffic?
|
8 |
|
9 |
- a. Hubble
|
10 |
- b. Hobble
|
11 |
-
- c. Grafana"
|
12 |
"Which of these are characteristics of eBPF?
|
13 |
- a. It allows dynamic changes to the kernel
|
14 |
- b. It can be used to drop network packets that are forbidden by the network policy
|
15 |
-
- c. It enables high-performance networking with security and observability built-in"
|
16 |
"What are the different tools for installing Cilium components into a Kubernetes cluster?
|
17 |
**Select all that apply.**
|
18 |
|
19 |
- a. Helm
|
20 |
- b. The Cilium CLI
|
21 |
-
- c. Curl"
|
22 |
"A Cilium agent runs on every node in a Kubernetes cluster.
|
23 |
|
24 |
**True/False**
|
25 |
|
26 |
- a. True
|
27 |
-
- b. False"
|
28 |
"How many instances of the Hubble Relay run on each cluster?
|
29 |
|
30 |
- a. One per node
|
31 |
- b. One per pod
|
32 |
-
- c. One per cluster"
|
33 |
"What is the Cilium CLI command for checking that connectivity and policy enforcement is working correctly?
|
34 |
|
35 |
- a. kubectl connectivity test
|
36 |
- b. cilium connectivity test
|
37 |
-
- c. cilium policy test"
|
38 |
"Which network policy resource type does Cilium support?
|
39 |
|
40 |
- a. Standard Kubernetes NetworkPolicy
|
41 |
- b. CiliumNetworkPolicy
|
42 |
- c. CiliumClusterNetworkPolicy
|
43 |
-
- d. All of the above"
|
44 |
"It’s possible to export Layer 3 network policy using the networkpolicy.io’s visual policy editor as CiliumNetworkPolicy YAML files.
|
45 |
|
46 |
**True/False**
|
47 |
|
48 |
- a. True
|
49 |
-
- b. False"
|
50 |
"Which of the following is a true statement?
|
51 |
**Select all that apply.**
|
52 |
|
53 |
- a. The CiliumNetworkPolicy resource supports service name-based egress policy for internal cluster communications
|
54 |
- b. The standard Kubernetes NetworkPolicy resource supports L7 HTTP protocol rules limiting access to specific HTTP paths
|
55 |
-
- c. The CiliumNetworkPolicy resource supports both TCP and ICMP egress policy"
|
56 |
"Hubble flows include packet dumps.
|
57 |
**True/False**
|
58 |
|
59 |
- a. True
|
60 |
-
- b. False"
|
61 |
"You can filter by packet verdict in the Hubble UI service map.
|
62 |
**True/False**
|
63 |
|
64 |
- a. True
|
65 |
-
- b. False"
|
66 |
"Which of the following statements are **TRUE**?
|
67 |
**Select all that apply.**
|
68 |
|
69 |
- a. The Hubble Relay service provides cluster-wide network observability
|
70 |
- b. It's not possible to filter flows by namespace using the Hubble CLI tool
|
71 |
- c. Hubble flows include information about traffic direction
|
72 |
-
- d. Hubble is optional and needs to be enabled when installing Cilium"
|
73 |
"After Istio is installed on a Kubernetes cluster, any workloads deployed to service mesh are automatically accompanied with sidecars.
|
74 |
|
75 |
**True/False**
|
76 |
a. True
|
77 |
-
b. False"
|
78 |
"How is outbound traffic from a service routed to the sidecar?
|
79 |
|
80 |
- a. Programmers must revise their code to specifically target the proxy at localhost:15000.
|
81 |
- b. iptables rules within a Pod are applied to transparently effect this change.
|
82 |
-
- c. Operators must use the istioctl rewire-pod command to transparently effect this change."
|
83 |
"What identity framework does Istio base its application of workload identity?
|
84 |
|
85 |
- a. Security Assertion Markup Language (SAML)
|
86 |
- b. Open ID Connect (OIDC)
|
87 |
- c. Secure Production Identity Framework for Everyone (SPIFFE)
|
88 |
-
- d. JSON Web Tokens (JWT)"
|
89 |
"The Istio framework offers the choice between manually configuring Envoy sidecars and letting the Istio control plane manage Envoy.
|
90 |
|
91 |
**True/False**
|
92 |
|
93 |
- a. True
|
94 |
-
- b. False"
|
95 |
"The _demo_ configuration profile installs only the Istio control plane and the ingress gateway.
|
96 |
|
97 |
**True/False**
|
98 |
|
99 |
- a. True
|
100 |
-
- b. False"
|
101 |
"Helm installation consists of the following Helm charts:
|
102 |
|
103 |
- a. base, istiod, gateway
|
104 |
- b. istiod, ingress-gateway, egress-gateway
|
105 |
- c. istiod, gateways
|
106 |
-
- d. base, control-plane, gateway"
|
107 |
"In which section of the IstioOperator resource can we configure Kubernetes resource limits and requests:
|
108 |
|
109 |
- a. global
|
110 |
- b. meshConfig
|
111 |
- c. components
|
112 |
-
- d. We cannot configure limits and requests."
|
113 |
"Observability is a concept that is broader than traditional monitoring.
|
114 |
|
115 |
**True/False**
|
116 |
|
117 |
- a. True
|
118 |
-
- b. False"
|
119 |
"What are the three main components of modern observability?
|
120 |
|
121 |
- a. Graphs, charts, and metrics
|
122 |
- b. Logs, metrics, and traces
|
123 |
-
- c. Logs, Garbage collection, and Threads"
|
124 |
"With Istio, developers must expose their metrics to Prometheus directly from inside their applications.
|
125 |
|
126 |
**True/False**
|
127 |
|
128 |
- a. True
|
129 |
-
- b. False"
|
130 |
"Envoy sidecars can initiate and propagate B3 trace headers without any assistance from the running applications.
|
131 |
|
132 |
**True/False**
|
133 |
|
134 |
- a. True
|
135 |
-
- b. False"
|
136 |
"Istio, Prometheus, Grafana, Jaeger, and Kiali are all open source projects.
|
137 |
|
138 |
**True/False**
|
139 |
|
140 |
- a. True
|
141 |
-
- b. False"
|
142 |
"The ingress and egress gateways in Istio are single instances of an Envoy proxy.
|
143 |
|
144 |
**True/False**
|
145 |
|
146 |
- a. True
|
147 |
-
- b. False"
|
148 |
"In which resource can we configure outlier detection and load balancer settings?
|
149 |
|
150 |
- a. VirtualService
|
151 |
- b. DestinationRule
|
152 |
- c. Gateway
|
153 |
-
- d. ServiceEntry"
|
154 |
"The traffic can be matched on multiple properties and to match the values, we can only use regular expressions.
|
155 |
|
156 |
**True/False**
|
157 |
|
158 |
- a. True
|
159 |
-
- b. False"
|
160 |
"When Envoy retries a failed request, the endpoint that caused the retry is no longer in the load balancing pool.
|
161 |
|
162 |
**True/False**
|
163 |
|
164 |
- a. True
|
165 |
-
- b. False"
|
166 |
"Authorization is all about the principal.
|
167 |
|
168 |
**True/False**
|
169 |
|
170 |
- a. True
|
171 |
-
- b. False"
|
172 |
"Which one of the following resources can we use to configure mTLS for inbound traffic?
|
173 |
|
174 |
- a. PeerAuthentication
|
175 |
- b. DestinationRule
|
176 |
- c. VirtualService
|
177 |
-
- d. AuthorizationPolicy"
|
178 |
"What do Kubernetes pods use as their identity during runtime?
|
179 |
|
180 |
- a. Kubernetes secrets
|
181 |
- b. Service accounts
|
182 |
- c. JWT tokens
|
183 |
-
- d. Bearer tokens"
|
184 |
"The clusters section in the Envoy configuration defines how the traffic is sent to the upstream service.
|
185 |
|
186 |
**True/False**
|
187 |
|
188 |
- a. True
|
189 |
-
- b. False"
|
190 |
"Where in the Envoy configuration is the router filter defined?
|
191 |
|
192 |
- a. Within the HTTP connection manager filter
|
193 |
- b. Within the routes
|
194 |
- c. Within the listener filter
|
195 |
-
- d. Within the clusters"
|
196 |
"We can apply the Envoy configuration patch only at the namespace level.
|
197 |
|
198 |
**True/False**
|
199 |
|
200 |
- a. True
|
201 |
-
- b. False"
|
202 |
"When using the **oci://** scheme in the WasmPlugin resource, the Istio agent downloads compiled Wasm plugins from an OCI-compliant registry.
|
203 |
|
204 |
**True/False**
|
205 |
|
206 |
- a. True
|
207 |
-
- b. False"
|
208 |
"By default, Istio watches all workloads in all namespaces and updates sidecar proxy configuration whenever new workloads are added, removed, or updated.
|
209 |
|
210 |
**True/False**
|
211 |
|
212 |
- a. True
|
213 |
-
- b. False"
|
214 |
"Which Istio resource can be used to provide the details about the namespace, labels, and service account to the VM workload?
|
215 |
|
216 |
- a. WorkloadEntry
|
217 |
- b. VirtualService
|
218 |
- c. ServiceEntry
|
219 |
-
- d. ServiceEntry"
|
220 |
"The primary cluster in the multi-cluster deployment scenario runs the control plane.
|
221 |
|
222 |
**True/False**
|
223 |
|
224 |
- a. True
|
225 |
-
- b. False"
|
226 |
"What is the east-west gateway used for?
|
227 |
|
228 |
- a. Service communication within a single Kubernetes cluster
|
229 |
- b. Communication between Istio control plane and services within one cluster
|
230 |
- c. Communication between workloads in the cluster and VMs
|
231 |
-
- d. Communication between workloads in the cluster and VMs, VM sidecars, and Istio’s control plane"
|
232 |
"The process of deploying an Envoy proxy alongside each workload is called:
|
233 |
|
234 |
- a. proxy bundling
|
235 |
- b. sidecar injection
|
236 |
- c. sidecar bundling
|
237 |
-
- d. proxy injection"
|
238 |
|
|
|
3 |
- a. Network policy enforcement
|
4 |
- b. Visibility into traffic at L3/L4 and L7
|
5 |
- c. Networking between Kubernetes pods
|
6 |
+
- d. Kubernetes secrets management","Answer: a, b, c"
|
7 |
"What is the name of the Cilium component that provides visibility into network traffic?
|
8 |
|
9 |
- a. Hubble
|
10 |
- b. Hobble
|
11 |
+
- c. Grafana", "Answer: a"
|
12 |
"Which of these are characteristics of eBPF?
|
13 |
- a. It allows dynamic changes to the kernel
|
14 |
- b. It can be used to drop network packets that are forbidden by the network policy
|
15 |
+
- c. It enables high-performance networking with security and observability built-in", "Answer: d"
|
16 |
"What are the different tools for installing Cilium components into a Kubernetes cluster?
|
17 |
**Select all that apply.**
|
18 |
|
19 |
- a. Helm
|
20 |
- b. The Cilium CLI
|
21 |
+
- c. Curl", "Answer: a, b"
|
22 |
"A Cilium agent runs on every node in a Kubernetes cluster.
|
23 |
|
24 |
**True/False**
|
25 |
|
26 |
- a. True
|
27 |
+
- b. False", "Answer: a"
|
28 |
"How many instances of the Hubble Relay run on each cluster?
|
29 |
|
30 |
- a. One per node
|
31 |
- b. One per pod
|
32 |
+
- c. One per cluster", "Answer: c"
|
33 |
"What is the Cilium CLI command for checking that connectivity and policy enforcement is working correctly?
|
34 |
|
35 |
- a. kubectl connectivity test
|
36 |
- b. cilium connectivity test
|
37 |
+
- c. cilium policy test", "Answer: b"
|
38 |
"Which network policy resource type does Cilium support?
|
39 |
|
40 |
- a. Standard Kubernetes NetworkPolicy
|
41 |
- b. CiliumNetworkPolicy
|
42 |
- c. CiliumClusterNetworkPolicy
|
43 |
+
- d. All of the above", "Answer: d"
|
44 |
"It’s possible to export Layer 3 network policy using the networkpolicy.io’s visual policy editor as CiliumNetworkPolicy YAML files.
|
45 |
|
46 |
**True/False**
|
47 |
|
48 |
- a. True
|
49 |
+
- b. False", "Answer: a"
|
50 |
"Which of the following is a true statement?
|
51 |
**Select all that apply.**
|
52 |
|
53 |
- a. The CiliumNetworkPolicy resource supports service name-based egress policy for internal cluster communications
|
54 |
- b. The standard Kubernetes NetworkPolicy resource supports L7 HTTP protocol rules limiting access to specific HTTP paths
|
55 |
+
- c. The CiliumNetworkPolicy resource supports both TCP and ICMP egress policy", "Answer: a"
|
56 |
"Hubble flows include packet dumps.
|
57 |
**True/False**
|
58 |
|
59 |
- a. True
|
60 |
+
- b. False" , "Answer: b"
|
61 |
"You can filter by packet verdict in the Hubble UI service map.
|
62 |
**True/False**
|
63 |
|
64 |
- a. True
|
65 |
+
- b. False", "Answer: a"
|
66 |
"Which of the following statements are **TRUE**?
|
67 |
**Select all that apply.**
|
68 |
|
69 |
- a. The Hubble Relay service provides cluster-wide network observability
|
70 |
- b. It's not possible to filter flows by namespace using the Hubble CLI tool
|
71 |
- c. Hubble flows include information about traffic direction
|
72 |
+
- d. Hubble is optional and needs to be enabled when installing Cilium", "Answer: a, c, d"
|
73 |
"After Istio is installed on a Kubernetes cluster, any workloads deployed to service mesh are automatically accompanied with sidecars.
|
74 |
|
75 |
**True/False**
|
76 |
a. True
|
77 |
+
b. False", "Answer: b."
|
78 |
"How is outbound traffic from a service routed to the sidecar?
|
79 |
|
80 |
- a. Programmers must revise their code to specifically target the proxy at localhost:15000.
|
81 |
- b. iptables rules within a Pod are applied to transparently effect this change.
|
82 |
+
- c. Operators must use the istioctl rewire-pod command to transparently effect this change.", "Answer: b."
|
83 |
"What identity framework does Istio base its application of workload identity?
|
84 |
|
85 |
- a. Security Assertion Markup Language (SAML)
|
86 |
- b. Open ID Connect (OIDC)
|
87 |
- c. Secure Production Identity Framework for Everyone (SPIFFE)
|
88 |
+
- d. JSON Web Tokens (JWT)", "Answer: c."
|
89 |
"The Istio framework offers the choice between manually configuring Envoy sidecars and letting the Istio control plane manage Envoy.
|
90 |
|
91 |
**True/False**
|
92 |
|
93 |
- a. True
|
94 |
+
- b. False", "Answer: b."
|
95 |
"The _demo_ configuration profile installs only the Istio control plane and the ingress gateway.
|
96 |
|
97 |
**True/False**
|
98 |
|
99 |
- a. True
|
100 |
+
- b. False", "Answer: b."
|
101 |
"Helm installation consists of the following Helm charts:
|
102 |
|
103 |
- a. base, istiod, gateway
|
104 |
- b. istiod, ingress-gateway, egress-gateway
|
105 |
- c. istiod, gateways
|
106 |
+
- d. base, control-plane, gateway", "Answer: a."
|
107 |
"In which section of the IstioOperator resource can we configure Kubernetes resource limits and requests:
|
108 |
|
109 |
- a. global
|
110 |
- b. meshConfig
|
111 |
- c. components
|
112 |
+
- d. We cannot configure limits and requests.", "Answer: c."
|
113 |
"Observability is a concept that is broader than traditional monitoring.
|
114 |
|
115 |
**True/False**
|
116 |
|
117 |
- a. True
|
118 |
+
- b. False", "Answer: a."
|
119 |
"What are the three main components of modern observability?
|
120 |
|
121 |
- a. Graphs, charts, and metrics
|
122 |
- b. Logs, metrics, and traces
|
123 |
+
- c. Logs, Garbage collection, and Threads", "Answer: b."
|
124 |
"With Istio, developers must expose their metrics to Prometheus directly from inside their applications.
|
125 |
|
126 |
**True/False**
|
127 |
|
128 |
- a. True
|
129 |
+
- b. False", "Answer: b."
|
130 |
"Envoy sidecars can initiate and propagate B3 trace headers without any assistance from the running applications.
|
131 |
|
132 |
**True/False**
|
133 |
|
134 |
- a. True
|
135 |
+
- b. False", "Answer: b."
|
136 |
"Istio, Prometheus, Grafana, Jaeger, and Kiali are all open source projects.
|
137 |
|
138 |
**True/False**
|
139 |
|
140 |
- a. True
|
141 |
+
- b. False", "Answer: a."
|
142 |
"The ingress and egress gateways in Istio are single instances of an Envoy proxy.
|
143 |
|
144 |
**True/False**
|
145 |
|
146 |
- a. True
|
147 |
+
- b. False", "Answer: a."
|
148 |
"In which resource can we configure outlier detection and load balancer settings?
|
149 |
|
150 |
- a. VirtualService
|
151 |
- b. DestinationRule
|
152 |
- c. Gateway
|
153 |
+
- d. ServiceEntry", "Answer: b."
|
154 |
"The traffic can be matched on multiple properties and to match the values, we can only use regular expressions.
|
155 |
|
156 |
**True/False**
|
157 |
|
158 |
- a. True
|
159 |
+
- b. False", "Answer: b."
|
160 |
"When Envoy retries a failed request, the endpoint that caused the retry is no longer in the load balancing pool.
|
161 |
|
162 |
**True/False**
|
163 |
|
164 |
- a. True
|
165 |
+
- b. False", "Answer: a."
|
166 |
"Authorization is all about the principal.
|
167 |
|
168 |
**True/False**
|
169 |
|
170 |
- a. True
|
171 |
+
- b. False", "Answer: b."
|
172 |
"Which one of the following resources can we use to configure mTLS for inbound traffic?
|
173 |
|
174 |
- a. PeerAuthentication
|
175 |
- b. DestinationRule
|
176 |
- c. VirtualService
|
177 |
+
- d. AuthorizationPolicy", "Answer: a."
|
178 |
"What do Kubernetes pods use as their identity during runtime?
|
179 |
|
180 |
- a. Kubernetes secrets
|
181 |
- b. Service accounts
|
182 |
- c. JWT tokens
|
183 |
+
- d. Bearer tokens", "Answer: b."
|
184 |
"The clusters section in the Envoy configuration defines how the traffic is sent to the upstream service.
|
185 |
|
186 |
**True/False**
|
187 |
|
188 |
- a. True
|
189 |
+
- b. False", "Answer: a."
|
190 |
"Where in the Envoy configuration is the router filter defined?
|
191 |
|
192 |
- a. Within the HTTP connection manager filter
|
193 |
- b. Within the routes
|
194 |
- c. Within the listener filter
|
195 |
+
- d. Within the clusters", "Answer: a."
|
196 |
"We can apply the Envoy configuration patch only at the namespace level.
|
197 |
|
198 |
**True/False**
|
199 |
|
200 |
- a. True
|
201 |
+
- b. False", "Answer: b."
|
202 |
"When using the **oci://** scheme in the WasmPlugin resource, the Istio agent downloads compiled Wasm plugins from an OCI-compliant registry.
|
203 |
|
204 |
**True/False**
|
205 |
|
206 |
- a. True
|
207 |
+
- b. False", "Answer: a."
|
208 |
"By default, Istio watches all workloads in all namespaces and updates sidecar proxy configuration whenever new workloads are added, removed, or updated.
|
209 |
|
210 |
**True/False**
|
211 |
|
212 |
- a. True
|
213 |
+
- b. False", "Answer: a."
|
214 |
"Which Istio resource can be used to provide the details about the namespace, labels, and service account to the VM workload?
|
215 |
|
216 |
- a. WorkloadEntry
|
217 |
- b. VirtualService
|
218 |
- c. ServiceEntry
|
219 |
+
- d. ServiceEntry", "Answer: a."
|
220 |
"The primary cluster in the multi-cluster deployment scenario runs the control plane.
|
221 |
|
222 |
**True/False**
|
223 |
|
224 |
- a. True
|
225 |
+
- b. False", "Answer: a."
|
226 |
"What is the east-west gateway used for?
|
227 |
|
228 |
- a. Service communication within a single Kubernetes cluster
|
229 |
- b. Communication between Istio control plane and services within one cluster
|
230 |
- c. Communication between workloads in the cluster and VMs
|
231 |
+
- d. Communication between workloads in the cluster and VMs, VM sidecars, and Istio’s control plane", "Answer: d."
|
232 |
"The process of deploying an Envoy proxy alongside each workload is called:
|
233 |
|
234 |
- a. proxy bundling
|
235 |
- b. sidecar injection
|
236 |
- c. sidecar bundling
|
237 |
+
- d. proxy injection", "Answer: d."
|
238 |
|