McAfee Secure

CNCF CKA Bundle

Exam Code: CKA

Exam Name Certified Kubernetes Administrator

Certification Provider: CNCF

Corresponding Certification: CKA

CNCF CKA Bundle $44.99
CKA Sample 1 CKA Sample 2 CKA Sample 3 CKA Sample 4 CKA Sample 5 CKA Sample 6 CKA Sample 7 CKA Sample 8 CKA Sample 9 CKA Sample 10

100% CNCF CKA Guaranteed Success With Testking Training Materials

Get Real CKA Exam Questions & Expert Verified Answers as Experienced on the Real Exam!

  • Questions & Answers

    CKA Questions & Answers

    58 Questions & Answers

    The ultimate exam preparation tool, Questions & Answers mirrors the actual CKA exam while allowing you to hone and measure every aspect of your test-taking ability.

  • CKA Video Course

    CKA Training Course

    138 Video Lectures

    CKA Video Course is developed by CNCF Professionals to help you pass the CKA exam.

    Description

    This course will improve your knowledge and skills required to pass Certified Kubernetes Administrator exam.
  • Study Guide

    CKA Study Guide

    268 PDF Pages

    Developed by industry experts, this 268-page guide spells out in painstaking detail all of the information you need to ace CKA exam.

Certified Kubernetes Administrator (CKA) Practice Tests

Satisfaction Guaranteed

Money Back Guarantee

Testking provides hassle-free money back guarantee with our products. That is because we have 100% trust in the abilities of our professional and experience product team, and our record is a proof of that.

99.6% PASS RATE
Total Cost: $194.97
Bundle Price: $149.98

Purchase Individually

  • Questions & Answers

    Questions & Answers

    58 Questions

    $124.99
  • CKA Video Course

    Training Course

    138 Video Lectures

    $39.99
  • Study Guide

    Study Guide

    268 PDF Pages

    $29.99

CNCF CKA Practice Test 37

Question 360

At Pinecrest logistics, in a sandbox Kubernetes cluster during a recovery tabletop exercise: An existing workload dispatch-api in namespace fulfillment requires a ConfigMap dispatch-config containing the nonsecret setting MODE=uat. Work only within the stated target and verify before declaring success. Which operational control most directly prevents this failure or configuration drift?

  1. Version nonsecret application settings and avoid putting credentials into ConfigMaps.
  2. Control privileged node labels and review availability before adding hard scheduling constraints.
  3. Track whether consumers use environment variables or mounted files when planning ConfigMap refreshes.
  4. Gate deployment promotion on observed rollout and readiness rather than API command exit alone.

Explanation

Correct Answer

A:

Version nonsecret application settings and avoid putting credentials into ConfigMaps. This reduces recurrence of the specific operational failure. It reinforces the action: Run kubectl -n fulfillment create configmap dispatch-config --from-literal=MODE=uat after checking whether it already exists. The relevant mechanism is: ConfigMaps hold ordinary configuration data; their existence does not automatically inject values into running Pods.

Incorrect Answers

B:

That safeguard is relevant to: Node selectors constrain scheduling to nodes whose labels match all specified key/value pairs; patching the Pod template triggers a rollout. The current failure instead follows from: ConfigMaps hold ordinary configuration data; their existence does not automatically inject values into running Pods. Its prevention measure is “Version nonsecret application settings and avoid putting credentials into ConfigMaps”.

C:

This routine guards against another mechanism: Environment variables are copied into new container processes from ConfigMap values; existing running processes need replacement to pick up changes. The recurring exposure in the current case is: ConfigMaps hold ordinary configuration data; their existence does not automatically inject values into running Pods. The matching preventive check is “Version nonsecret application settings and avoid putting credentials into ConfigMaps”.

D:

The suggested review tracks a different technical risk: A successful API mutation does not guarantee updated Pods are healthy and available; rollout status tracks controller progress. Here the sustained control must address: ConfigMaps hold ordinary configuration data; their existence does not automatically inject values into running Pods. Choose “Version nonsecret application settings and avoid putting credentials into ConfigMaps”.

Question 361

