A software development team uses a single physical server for testing the latest code in multiple environments: development, pre-production, and production. What is the recommended approach to…

Assigning different developers does not inherently provide technical separation or security boundaries on a shared server; it is a process control.

Implementing peer review is a good development practice for code quality and security, but it does not provide runtime isolation or access control between environments on a single server.

Developing and deploying each environment with its own set of software tools might be resource-intensive and doesn't inherently create security isolation; the core issue is the privilege separation on the shared host.

Using different user/group IDs for deploying and running workloads in each environment on a shared server is crucial for basic security. This implements the principle of least privilege, ensuring that actions in one environment do not inadvertently or maliciously affect another by restricting access based on identity.