Citrix CCP-N study plan

Sketch the Citrix ADC architecture from memory: packet engine, nCore versus classic, MPX/VPX/CPX/BLX form factors, and where each plane (management, data, control) runs

Differentiate virtual server types (L4 vs L7, content switching, SSL offload, transparent, forwarding) and state which traffic pattern each fits

Trace one client request end-to-end through a load balancing vserver, service, and monitor, naming the decision point at each hop

Map the three default load balancing methods (round robin, least connection, least response time) to a traffic profile where each is the wrong choice

Configure a load balancing vserver with three services and bind monitors, then break one service and observe the state change

Explain monitor types (PING, TCP, HTTP, HTTP-ECV, custom script) and choose interval, retries, and timeout values that avoid false positives

Compare persistence methods (source IP, cookie insert, SSL session ID, radius) and justify the choice for a stateful web app

Calculate effective capacity and failover behavior when service weights and max-client settings interact

Design a VLAN layout with NSIP, SNIP, VIP, and MIP assignments, explaining which subnet each address must belong to

Configure static routes, a default gateway, and policy-based routes, and predict forwarding when overlapping routes exist

Enable and verify USIP and MAC-based forwarding in a mode where return traffic would otherwise bypass the ADC

Describe interface modes (access, trunk, 802.1Q tagging) and apply them to a two-switch redundant topology

Bind a server certificate and intermediate chain to an SSL vserver, then verify chain order with openssl s_client

Configure SSL profiles, ciphers, and TLS protocol versions, and articulate the tradeoff between security posture and legacy client support

Explain Certificate Signing Request generation, key matching, and what breaks when a certificate is renewed without updating the binding

Describe HA pair states (primary/secondary, sync, propagation) and the conditions that trigger failover, including forced and partial failover

Configure HA nodes with heartbeat and sync settings, then simulate a link failure and record which traffic survives

Explain GSLB components (sites, services, monitors, MEP, DNS VIP) and how metric exchange drives site selection

Compare GSLB algorithms (round robin, static proximity, dynamic RTT, least connections) and select one for a stated latency requirement

Describe how GSLB interacts with DNS delegation and CNAME-based configuration, and where the resolution decision is made

Build an authentication vserver with LDAP and local fallback, then bind it to a traffic policy for a protected resource

Write authorization and responder policies that permit, deny, and redirect, and order them so evaluation precedence is correct

Explain session profiles, timeouts, and single sign-on behavior across multiple protected applications

Apply a basic application firewall or rate-limiting control and describe the traffic it blocks

Enable compression and caching policies and measure the before/after response size and latency in a lab

Configure a content switching vserver that routes by URL path or host header, and verify each branch

Interpret the dashboard, syslog, and nsconmsg output to isolate a slow-backend versus ADC-side bottleneck

Use nstrace or a packet capture to confirm where a request stalls, and document the evidence trail

Re-run every missed self-test question from weeks 2 to 7 and rewrite each explanation in your own words

Rebuild a full lab from a blank ADC: VLANs, HA pair, SSL vserver, GSLB stub, and an authentication policy

Time a 60-question mixed practice set and log weak domains by percentage

Produce a one-page cheat sheet of commands and defaults you repeatedly forget