At Northstar finance, in an isolated training cluster during a scheduled maintenance rehearsal: An existing ConfigMap invoice-config in namespace ledger must supply environment variables to Deployment invoice-api. Work only within the stated target and verify before declaring success. Which command or initial safe diagnostic step best addresses the stated lab task?

  1. Run kubectl -n ledger rollout status deployment/invoice-api --timeout=120s.
  2. Run kubectl -n ledger rollout undo deployment/invoice-api after checking rollout history.
  3. Run kubectl -n ledger set env deployment/invoice-api --from=configmap/invoice-config.
  4. Run kubectl -n observability set resources deployment/metrics-api --requests=cpu=400m --limits=memory=384Mi after verifying the Deployment's container selection.

Explanation

Correct Answer

C:

Run kubectl -n ledger set env deployment/invoice-api --from=configmap/invoice-config. This is the appropriate command-line action or first safe diagnostic. The technical reason is: Environment variables are copied into new container processes from ConfigMap values; existing running processes need replacement to pick up changes. Validate the result with: Run kubectl -n ledger describe deployment invoice-api and inspect the environment references on newly created Pods. Execute changes only in an authorized disposable lab or after normal production change controls.

Incorrect Answers

A:

The offered action targets: A successful API mutation does not guarantee updated Pods are healthy and available; rollout status tracks controller progress. The case facts point instead to: Environment variables are copied into new container processes from ConfigMap values; existing running processes need replacement to pick up changes. Implement “Run kubectl -n ledger set env deployment/invoice-api --from=configmap/invoice-config” to address that specific condition.

B:

This alternative is a response to another technical cause: A Deployment tracks ReplicaSet revisions and rollout undo restores a recorded earlier Pod template. The reported case instead depends on: Environment variables are copied into new container processes from ConfigMap values; existing running processes need replacement to pick up changes. The action that directly addresses it is “Run kubectl -n ledger set env deployment/invoice-api --from=configmap/invoice-config”.

D:

The offered action targets: Requests inform scheduling and limits cap runtime consumption; the settings play different roles. The case facts point instead to: Environment variables are copied into new container processes from ConfigMap values; existing running processes need replacement to pick up changes. Implement “Run kubectl -n ledger set env deployment/invoice-api --from=configmap/invoice-config” to address that specific condition.

Question 362

At Northstar finance, in an isolated training cluster during a scheduled maintenance rehearsal: An existing ConfigMap invoice-config in namespace ledger must supply environment variables to Deployment invoice-api. Work only within the stated target and verify before declaring success. Which Kubernetes behavior best explains the required change or diagnosis?

  1. Deployment rolling-update parameters govern how many old Pods may be unavailable and extra Pods may be created during replacement.
  2. CronJob suspension prevents new scheduled Jobs but does not terminate existing Jobs already running.
  3. HPA evaluates metrics relative to Pod resource requests; missing metrics or requests can leave desired replicas unknown.
  4. Environment variables are copied into new container processes from ConfigMap values; existing running processes need replacement to pick up changes.

Explanation

Correct Answer

D:

Environment variables are copied into new container processes from ConfigMap values; existing running processes need replacement to pick up changes. This explains the stated condition. The corresponding action is: Run kubectl -n ledger set env deployment/invoice-api --from=configmap/invoice-config. The direct acceptance evidence is: Run kubectl -n ledger describe deployment invoice-api and inspect the environment references on newly created Pods.

Incorrect Answers

A:

This principle describes a separate cause: Deployment rolling-update parameters govern how many old Pods may be unavailable and extra Pods may be created during replacement. The reported condition is governed by: Environment variables are copied into new container processes from ConfigMap values; existing running processes need replacement to pick up changes. The two mechanisms should not be conflated.

B:

CronJob suspension prevents new scheduled Jobs but does not terminate existing Jobs already running. That explanation applies to a different technical failure. Here the controlling principle is: Environment variables are copied into new container processes from ConfigMap values; existing running processes need replacement to pick up changes.

C:

The offered statement is true for this other mechanism: HPA evaluates metrics relative to Pod resource requests; missing metrics or requests can leave desired replicas unknown. It does not explain the facts described here, which follow from: Environment variables are copied into new container processes from ConfigMap values; existing running processes need replacement to pick up changes.

Question 363

