156-836 · Question #115
What cannot be a reason for DETACHED status of Appliance when running asg monitor command?
The correct answer is C. Appliance installed with R80.20. Option C is correct because the installed software version (R80.20) has no bearing on whether an appliance shows as DETACHED - software version is a static property of the appliance, not a connectivity or communication state indicator. DETACHED status in asg monitor…
Question
What cannot be a reason for DETACHED status of Appliance when running asg monitor command?
Options
- AAppliance reboots
- BAppliance is a member of Security Group, but currently disconnected
- CAppliance installed with R80.20
- DThere's an issue with Downlink cable
How the community answered
(27 responses)- A4% (1)
- B15% (4)
- C74% (20)
- D7% (2)
Explanation
Option C is correct because the installed software version (R80.20) has no bearing on whether an appliance shows as DETACHED - software version is a static property of the appliance, not a connectivity or communication state indicator. DETACHED status in asg monitor specifically reflects that the Security Group Orchestrator (SGO) cannot communicate with the appliance, which a software version alone cannot cause.
Why the distractors are wrong:
- A (Reboot): A rebooting appliance temporarily loses its connection to the SGO, which legitimately triggers DETACHED during the downtime.
- B (Disconnected from Security Group): A member that is physically or logically disconnected cannot maintain its sync/communication channel with the SGO - a classic cause of DETACHED.
- D (Downlink cable issue): A faulty downlink cable breaks the physical network path the appliance uses to communicate, directly causing DETACHED status.
Memory tip: Think "DETACHED = disconnected." Every valid reason (reboot, disconnection, bad cable) involves an interruption to the physical or logical link. A software version number is just a label - it cannot sever a connection, so it can never be the reason.
Topics
Community Discussion
9
Luis F.Dec 12, 2025C is the right answer on this one. The installed version, like R80.20, has nothing to do with DETACHED status in asg monitor because DETACHED is about connectivity and availability issues, things like reboots, disconnected Security Group members, or physical cable problems with the Downlink, not what software version you put on the box.
Dervla O.Dec 14, 2025DETACHED does flag connectivity and availability gaps, but version state matters indirectly when an upgrade leaves a gateway mid-process and the management server loses sync before it reconnects.
Prof. SaraNov 24, 2025Honestly my first instinct was D, because a bad Downlink cable is a physical layer problem and I almost talked myself into thinking that was too obvious to be a listed cause, but then I remembered that DETACHED in asg monitor is specifically about communication and sync state, and a reboot, a disconnected member, or a cable fault all directly disrupt that state, while the installed version of the OS has nothing to do with triggering DETACHED status, making C the one thing that simply cannot be a reason.
Dervla O.Nov 8, 2025Saw this exact trap on my sitting, and it burned about ninety seconds because I kept second-guessing B. The stem is asking what CANNOT cause DETACHED, so you eliminate the real culprits first: a reboot breaks connectivity, a bad Downlink cable kills the link, and a disconnected Security Group member is the textbook case. R80.20 installation version has nothing to do with runtime attachment status, so C falls out cleanly once you frame it as an elimination rather than a recall question.
Prof. SaraNov 11, 2025The elimination frame is solid, but reinforce the habit of anchoring "DETACHED" to the specific runtime states the gateway reports so you are not relying on process of elimination alone when a harder stem makes two distractors look plausible.
Mateus R.Dec 6, 2025A reboot clears and resets the connection state, it would not leave the appliance stuck DETACHED.
Luis F.Dec 7, 2025Hey Mateus, actually the answer is C on this one. A reboot does reset the state but the appliance comes back up and has to re-negotiate its connection with the manager, and if that negotiation fails or times out the appliance can end up stuck in DETACHED state.
Samuel O.Nov 19, 2025Reboots are a managed, expected lifecycle event that the system accounts for, so a temporary reboot would never just leave an appliance sitting in DETACHED, it would cycle back or show a different transitional state. I keep coming back to A because of that, the other three all describe actual communication or connectivity breakdowns that the monitor command would have no way to resolve on its own.
Dervla O.Nov 20, 2025Samuel, the trap in your reasoning is that you are evaluating what the system intends versus what the monitor command actually observes at a point in time, and C is correct because a reboot in progress looks identical to a detached appliance from the monitor's perspective until the cycle completes, which is exactly the kind of transient state the question is testing your ability to recognize.