Why is it important to keep ROA management aligned with prefix origination changes?

• A. To ensure ROA entries remain accurate as prefixes or ASNs change
• B. ROA entries automatically update with a policy
• C. ROA changes never affect validation
• D. ROAs are immutable

Answer: (B)

Keeping ROA management aligned with prefix origination changes is essential so that route validation stays accurate as network configurations evolve. An ROA states which ASN may originate a given prefix; when that origination changes—due to re-homing, traffic engineering, or prefix reassignment—the ROA must reflect the new origin for validation to remain trustworthy. Using policy-driven automation to update ROAs means these changes are applied consistently and quickly, reducing gaps where a valid route could be wrongly rejected or a rogue route could appear valid. This automated alignment is preferable to manual updates, which are prone to delays and human error. While it might seem that ROAs are immutable or that changes don’t affect validation, in reality, misaligned ROAs undermine the purpose of RPKI and can lead to dropped legitimate traffic or accepted illegitimate routes.