Prepare and test your skills

Prepare and test your skills

Free sample question with answers and detailed explanation below. The Professional Cloud Network Engineer practice bank has an additional 2,437 practice questions.Try 10 free realistic questions: instant score, no credit card, and no account required.
You are troubleshooting two cross-project VPC spokes in a Network Connectivity Center (NCC) environment where auto-accept is disabled:
spoke-app-a: An administrator proposed adding 18 exclude-export-ranges CIDRs, and the hub administrator accepted the proposal. gcloud network-connectivity spokes describe shows state: ACTIVE and reason UPDATE_FAILED.spoke-legacy-b: Previously attached to a deleted hub (hub-old), it shows state: OBSOLETE. Immediately after deleting spoke-legacy-b, attaching its VPC to a new hub (hub-prod) failed.What explains these operational states, and how should you resolve both issues?
In Network Connectivity Center, a spoke's operational state determines whether it actively participates in hub route exchange, while the deletion cool-down period prevents race conditions when migrating a VPC network's bindings between distinct hubs.
spoke-app-a: When a spoke update fails with state: ACTIVE and reason UPDATE_FAILED, the spoke remains fully operational using its previous configuration. Route exchange is not suspended, and deleting the spoke would cause an unnecessary production outage.OBSOLETE cool-down: Deleting an OBSOLETE spoke does not exempt its VPC network from the mandatory 10-minute cool-down period when attaching that VPC to a different hub (hub-prod). Immediate creation fails until the cool-down timer expires.ACTIVE state guarantee: Any spoke in the ACTIVE state—even with UPDATE_FAILED, UPDATE_REJECTED, or UPDATE_PENDING_REVIEW—continues forwarding dataplane traffic.INACTIVE state behavior: Only INACTIVE spokes (PENDING_REVIEW or REJECTED) and OBSOLETE spokes lack operational hub connectivity.spoke-app-a were in an INACTIVE state with a misconfigured VPC binding that required replacement, and spoke-legacy-b's VPC were being re-attached to the same hub rather than a new hub (hub-prod).
Network Connectivity Center uses distinct state reasons on an ACTIVE spoke to differentiate between pending administrative approval and failed control-plane execution during the cross-project spoke update lifecycle.
UPDATE_FAILED: The UPDATE_FAILED reason explicitly means that the hub administrator has already accepted the update proposal, but the update could not be applied—in this case because specifying 18 export filters exceeds the maximum limit of 16 export filters per VPC spoke.hub-prod. Attempting to approve it again will not resolve the configuration error; the spoke administrator must submit a new compliant update proposal with 16 or fewer filters.UPDATE_PENDING_REVIEW: Indicates an ACTIVE spoke has a proposed property change that the hub administrator has not yet accepted or rejected.UPDATE_FAILED: Indicates an ACTIVE spoke had its update proposal accepted by the hub administrator, but execution failed due to quota, limit, or validation errors.UPDATE_REJECTED: Indicates an ACTIVE spoke had its update proposal explicitly rejected by the hub administrator.spoke-legacy-b before attaching the VPC to hub-prod is correct, the incorrect diagnosis of spoke-app-a makes this option invalid.gcloud network-connectivity spokes describe for spoke-app-a had returned state: ACTIVE with reason UPDATE_PENDING_REVIEW rather than UPDATE_FAILED, indicating that the hub administrator simply needed to review and accept the proposed filter changes.
Cross-project VPC spokes support in-place update proposals for modifying export filters without disrupting active traffic, whereas the OBSOLETE state represents an irreversible detachment caused by the deletion of the spoke's parent hub.
include-export-ranges and exclude-export-ranges on existing ACTIVE cross-project VPC spokes via spoke update proposals. spoke-app-a failed because 18 filters exceeded the 16-filter limit, not because updates are unsupported.OBSOLETE state: Once hub-old is deleted and spoke-legacy-b enters OBSOLETE, its state never changes and its hub reference cannot be patched. The spoke can only be deleted.include-export-ranges and exclude-export-ranges (up to 16 filters), not Cloud Router BGP policies.OBSOLETE immutability: An OBSOLETE spoke cannot be repaired, reparented to hub-prod, or restored by recreating a hub with the old name.You were managing BGP prefix advertisements for a hybrid spoke on Cloud Router rather than subnet export filters on a VPC spoke, and hub-old had not already been deleted.
In Network Connectivity Center (NCC), spoke status is tracked using a spoke state (ACTIVE, INACTIVE, or OBSOLETE) paired with a state reason. When a cross-project VPC spoke is updated, the spoke remains in the ACTIVE state while the control plane validates and applies the accepted changes against NCC quotas and limits. When a hub is deleted, all remaining spokes attached to that hub transition to the terminal OBSOLETE state.
spoke-app-a (ACTIVE / UPDATE_FAILED): The ACTIVE state confirms that spoke-app-a is still operational and exchanging routes using its previous valid configuration. However, UPDATE_FAILED indicates that although the hub administrator accepted the proposal, applying it failed because NCC VPC spokes support a maximum of 16 export filters. Reducing the exclude-export-ranges list to 16 or fewer CIDRs (and ensuring no VPC subnet is larger than a specified filter) and submitting a new update proposal allows the update to succeed.spoke-legacy-b (OBSOLETE): Once a spoke becomes OBSOLETE because hub-old was deleted, its state never changes and it can only be deleted. After deleting a spoke, you must wait for a cool-down period of at least 10 minutes before attaching that same VPC network to a different hub (hub-prod).ACTIVE with UPDATE_FAILED: Existing dataplane connectivity continues without interruption using the last committed spoke properties.OBSOLETE terminal state: Triggered when the parent hub is deleted; the reasons field is empty and the spoke cannot be reactivated or reparented.Unlike options that unnecessarily delete an operational ACTIVE spoke or mistake UPDATE_FAILED for an unreviewed proposal, this approach preserves production traffic on spoke-app-a while correcting the exact filter-limit violation and honoring the mandatory cross-hub cool-down timer for spoke-legacy-b.
Answer them yourself and get your score the moment you finish. No account needed.
Full access includes
Keep the momentum going with these hand-picked practice scenarios
Last updated Validated