At Northstar finance, in an isolated training cluster during a scheduled maintenance rehearsal: An existing ConfigMap invoice-config in namespace ledger must supply environment variables to Deployment invoice-api. Work only within the stated target and verify before declaring success. Which observation best verifies the requested outcome rather than an unrelated state?

  1. Run kubectl -n ledger describe deployment invoice-api and inspect the environment references on newly created Pods.
  2. Run kubectl -n ledger get deployment invoice-api -o jsonpath='{.spec.template.spec.nodeSelector}' and check Pod placements.
  3. Run kubectl -n observability get deployment metrics-api -o yaml and inspect resource requests and limits for each container.
  4. Run kubectl -n ledger describe deployment invoice-api and inspect environment key references without printing secret values.

Explanation

Correct Answer

A:

Run kubectl -n ledger describe deployment invoice-api and inspect the environment references on newly created Pods. This validates the affected object or control path, rather than only showing a command completed. The underlying reason is: Environment variables are copied into new container processes from ConfigMap values; existing running processes need replacement to pick up changes. The intended action is: Run kubectl -n ledger set env deployment/invoice-api --from=configmap/invoice-config.

Incorrect Answers

B:

That test belongs to another control with this basis: Node selectors constrain scheduling to nodes whose labels match all specified key/value pairs; patching the Pod template triggers a rollout. In the current case, the governing reason is: Environment variables are copied into new container processes from ConfigMap values; existing running processes need replacement to pick up changes. The direct verification is “Run kubectl -n ledger describe deployment invoice-api and inspect the environment references on newly created Pods”.

C:

This observation would test a different technical dependency: Requests inform scheduling and limits cap runtime consumption; the settings play different roles. The current issue is governed by: Environment variables are copied into new container processes from ConfigMap values; existing running processes need replacement to pick up changes. Its decisive check is “Run kubectl -n ledger describe deployment invoice-api and inspect the environment references on newly created Pods”.

D:

The alternative verifies a different condition: Pod templates can reference Secret keys without copying literal secret values into the Deployment spec. The current case instead depends on: Environment variables are copied into new container processes from ConfigMap values; existing running processes need replacement to pick up changes. Confirm that “Run kubectl -n ledger describe deployment invoice-api and inspect the environment references on newly created Pods”.

Question 364

At Northstar finance, in an isolated training cluster during a scheduled maintenance rehearsal: An existing ConfigMap invoice-config in namespace ledger must supply environment variables to Deployment invoice-api. Work only within the stated target and verify before declaring success. Which operational control most directly prevents this failure or configuration drift?

  1. Check disruption budgets and readiness behavior before application restarts.
  2. Track whether consumers use environment variables or mounted files when planning ConfigMap refreshes.
  3. Gate deployment promotion on observed rollout and readiness rather than API command exit alone.
  4. Track HPA metric availability and avoid simultaneous manual scaling policies that fight the controller.

Explanation

Correct Answer

B:

Track whether consumers use environment variables or mounted files when planning ConfigMap refreshes. This reduces recurrence of the specific operational failure. It reinforces the action: Run kubectl -n ledger set env deployment/invoice-api --from=configmap/invoice-config. The relevant mechanism is: Environment variables are copied into new container processes from ConfigMap values; existing running processes need replacement to pick up changes.

Incorrect Answers

A:

That safeguard is relevant to: Rollout restart annotates the Pod template so the Deployment controller replaces Pods according to its rollout strategy. The current failure instead follows from: Environment variables are copied into new container processes from ConfigMap values; existing running processes need replacement to pick up changes. Its prevention measure is “Track whether consumers use environment variables or mounted files when planning ConfigMap refreshes”.

C:

The suggested review tracks a different technical risk: A successful API mutation does not guarantee updated Pods are healthy and available; rollout status tracks controller progress. Here the sustained control must address: Environment variables are copied into new container processes from ConfigMap values; existing running processes need replacement to pick up changes. Choose “Track whether consumers use environment variables or mounted files when planning ConfigMap refreshes”.

D:

That safeguard is relevant to: HPA evaluates metrics relative to Pod resource requests; missing metrics or requests can leave desired replicas unknown. The current failure instead follows from: Environment variables are copied into new container processes from ConfigMap values; existing running processes need replacement to pick up changes. Its prevention measure is “Track whether consumers use environment variables or mounted files when planning ConfigMap refreshes”.

Question 365

