Q1 (EN): How would you handle a host failure in a virtualisation cluster? Answer (optional): Validate alerts, confirm HA restarts, evacuate via vMotion if needed, place the host in maintenance, collect logs/dumps, perform RCA and apply patch/firmware. Q2 (EN): When would you use vMotion versus Storage vMotion? Answer (optional): vMotion for CPU/RAM migration to mitigate host risk; Storage vMotion to relieve datastore pressure or rebalance I/O without guest downtime. Q3 (EN): How do you choose between iSCSI, NFS and Fibre Channel? Answer (optional): FC for low-latency Tier-1 workloads; iSCSI for operational simplicity with MPIO and security; NFS v4.1 for flexibility. Enforce isolation and storage QoS. Q4 (EN): Your backup/DR approach and typical RPO/RTO? Answer (optional): 3-2-1-1-0 strategy, application-aware backups for critical VMs, weekly restore drills; set RPO/RTO by business criticality (e.g., 15 min / 1 hour). Q5 (EN): Datastore is getting full—what’s your action plan? Answer (optional): Alert thresholds ~85/90%, clean snapshots, Storage vMotion hot spots, extend LUN/reclaim space, then update capacity forecasts. Q6 (EN): How do you troubleshoot high disk latency? Answer (optional): Trace host→HBA→switch→array and in-guest I/O, tune queue depth, isolate noisy neighbours, adjust storage policy/tiering. Q7 (EN): How do you manage changes and rollback? Answer (optional): RFC with risk/impact and a clear rollback plan; test → maintenance window → post-checks; document runbook and results.