ANS-C01 deep review — September 28, 2026

The entire guide, 177 detailed knowledge/skill bullets across 16 tasks, root blueprint and in-scope list were reviewed. Broad domains match the accepted baseline. The English credential page still gives December 31 retirement, while the Japanese page gives August 25; language-specific booking needs confirmation. No replacement certification was named. The detailed blueprint's multiple-response/matching format also differs from the credential overview.

Changes for learners

Correct the minimum passing score from 700 to 750. Add domain-registration responsibilities, Kubernetes load-balancer reconciliation and explicit multicast membership/attachment limits. Repair the body and answer guide's TGW association rule: policy-table association is an alternative, with system-entry precedence, customer first-match behavior and unmatched drop. Preserve the Reachability Analyzer limitation.

The scope list still names App Mesh, whose official notice says support ends September 30 and resources/console become inaccessible afterward. Flag this distinct service event. Add Regional NAT automatic/manual behavior, private-NAT limits, expansion delay and connection-reset migration caveats. These product updates do not establish revised exam weights.

Four original worked decisions cover policy versus route selection, longest prefix, MTU and bandwidth-delay product. Eight local assertions passed. Preserve 42 answer explanations and eight proposed labs. Qualify paid resource metadata and keep Places to learn last.

Article and validation boundaries

The Regional NAT introduction is accepted for routing/inspection context; its absolute security/port-protection wording is not adopted. Current service documentation supplies the limitations. No AWS traffic, controller deployment, NAT conversion or paid lesson was executed. Independent human review remains pending.

The operational receipt records fetches, hashed objectives, section mapping, contradictions and repository/site gates. Candidate snapshots were compared without advancing accepted files. A guessed policy-document path returned a 200 shell; the canonical link was resolved from the source page and only that usable source was registered.