A company has a Kubernetes cluster with a service mesh (Istio) installed. They have a service 'api' that is exposed to the internet via an Istio Gateway. The team wants to implement a canary release for the 'api' service. They have two versions of the service, 'v1' and 'v2', deployed as separate Deployments. They want to send 10% of the traffic to 'v2' and 90% to 'v1'. They also want to ensure that the canary release can be monitored. Which configuration should the team use?

Create a NetworkPolicy that allows 10% of traffic to reach 'v2'.

Create a DestinationRule that routes 90% of traffic to 'v1' and 10% to 'v2'.

Create a Service of type LoadBalancer that routes 10% of traffic to 'v2'.

Create a VirtualService that routes 90% of traffic to 'v1' and 10% to 'v2', and use the service mesh's observability features to monitor the canary.

A company is deploying a Helm chart that includes a Deployment with three replicas. The chart also includes a Service of type ClusterIP. The team wants to ensure that the Deployment is updated with a rolling update strategy, and that the Service is not recreated during a 'helm upgrade'. The team is using a standard Helm chart structure. What should the team do to achieve this?

Use a separate Helm chart for the Service to avoid it being updated.

Set the Deployment's 'recreate' strategy to ensure a clean update.

Ensure the Deployment template has a 'strategy' field set to 'RollingUpdate', and ensure the Service template has a stable name.

Use a pre-upgrade hook to delete the Service before the upgrade.

A platform team has created a Helm chart for a stateful application. The chart includes a StatefulSet, a Service, and a PersistentVolumeClaim. The team wants to deploy this chart to a production cluster. They need to ensure that the PersistentVolumeClaim uses a specific StorageClass that is only available in the production cluster. How should the team configure the Helm chart to achieve this?

Define the StorageClass name as a value in the chart's values.yaml file and pass a custom value file during deployment.

Use a Kubernetes Secret to store the StorageClass name and reference it in the PersistentVolumeClaim.

Create a separate Helm chart for the production environment with the correct StorageClass.

Hardcode the production StorageClass name in the chart's PersistentVolumeClaim template.

A platform team manages a Helm chart for a critical application. They need to deploy a new version of the chart to production. The new version includes a change to the PersistentVolumeClaim template, which will cause the PVC to be recreated. The team wants to avoid any downtime for the application. What is the best approach for the team to take?

Delete the existing PVC manually before running 'helm upgrade'.

Run 'helm upgrade' directly. Helm will handle the PVC migration automatically without any downtime.

Review the change to the PVC template and ensure that the new PVC can be provisioned before the old one is deleted. Use a pre-upgrade hook to back up the data.

Use 'helm rollback' if the upgrade fails. This will automatically restore the old PVC.

VMwareVCAP-VCF VKS (3V0-24.25)

Domain 1Objective 2

Use Kubernetes Architecture, Networking, Storage, Service Mesh, and Helm VCAP-VCF-VKS Practice Questions (Page 1)

Part of the IT Architectures, Technologies, Standards domain, which makes up ~9% of our current practice bank.

20questions here

4free pages

5concepts

Questions 1–5

1expert · hard
A company has a Kubernetes cluster with a service mesh (Istio) installed. They have a service 'api' that is exposed to the internet via an Istio Gateway. The team wants to implement a canary release for the 'api' service. They have two versions of the service, 'v1' and 'v2', deployed as separate Deployments. They want to send 10% of the traffic to 'v2' and 90% to 'v1'. They also want to ensure that the canary release can be monitored. Which configuration should the team use?
Select an answer first
2expert · hard
A company is deploying a Helm chart that includes a Deployment with three replicas. The chart also includes a Service of type ClusterIP. The team wants to ensure that the Deployment is updated with a rolling update strategy, and that the Service is not recreated during a 'helm upgrade'. The team is using a standard Helm chart structure. What should the team do to achieve this?
Select an answer first
3application · medium
A platform team has created a Helm chart for a stateful application. The chart includes a StatefulSet, a Service, and a PersistentVolumeClaim. The team wants to deploy this chart to a production cluster. They need to ensure that the PersistentVolumeClaim uses a specific StorageClass that is only available in the production cluster. How should the team configure the Helm chart to achieve this?
Select an answer first
4expert · hard
A platform team manages a Helm chart for a critical application. They need to deploy a new version of the chart to production. The new version includes a change to the PersistentVolumeClaim template, which will cause the PVC to be recreated. The team wants to avoid any downtime for the application. What is the best approach for the team to take?
Select an answer first
5foundation · easy
Which capability is provided by a service mesh to help operators understand service-to-service communication?
Select an answer first

Finished these 5 questions?

Review the revealed explanations, or continue through the curriculum.

Next 5 questions →Back to VCAP-VCF-VKS

Free Basic Practice is a study aid with revealable answers — not a scored exam. Examers.io is independent and not affiliated with or endorsed by VMware. “VCAP-VCF-VKS” is a trademark of its owner, used for identification only.

Use Kubernetes Architecture, Networking, Storage, Service Mesh, and Helm VCAP-VCF-VKS Practice Questions (Page 1)

Questions 1–5

Which capability is provided by a service mesh to help operators understand service-to-service communication?

Keep studying — IT Architectures, Technologies, Standards