At Horizon observability, in a disposable simulated environment during a monitored release window: An existing ConfigMap metrics-config in namespace observability must supply environment variables to Deployment metrics-api. Work only within the stated target and verify before declaring success. Which command or initial safe diagnostic step best addresses the stated lab task?

  1. Run kubectl -n observability patch cronjob hourly-rollup --type=merge -p '{"spec":{"suspend":true}}'.
  2. Run kubectl -n observability patch deployment metrics-api --type=merge -p '{"spec":{"template":{"spec":{"tolerations":[{"key":"special","operator":"Equal","value":"dedicated","effect":"NoSchedule"}]}}}}' after checking existing tolerations.
  3. Run kubectl -n observability create secret generic lab-metrics-key --from-literal=TOKEN=dummy-demo-two for this disposable lab only.
  4. Run kubectl -n observability set env deployment/metrics-api --from=configmap/metrics-config.

Explanation

Correct Answer

D:

Run kubectl -n observability set env deployment/metrics-api --from=configmap/metrics-config. This is the appropriate command-line action or first safe diagnostic. The technical reason is: Environment variables are copied into new container processes from ConfigMap values; existing running processes need replacement to pick up changes. Validate the result with: Run kubectl -n observability describe deployment metrics-api and inspect the environment references on newly created Pods. Execute changes only in an authorized disposable lab or after normal production change controls.

Incorrect Answers

A:

This alternative is a response to another technical cause: CronJob suspension prevents new scheduled Jobs but does not terminate existing Jobs already running. The reported case instead depends on: Environment variables are copied into new container processes from ConfigMap values; existing running processes need replacement to pick up changes. The action that directly addresses it is “Run kubectl -n observability set env deployment/metrics-api --from=configmap/metrics-config”.

B:

The proposed action belongs to the mechanism: A toleration allows a Pod past a matching taint but does not ensure placement without node selection and capacity. Here the stated fault follows a different mechanism: Environment variables are copied into new container processes from ConfigMap values; existing running processes need replacement to pick up changes. The corrective choice is “Run kubectl -n observability set env deployment/metrics-api --from=configmap/metrics-config”.

C:

The offered action targets: Kubernetes Secrets are API objects intended for sensitive values, but literals in a shell command can leak via shell history and process observation. The case facts point instead to: Environment variables are copied into new container processes from ConfigMap values; existing running processes need replacement to pick up changes. Implement “Run kubectl -n observability set env deployment/metrics-api --from=configmap/metrics-config” to address that specific condition.

Question 366

At Horizon observability, in a disposable simulated environment during a monitored release window: An existing ConfigMap metrics-config in namespace observability must supply environment variables to Deployment metrics-api. Work only within the stated target and verify before declaring success. Which Kubernetes behavior best explains the required change or diagnosis?

  1. Environment variables are copied into new container processes from ConfigMap values; existing running processes need replacement to pick up changes.
  2. Pod templates can reference Secret keys without copying literal secret values into the Deployment spec.
  3. Node selectors constrain scheduling to nodes whose labels match all specified key/value pairs; patching the Pod template triggers a rollout.
  4. HPA evaluates metrics relative to Pod resource requests; missing metrics or requests can leave desired replicas unknown.

Explanation

Correct Answer

A:

Environment variables are copied into new container processes from ConfigMap values; existing running processes need replacement to pick up changes. This explains the stated condition. The corresponding action is: Run kubectl -n observability set env deployment/metrics-api --from=configmap/metrics-config. The direct acceptance evidence is: Run kubectl -n observability describe deployment metrics-api and inspect the environment references on newly created Pods.

Incorrect Answers

B:

The offered statement is true for this other mechanism: Pod templates can reference Secret keys without copying literal secret values into the Deployment spec. It does not explain the facts described here, which follow from: Environment variables are copied into new container processes from ConfigMap values; existing running processes need replacement to pick up changes.

C:

This principle describes a separate cause: Node selectors constrain scheduling to nodes whose labels match all specified key/value pairs; patching the Pod template triggers a rollout. The reported condition is governed by: Environment variables are copied into new container processes from ConfigMap values; existing running processes need replacement to pick up changes. The two mechanisms should not be conflated.

D:

HPA evaluates metrics relative to Pod resource requests; missing metrics or requests can leave desired replicas unknown. That explanation applies to a different technical failure. Here the controlling principle is: Environment variables are copied into new container processes from ConfigMap values; existing running processes need replacement to pick up changes.

Question 367

