Based on the default settings for the Alcatel-Lucent 7750 SR, when a policy change is made and committed, what action is required by the user for the change to take effect?

Question

Options

• AExecute a command to re-evaluate all routes in the Local-RIB against the configured export policies.
• BExecute a command to re-evaluate all routes in the RIB-In against the configured import policies.
• CExecute a command to reset the BGP session with the affected peer or peers.
• DNo further action is required.

• B
  6% (1)
• D
  94% (16)

Explanation

On the Alcatel-Lucent 7750 SR, the SR-OS platform automatically re-evaluates affected routes the moment a policy change is committed - no additional user action is needed, making D correct. This "auto-apply on commit" behavior is a core design feature of SR-OS, distinguishing it from some other vendors where you must explicitly trigger re-evaluation.

Why the distractors are wrong:

• A is wrong because manually triggering a Local-RIB re-evaluation against export policies is unnecessary - SR-OS handles this automatically on commit.
• B is wrong for the same reason - RIB-In re-evaluation against import policies also happens automatically without a separate command.
• C is wrong because resetting a BGP session is a disruptive action that tears down and rebuilds the peering relationship; it is never required simply to apply a policy update on the 7750 SR.

Memory tip: Think "commit = complete" on the 7750 SR. Unlike platforms where a policy change is a two-step process (edit, then trigger), SR-OS treats the commit itself as the trigger - one action, done.

No community discussion yet for this question.