Correct Answer:

See the Explanation.
Explanation:
1. Taint a node:
oc adm taint nodes worker-2 dedicated=vm:NoSchedule
2. Add to VM YAML:
template:
spec:
tolerations:
- key: dedicated
value: vm
effect: NoSchedule
3. VM will now schedule on tainted node.
4. Used for isolating workloads.
5. Confirm with: oc describe node worker-2

Correct Answer:

See the Explanation.
Explanation:
1. Ensure the VM is running and listening on the desired port (e.g., 80).
2. Label the VM:
oc label vm <vm-name> app=web-vm
3. Create a service:
apiVersion: v1
kind: Service
metadata:
name: web-vm-svc
spec:
selector:
kubevirt.io/domain: <vm-name>
ports:
- port: 80
targetPort: 80
4. Apply with oc apply -f svc.yaml
5. Test with curl web-vm-svc.default.svc.cluster.local

Correct Answer:

See the Explanation.
Explanation:
1. Snapshot PVC using CSI snapshot (if enabled).
2. Export PVC using rsync/restic/Velero or by cloning to backup namespace.
3. For manual backup: use kubectl cp or mount PVC to a pod and archive.
4. Store off-cluster if required.
5. Reimport later into new DV.

Correct Answer:

See the Explanation.
Explanation:
1. Use a storage class that supports encryption (e.g., Ceph or CSI driver).
2. Confirm with:
oc get sc <sc-name> -o yaml | grep encryption
3. Ensure PVC uses that class.
4. Use CSI secrets if required.
5. Validate with provider documentation.

Correct Answer:

See the Explanation.
Explanation:
1. Define two network interfaces:
networks:
- name: default
pod: {}
- name:
extnet
multus:
networkName: ext-bridge-net
interfaces:
- name: default
masquerade: {}
- name: extnet
bridge: {}
2. Confirm both eth0 and eth1 are inside the VM.
3. Use eth1 for external and eth0 for internal.
4. Use cloud-init for routing preference.
5. Test both networks.