Which statement best describes how SAD handles CSA boundary updates for stops affected by MLD changes?

Which statement best describes how SAD handles CSA boundary updates for stops affected by MLD changes?

• A. SAD will auto-adjust any stop regardless of context.
• B. SAD will auto-adjust boundaries only for stops whose MLD changes CSA assignment according to current boundaries.
• C. SAD will not adjust any boundaries automatically.
• D. SAD requires manual approval for each change.

Answer: (B)

SAD updates boundaries only when an MLD change would actually move a stop into a different CSA under the current boundary layout. In practice, when an MLD update occurs, SAD checks if that change would cause a CSA reassignment for that stop. If it would, the boundary is updated automatically to reflect the new CSA. If the MLD change doesn’t cross a boundary and the stop remains in the same CSA, nothing changes automatically. This keeps updates focused and avoids unnecessary boundary churn. Why this fits best: it captures the idea that automatic updates are conditional on real cross-boundary impact, not applied to every stop or left entirely manual.

SAD updates boundaries only when an MLD change would actually move a stop into a different CSA under the current boundary layout. In practice, when an MLD update occurs, SAD checks if that change would cause a CSA reassignment for that stop. If it would, the boundary is updated automatically to reflect the new CSA. If the MLD change doesn’t cross a boundary and the stop remains in the same CSA, nothing changes automatically. This keeps updates focused and avoids unnecessary boundary churn.

Why this fits best: it captures the idea that automatic updates are conditional on real cross-boundary impact, not applied to every stop or left entirely manual.