Q: 14
After 30 minutes of inactivity, a GitHub Codespace will:
Options
Discussion
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.
Why is anyone considering C here? Codespace doesn't restart, it just pauses after inactivity right?
Its D since after 30 minutes of inactivity, a Codespace just times out to save compute. It doesn’t auto-delete your environment or restart itself. You’d need to reconnect to resume work. Pretty sure about this but correct me if I’m wrong.
Probably D, since the Codespace just times out to save resources. It doesn’t delete your work or auto-commit, it pauses until you reconnect. Similar question popped up in some practice sets.
Be respectful. No spam.
