Citrix Certified Expert - Virtualization: Assessment and Design cheat sheet
Citrix Certified Expert - Virtualization: Assessment and Design · Keep the key ideas within reach.
Assess requirements and design the user experience
Segment users by actual workload, location, endpoints and required capabilities.
Define acceptance criteria and test representative user segments.
Verify platform/version support for peripherals, authentication and media optimization.
Treat HDX settings as trade-offs to test rather than universal defaults.
Link requirements to decisions, rationale and validation evidence.
Access, authentication and the launch path
Separate authentication, enumeration, brokering and HDX transport.
The VDA hosts the application; Controllers do not render every session frame.
Cloud Connector and Rendezvous responsibilities depend on the selected architecture.
FAS supports certificate-based VDA logon in an appropriately configured trusted design.
Match troubleshooting evidence to the failing stage and protect sensitive logs.
Images, applications and user state
Compare MCS and Citrix Provisioning dependencies and operational trade-offs.
Assignment, machine persistence and user-state persistence are separate design decisions.
BDM bootstrap selection does not by itself determine all target IP configuration.
Validate application/layer compatibility and user-state concurrency requirements.
Test image updates and document rollback and separate data recovery.
Controllers, catalogs, policies and management
A delivery group can draw compatible machines from multiple catalogs.
A single machine belongs to one delivery group at a time.
Evaluate policy scope, filters, priorities and resulting settings rather than claiming universal precedence.
Use roles and scopes for least-privilege delegated administration.
Monitoring evidence suggests hypotheses; validate the actual dependency or failure.
Compute, storage, network and capacity evidence
Use representative measured workloads rather than a universal sessions-per-host number.
Test launch bursts as well as steady-state operation.
Include surviving capacity under the agreed failure scenario.
Measure storage latency, I/O, network and profile dependencies separately.
Balance service requirements, fault domains, startup capacity and cost.
Availability, multi-site behaviour and recovery
Define RTO, RPO, user scope and failure conditions before selecting components.
Map shared dependencies that can defeat apparent redundancy.
LHC and Workspace connection-lease continuity are distinct mechanisms.
Replication and backups have different roles in recovery from corruption or deletion.
Exercise and measure the complete runbook, including usable applications and data.