An enterprise received 80 new WAN Edge serial numbers and chassis numbers from logistics, and SD-WAN Manager shows some devices as staging while new routers cannot join the fabric. The validator is reachable and certificates are valid. Which certificate and device-list action authorizes the routers and clarifies validation states?

The correct action succeeds because authorization to join depends on SD-WAN Manager knowing the logistics-provided serial and chassis numbers, and the sync of valid devices moves already-seen entries from staging to authorized state, which directly explains both symptoms when the validator is reachable and certificates are valid. Synchronizing controllers with the Validator to refresh trusted inventory is standard hygiene for drifted inventories, but it fails by concept of source data because a sync without uploading the 80 new identifiers cannot authorize routers that Manager has never learned. Uploading the authorized list to the Validator is a normal bootstrap step for chassis authorization, but it fails by concept of control location because the stated display and promotion point is SD-WAN Manager while the validator path is already healthy, so the staging versus valid clarification never occurs. Reinstalling the enterprise root chain on Manager is a legitimate PKI remediation for expiry or mistrust, but it fails by concept of trust validity because the scenario explicitly states certificates are valid, leaving the missing authorization unresolved and new routers still unable to authenticate for fabric join. An exam caveat is to separate reachability and cryptographic validity from explicit allowlisting, since reachable and valid often tempts a certificate or connectivity fix when the actual gate is administrative authorization. As a practical check, confirm the uploaded file contains all 80 serial and chassis pairs, then verify Manager shows expected valid count and staging clears after sync before attempting ZTP or manual onboarding.