I'm a bit confused by the wording of the question. Does "existing standalone FortiSwitch configuration" mean I need to preserve the current settings, or can I make changes as long as I switch to FortiLink management?
Okay, I think I've got it. The key is to maintain the existing standalone FortiSwitch configuration while transitioning to FortiLink management. Option B looks like the way to go.
Creating a prebuilt task entity could be a good way to capture those out-of-scope intents. That might give us more control over how the model handles them.
I think the answer is C) FortiGate will automatically save the existing FortiSwitch configuration during the Forti-link management process. It makes sense to me.
C is interesting, but I'm not sure I trust the FortiGate to automatically handle the configuration during the transition. Better to be safe and go with B.
Option B seems to be the way to go. Enabling FortiLink before the authorization process sounds like the logical step to maintain the existing configuration.
Oliva
3 months agoVelda
3 months agoLanie
3 months agoLouvenia
4 months agoHollis
4 months agoAnnalee
4 months agoAlishia
4 months agoMelissa
4 months agoAudra
5 months agoDean
5 months agoTheola
5 months agoJeffrey
5 months agoWilliam
5 months agoIzetta
5 months agoCherry
5 months agoDusti
5 months agoMan
2 years agoKami
2 years agoMeaghan
1 year agoEthan
1 year agoNatalie
1 year agoRefugia
2 years agoMariko
2 years agoGlendora
2 years agoRoxane
2 years agoValda
2 years agoJaime
2 years agoDaron
2 years agoYuette
2 years agoMargart
2 years agoLourdes
2 years agoNoah
2 years agoWalker
2 years agoTess
2 years agoRebbecca
2 years agoJosefa
2 years agoRebbecca
2 years ago