At Horizon observability, in a disposable simulated environment during a monitored release window: An existing ConfigMap metrics-config in namespace observability must supply environment variables to Deployment metrics-api. Work only within the stated target and verify before declaring success. Which observation best verifies the requested outcome rather than an unrelated state?

  1. Run kubectl -n observability get deployment metrics-api -o yaml and inspect resource requests and limits for each container.
  2. Run kubectl -n observability describe deployment metrics-api and inspect the environment references on newly created Pods.
  3. Run kubectl -n fulfillment describe deployment dispatch-api and inspect environment key references without printing secret values.
  4. Run kubectl -n observability get hpa metrics-api and inspect observed utilization and replica bounds.

Explanation

Correct Answer

B:

Run kubectl -n observability describe deployment metrics-api and inspect the environment references on newly created Pods. This validates the affected object or control path, rather than only showing a command completed. The underlying reason is: Environment variables are copied into new container processes from ConfigMap values; existing running processes need replacement to pick up changes. The intended action is: Run kubectl -n observability set env deployment/metrics-api --from=configmap/metrics-config.

Incorrect Answers

A:

That test belongs to another control with this basis: Requests inform scheduling and limits cap runtime consumption; the settings play different roles. In the current case, the governing reason is: Environment variables are copied into new container processes from ConfigMap values; existing running processes need replacement to pick up changes. The direct verification is “Run kubectl -n observability describe deployment metrics-api and inspect the environment references on newly created Pods”.

C:

The alternative verifies a different condition: Pod templates can reference Secret keys without copying literal secret values into the Deployment spec. The current case instead depends on: Environment variables are copied into new container processes from ConfigMap values; existing running processes need replacement to pick up changes. Confirm that “Run kubectl -n observability describe deployment metrics-api and inspect the environment references on newly created Pods”.

D:

That test belongs to another control with this basis: HPA evaluates metrics relative to Pod resource requests; missing metrics or requests can leave desired replicas unknown. In the current case, the governing reason is: Environment variables are copied into new container processes from ConfigMap values; existing running processes need replacement to pick up changes. The direct verification is “Run kubectl -n observability describe deployment metrics-api and inspect the environment references on newly created Pods”.

Question 368

At Horizon observability, in a disposable simulated environment during a monitored release window: An existing ConfigMap metrics-config in namespace observability must supply environment variables to Deployment metrics-api. Work only within the stated target and verify before declaring success. Which operational control most directly prevents this failure or configuration drift?

  1. For production use protected secret-delivery workflows, RBAC and encryption-at-rest controls.
  2. Pin reviewed image tags or digests and retain rollout history for recovery.
  3. Track whether consumers use environment variables or mounted files when planning ConfigMap refreshes.
  4. Check disruption budgets and readiness behavior before application restarts.

Explanation

Correct Answer

C:

Track whether consumers use environment variables or mounted files when planning ConfigMap refreshes. This reduces recurrence of the specific operational failure. It reinforces the action: Run kubectl -n observability set env deployment/metrics-api --from=configmap/metrics-config. The relevant mechanism is: Environment variables are copied into new container processes from ConfigMap values; existing running processes need replacement to pick up changes.

Incorrect Answers

A:

This routine guards against another mechanism: Kubernetes Secrets are API objects intended for sensitive values, but literals in a shell command can leak via shell history and process observation. The recurring exposure in the current case is: Environment variables are copied into new container processes from ConfigMap values; existing running processes need replacement to pick up changes. The matching preventive check is “Track whether consumers use environment variables or mounted files when planning ConfigMap refreshes”.

B:

The suggested review tracks a different technical risk: Updating a Deployment Pod template triggers a controlled rollout; restarting Pods alone will not change the image reference. Here the sustained control must address: Environment variables are copied into new container processes from ConfigMap values; existing running processes need replacement to pick up changes. Choose “Track whether consumers use environment variables or mounted files when planning ConfigMap refreshes”.

D:

This routine guards against another mechanism: Rollout restart annotates the Pod template so the Deployment controller replaces Pods according to its rollout strategy. The recurring exposure in the current case is: Environment variables are copied into new container processes from ConfigMap values; existing running processes need replacement to pick up changes. The matching preventive check is “Track whether consumers use environment variables or mounted files when planning ConfigMap refreshes”.

Question 369

