Cluster Test and Verification
NCP-AII · 66 questions
- A city must decide when a new permitting GPU host may join the shared queue. What Domain 4 gate should run first?
- County health sees thermal and power warnings only while single-node GPU stress is running. What should operators conclude?
- Transit ops images many new GPU nodes and needs comparable single-node stress results. What should the standard require?
- A school-district lab runs single-node stress and observes ECC errors and XID storms. What is the correct acceptance action?
- Emergency management must stress newly imaged GPU nodes without jeopardizing 911 NLP standby capacity. How should stress be planned?
- After bring-up, a city wants a floating-point performance baseline on municipal GPU nodes. Which Domain 4 action fits?
- County health finishes HPL on HGX-class inference nodes. How should operators interpret the GFLOPS results?
- Transit ops applies GPU and system firmware updates on a training rack. What HPL practice detects regressions?
- A water-utility digital-twin team needs HPL results comparable across racks. What must be controlled?
- Housing authority acceptance finds one GPU node with an HPL score far below peer nodes. What should operators do?
- A city multi-GPU permitting server must prove intra-node NVLink paths before fabric tests. What should operators run?
- County health single-node NCCL shows asymmetric bandwidth across GPU pairs on an NVLink Switch system. What should operators suspect?
- Transit ops builds a single-node NCCL acceptance suite for new multi-GPU servers. What should the suite include?
- A school-district lab runs single-node NCCL all-reduce. What participation result is required for acceptance?
- Courts OCR finishes hardware install on multi-GPU servers and needs a reference for later regressions. What single-node NCCL practice is required?
- A city must declare an AI fabric row ready and needs proof interconnects are healthy. What cable validation should operators perform?
- County health verification shows BER and signal metrics failing thresholds on one AI fabric cable. What should operators do?
- Transit ops recabled GPU fabric ports and must prove signal health again. What confirmation method fits Domain 4?
- A water-utility AI link shows poor signal quality. Operators must choose the right triage path. What distinction matters?
- Library AI rack validation finishes cable signal checks. What documentation practice is required?
- A city must prove rail-optimized GPU fabric cabling matches design before load. What confirmation is required?
- County health sees links up but NCCL performance far below design after a re-cable. What cabling fault should operators suspect?
- Transit ops must prove each AI fabric cable lands on the intended ports. What verification practice fits?
- Emergency management finds a storage cable seated in a compute rail port on the AI fabric. What should operators do?
- A city prepares to load an AI fabric and must check leaf and spine software currency. What Domain 4 confirmation is required?
- County health finds a leaf switch still on an outdated image during AI fabric validation. What gate action is correct?
- Transit ops completes maintenance on the GPU fabric and must prove switch software consistency. What should operators do?
- A school-district lab upgrades a fabric switch and must close the change. What validation step is required?
- A city must accept DPU-equipped municipal GPU nodes. What BlueField-3 confirmation belongs in Domain 4 verification?
- County health discovery finds a BlueField-3 still on factory firmware during rack acceptance. What should operators do?
- Transit ops defines the contents of every GPU rack acceptance package. What BlueField-3 practice should be included?
- A water utility needs BlueField-3 offload features that depend on DOCA-aligned software. What verification is required?
- A city prepares long-reach AI optics and must validate pluggable modules. What Domain 4 confirmation applies where supported?
- County health finds optics whose firmware is below the approved AI fabric level. What remediation is correct?
- Transit ops performs cable and optics validation walks on the GPU fabric. What transceiver practice should be included?
- Emergency management sees intermittent AI fabric link flaps during verification. What transceiver-related investigation fits Domain 4?
- A city brings up new AI racks and needs a broad node health assessment. What Domain 4 tool should operators run?
- County health ClusterKit output fails in a way that points to network versus GPU. What should operators do with the results?
- Transit ops finishes a major firmware window on the GPU fleet. What ClusterKit practice should follow?
- A school-district lab accepts sibling GPU nodes and wants to spot outliers. How should ClusterKit reports be used?
- Courts OCR completes ClusterKit on new GPU nodes and must keep municipal change evidence. What practice is required?
- A city must prove east-west fabric bandwidth across its municipal AI factory before training jobs scale out. What should operators run?
- County health measures NCCL east-west bandwidth well below the fabric design target. What should operators do next?
- Transit ops adds a new GPU rack and needs a reference for later fabric regressions. What NCCL practice is required?
- A water utility must confirm NCCL performance matches its rail-optimized AI topology. What should verification show?
- Housing authority will not start production training until fabric collectives meet policy. What go-live criterion fits Domain 4?
- A city wants endurance proof on a new permitting rack before tenant jobs arrive. What Domain 4 activity is required?
- County health NCCL burn-in accumulates XID and link errors past policy thresholds. What should operators do?
- Transit ops debates whether a brief NCCL all-reduce equals full acceptance. How should the contrast be framed?
- Emergency management must burn-in fabric nodes without starving 911 NLP inference. What scheduling approach fits?
- Library NLP runs multi-hour NCCL burn-in and needs early warning of latent GPU faults. What should operators capture?
- A city needs proof that municipal GPUs stay stable under sustained Linpack load. What Domain 4 activity is required?
- County health upgrades cooling and must show the change helped under load. What validation fits?
- Transit ops moves GPU nodes from staging into production queues. What HPL requirement should gate that move?
- Water utility HPL burn-in shows progressive score decay over successive hours. What does that signal?
- Courts OCR must schedule multi-hour HPL burn-in without surprising other change windows. What operational control is required?
- A city wants burn-in that stresses AI-framework paths, not only microbenchmarks. What Domain 4 activity fits?
- County health passed HPL and NCCL yet still sees training-stack faults. Why add NeMo burn-in?
- Transit ops configures NeMo burn-in for HGX-class nodes with finite GPU memory. What sizing rule applies?
- School-district lab sees OOM and faults only during NeMo burn-in after HPL/NCCL passed. What should operators do?
- Housing authority prepares an acceptance package after cluster verification. How should NeMo burn-in evidence be handled?
- A city must validate the municipal training filesystem from GPU nodes before large jobs. What Domain 4 step is required?
- County health storage tests report throughput and latency for the dataset pipeline. How should operators interpret them?
- Transit ops validates AI training storage and must cover resiliency, not only peak IOPS. What should storage tests include?
- Water utility storage tests show capacity and paths that look like local disk only, not the shared training export. What should operators conclude?
- A library consortium plans large corpus ingestion onto its municipal GPU training filesystem. What storage verification step should they complete first?