Q: 14
After 30 minutes of inactivity, a GitHub Codespace will:
Options
Discussion
Option D is correct. It just times out after 30 min idle, doesn't restart or delete. A lot of folks confuse timeout with restart, but Codespace sessions are only paused so you can reconnect. If it actually auto-restarted, that'd be way more disruptive. Anyone have docs saying otherwise?
C imo. Some cloud dev tools do restart after a long idle period, so I wouldn't be surprised if Codespaces just does a full restart at 30 minutes too. Not 100 percent sure though, anyone get a different result?
Seriously, why can't Microsoft just call it "suspend" instead of "time out"? Anyway, D
Its C, I think. Some platforms do a restart after inactivity instead of just timing out, and Codespaces could be similar. Not totally sure though, maybe there's a detail I've missed.
I'm thinking C makes sense. After 30 min of doing nothing, the Codespace probably just restarts to clear out unused resources. Not 100% but that seems how some other cloud dev environments behave too.
Option D fits unless you set a custom timeout. In that rare case, it could trigger before or after 30 minutes, but default is to time out. Pretty sure that's what exam wants, unless they specify config changes.
I remember seeing something like this in the official guide-looks like C is the answer.
C/D? Depends how strict they're being. If Codespaces just pause without actually restarting, then D is more accurate. But some folks might read "time out" as "restart." I think D is right for this question, but open to other takes if someone has seen it behave differently.
D , not C. Codespaces only time out after 30 minutes idle, they don't actually restart or delete unless you do it manually. Easy to mix up with other cloud IDE behaviors!
saw pretty similar problem in my exam, in the official practice test, D is correct.
Be respectful. No spam.