At Pinecrest logistics, in a sandbox Kubernetes cluster during a recovery tabletop exercise: An existing ConfigMap dispatch-config in namespace fulfillment must supply environment variables to Deployment dispatch-api. Work only within the stated target and verify before declaring success. Which command or initial safe diagnostic step best addresses the stated lab task?

  1. Run kubectl -n fulfillment set env deployment/dispatch-api --from=configmap/dispatch-config.
  2. Run kubectl -n fulfillment rollout restart deployment/dispatch-api.
  3. Run kubectl -n observability create configmap metrics-config --from-literal=MODE=production after checking whether it already exists.
  4. Run kubectl -n fulfillment set env deployment/dispatch-api --from=secret/lab-dispatch-key.

Explanation

Correct Answer

A:

Run kubectl -n fulfillment set env deployment/dispatch-api --from=configmap/dispatch-config. This is the appropriate command-line action or first safe diagnostic. The technical reason is: Environment variables are copied into new container processes from ConfigMap values; existing running processes need replacement to pick up changes. Validate the result with: Run kubectl -n fulfillment describe deployment dispatch-api and inspect the environment references on newly created Pods. Execute changes only in an authorized disposable lab or after normal production change controls.

Incorrect Answers

B:

The offered action targets: Rollout restart annotates the Pod template so the Deployment controller replaces Pods according to its rollout strategy. The case facts point instead to: Environment variables are copied into new container processes from ConfigMap values; existing running processes need replacement to pick up changes. Implement “Run kubectl -n fulfillment set env deployment/dispatch-api --from=configmap/dispatch-config” to address that specific condition.

C:

This alternative is a response to another technical cause: ConfigMaps hold ordinary configuration data; their existence does not automatically inject values into running Pods. The reported case instead depends on: Environment variables are copied into new container processes from ConfigMap values; existing running processes need replacement to pick up changes. The action that directly addresses it is “Run kubectl -n fulfillment set env deployment/dispatch-api --from=configmap/dispatch-config”.

D:

The proposed action belongs to the mechanism: Pod templates can reference Secret keys without copying literal secret values into the Deployment spec. Here the stated fault follows a different mechanism: Environment variables are copied into new container processes from ConfigMap values; existing running processes need replacement to pick up changes. The corrective choice is “Run kubectl -n fulfillment set env deployment/dispatch-api --from=configmap/dispatch-config”.

Question 370

At Pinecrest logistics, in a sandbox Kubernetes cluster during a recovery tabletop exercise: An existing ConfigMap dispatch-config in namespace fulfillment must supply environment variables to Deployment dispatch-api. Work only within the stated target and verify before declaring success. Which Kubernetes behavior best explains the required change or diagnosis?

  1. A successful API mutation does not guarantee updated Pods are healthy and available; rollout status tracks controller progress.
  2. Environment variables are copied into new container processes from ConfigMap values; existing running processes need replacement to pick up changes.
  3. Pod templates can reference Secret keys without copying literal secret values into the Deployment spec.
  4. Node selectors constrain scheduling to nodes whose labels match all specified key/value pairs; patching the Pod template triggers a rollout.

Explanation

Correct Answer

B:

Environment variables are copied into new container processes from ConfigMap values; existing running processes need replacement to pick up changes. This explains the stated condition. The corresponding action is: Run kubectl -n fulfillment set env deployment/dispatch-api --from=configmap/dispatch-config. The direct acceptance evidence is: Run kubectl -n fulfillment describe deployment dispatch-api and inspect the environment references on newly created Pods.

Incorrect Answers

A:

The offered statement is true for this other mechanism: A successful API mutation does not guarantee updated Pods are healthy and available; rollout status tracks controller progress. It does not explain the facts described here, which follow from: Environment variables are copied into new container processes from ConfigMap values; existing running processes need replacement to pick up changes.

C:

Pod templates can reference Secret keys without copying literal secret values into the Deployment spec. That explanation applies to a different technical failure. Here the controlling principle is: Environment variables are copied into new container processes from ConfigMap values; existing running processes need replacement to pick up changes.

D:

The offered statement is true for this other mechanism: Node selectors constrain scheduling to nodes whose labels match all specified key/value pairs; patching the Pod template triggers a rollout. It does not explain the facts described here, which follow from: Environment variables are copied into new container processes from ConfigMap values; existing running processes need replacement to pick up changes.