The correct options are You can rename the codespace display name, You can open the codespace in another supported IDE, You can choose a different compute size for the codespace virtual machine, and You can change the default shell used inside the codespace.

Renaming only updates the display name that you see in GitHub and it does not alter the dev container or the project files. This is a simple metadata change so no rebuild is needed.

Opening the same codespace in another supported IDE changes only the client you use to connect. The container keeps running with the same environment which means switching editors does not require a rebuild.

Choosing a different compute size updates the machine type for the running codespace. GitHub stops and restarts the virtual machine while preserving your persistent storage and container state so you do not rebuild the environment.

Changing the default shell is an editor or user preference that affects the integrated terminal. You can set a different shell profile or configure it through settings or dotfiles and this does not require rebuilding the container.

You can replace the operating system that runs the codespace is incorrect. The operating system comes from the dev container image or Dockerfile and changing it means updating the dev container configuration and rebuilding or recreating the codespace.

Full AWS Practitioner Certification Question