The correct options are Update the display name of a codespace for easier identification, Pick a different compute size for the codespace virtual machine, Set or switch the shell used in the terminal within a codespace, and Specify the geographic region where new codespaces are provisioned.

Renaming a codespace is supported and lets teams keep environments easy to recognize across multiple projects or tasks. You can change a codespace name from the GitHub interface or through supported tools so lists remain clear as work evolves.

Choosing a machine type is a built in capability that allows you to align CPU and memory with the workload. You can start with a smaller configuration and later change to a larger one if builds or tests need more resources.

Switching the terminal shell is also supported. You can select bash, zsh, or another shell through the editor’s terminal profiles or by configuring your dotfiles so contributors work in a familiar command line environment.

Setting a region for new environments is available so you can place codespaces closer to your developers or data and reduce latency. Organizations can also control which regions are allowed and set defaults to keep provisioning consistent.

Switch the host operating system to macOS or Windows is incorrect because GitHub Codespaces run on Linux based virtual machines and you cannot change the underlying host operating system to macOS or Windows.

Choose a Google Cloud project where the codespace runs and bills to is incorrect because Codespaces are hosted on GitHub’s infrastructure and billed through GitHub’s billing on Azure infrastructure rather than through Google Cloud projects.

Full AWS Practitioner Certification Question