最新的RedHat Red Hat Certified Specialist in OpenShift Virtualization - EX316免費考試真題
How do you clean up a VM template and all its associated resources?
正確答案:
See the Explanation.
Explanation:
1. Delete the template: oc delete template <name>
2. Optionally delete related PVCs, DataVolumes.
3. List templates with oc get templates
4. Ensure no VMs still use it.
5. Clean practice for template lifecycle.
Explanation:
1. Delete the template: oc delete template <name>
2. Optionally delete related PVCs, DataVolumes.
3. List templates with oc get templates
4. Ensure no VMs still use it.
5. Clean practice for template lifecycle.
How do you verify NMState is managing your nodes?
正確答案:
See the Explanation.
Explanation:
1. List all NMStateConfig objects: oc get nmstateconfigs
2. Check if one exists per worker/master node.
3. View config: oc describe nmstateconfig <node-name>
4. Confirm node labels: nmstate.io/node-network-config=true
5. Validate status using: oc get nncp (NodeNetworkConfigurationPolicy)
Explanation:
1. List all NMStateConfig objects: oc get nmstateconfigs
2. Check if one exists per worker/master node.
3. View config: oc describe nmstateconfig <node-name>
4. Confirm node labels: nmstate.io/node-network-config=true
5. Validate status using: oc get nncp (NodeNetworkConfigurationPolicy)
How do you connect a VM to an NFS share using Multus?
正確答案:
See the Explanation.
Explanation:
1. Create Multus NAD to connect to NFS network.
2. Inside VM:
o Install nfs-utils
o Mount with: mount -t nfs <nfs-server>:/path /mnt
3. Automount via /etc/fstab
4. Validate mount and permissions.
5. Useful for external shared content.
Explanation:
1. Create Multus NAD to connect to NFS network.
2. Inside VM:
o Install nfs-utils
o Mount with: mount -t nfs <nfs-server>:/path /mnt
3. Automount via /etc/fstab
4. Validate mount and permissions.
5. Useful for external shared content.
How do you verify the PVCs created from a VM snapshot restore?
正確答案:
See the Explanation.
Explanation:
1. After restore: oc get pvc -l snapshot.kubevirt.io/restore-name=<restore-name>
2. Check status and sizes: oc describe pvc <name>
3. Ensure they match original PVCs.
4. Confirm bound state.
5. Mounted automatically to restored VM.
Explanation:
1. After restore: oc get pvc -l snapshot.kubevirt.io/restore-name=<restore-name>
2. Check status and sizes: oc describe pvc <name>
3. Ensure they match original PVCs.
4. Confirm bound state.
5. Mounted automatically to restored VM.
How do you simulate readiness failure to observe probe behavior?
正確答案:
See the Explanation.
Explanation:
1. Inside VM, stop the service monitored by readinessProbe.
2. Run:
systemctl stop sshd
3. Watch oc describe vmi for readiness change.
4. VM will be marked as NotReady in endpoints.
5. Traffic stops until service is restored.
Explanation:
1. Inside VM, stop the service monitored by readinessProbe.
2. Run:
systemctl stop sshd
3. Watch oc describe vmi for readiness change.
4. VM will be marked as NotReady in endpoints.
5. Traffic stops until service is restored.
How do you manually assign a NodePort port number to avoid conflicts?
正確答案:
See the Explanation.
Explanation:
1. In your Service YAML, set the nodePort
explicitly: nodePort: 30444
2. Ensure the port is within OpenShift's NodePort range (default: 30000-32767).
3. Avoid overlapping ports across services.
4. Apply and test access externally.
5. Prevents port collision.
Explanation:
1. In your Service YAML, set the nodePort
explicitly: nodePort: 30444
2. Ensure the port is within OpenShift's NodePort range (default: 30000-32767).
3. Avoid overlapping ports across services.
4. Apply and test access externally.
5. Prevents port collision.
How do you list all PVCs used by running VMs in a namespace?
正確答案:
See the Explanation.
Explanation:
1. List VMs: oc get vm
2. For each VM:
oc get vm <name> -o jsonpath='{.spec.template.spec.volumes[*].persistentVolumeClaim.claimName}'
3. Optionally use: oc get pvc -o wide to find binding.
4. Automate with a script for large environments.
5. Helpful for auditing storage usage.
Explanation:
1. List VMs: oc get vm
2. For each VM:
oc get vm <name> -o jsonpath='{.spec.template.spec.volumes[*].persistentVolumeClaim.claimName}'
3. Optionally use: oc get pvc -o wide to find binding.
4. Automate with a script for large environments.
5. Helpful for auditing storage usage.
How do you find which VolumeSnapshotClass is used for a VM snapshot?
正確答案:
See the Explanation.
Explanation:
1. Get VM snapshot:
oc get vmsnapshot <name> -o yaml
2. Follow status.virtualMachineSnapshotContentName
3. Inspect content's volume snapshot source.
4. Cross-check volumeSnapshotClassName.
5. Compare with oc get volumesnapshotclass.
Explanation:
1. Get VM snapshot:
oc get vmsnapshot <name> -o yaml
2. Follow status.virtualMachineSnapshotContentName
3. Inspect content's volume snapshot source.
4. Cross-check volumeSnapshotClassName.
5. Compare with oc get volumesnapshotclass.
How do you force a watchdog reboot for testing?
正確答案:
See the Explanation.
Explanation:
1. Access VM and disable watchdog
daemon: systemctl stop watchdog
2. Wait for timeout (~60 seconds).
3. Watchdog device will trigger a guest reboot.
4. Confirm with:
oc get vmi -o wide
5. VM should restart on the same or new node.
Explanation:
1. Access VM and disable watchdog
daemon: systemctl stop watchdog
2. Wait for timeout (~60 seconds).
3. Watchdog device will trigger a guest reboot.
4. Confirm with:
oc get vmi -o wide
5. VM should restart on the same or new node.
How do you validate the success of a VM restore operation?
正確答案:
See the Explanation.
Explanation:
1. Check VM is created: oc get vm <vm>
2. Confirm disk is attached and ready: oc get pvc
3. Start the VM: virtctl start <vm>
4. Use virtctl console or SSH to verify boot.
5. Review app or OS logs to confirm full recovery.
Explanation:
1. Check VM is created: oc get vm <vm>
2. Confirm disk is attached and ready: oc get pvc
3. Start the VM: virtctl start <vm>
4. Use virtctl console or SSH to verify boot.
5. Review app or OS logs to confirm full recovery.
How do you reboot the virtual machine from inside the guest OS?
正確答案:
See the Explanation.
Explanation:
1. Inside
VM: sudo
reboot
2. VM will shut down and restart.
3. From host:
virtctl restart <vm-name>
4. Confirm with oc get vmi
5. Useful during package updates.
Explanation:
1. Inside
VM: sudo
reboot
2. VM will shut down and restart.
3. From host:
virtctl restart <vm-name>
4. Confirm with oc get vmi
5. Useful during package updates.
How do you validate the health probes configured on a running VM?
正確答案:
See the Explanation.
Explanation:
1. Run:
oc describe vmi <vm-name>
2. Check the Conditions: section for probe status.
3. Look for LivenessProbeFailed or Ready=True.
4. Use oc logs on virt-launcher pod for probe output.
5. Adjust probe parameters if failing unexpectedly.
Explanation:
1. Run:
oc describe vmi <vm-name>
2. Check the Conditions: section for probe status.
3. Look for LivenessProbeFailed or Ready=True.
4. Use oc logs on virt-launcher pod for probe output.
5. Adjust probe parameters if failing unexpectedly.
How do you test node drain compatibility with VM live migration?
正確答案:
See the Explanation.
Explanation:
1. Start a VM on a worker node.
2. Drain the node:
oc adm drain <node> --ignore-daemonsets --delete-emptydir-data
3. Observe that VM is migrated automatically.
4. Check oc get vmi to verify node change.
5. Ensures seamless upgrades or patching.
Explanation:
1. Start a VM on a worker node.
2. Drain the node:
oc adm drain <node> --ignore-daemonsets --delete-emptydir-data
3. Observe that VM is migrated automatically.
4. Check oc get vmi to verify node change.
5. Ensures seamless upgrades or patching.