Migrating Workloads to Physically Separated Hardware
Question
You are working at an institution that processes medical data.
You are migrating several workloads onto Google Cloud.
Company policies require all workloads to run on physically separated hardware, and workloads from different clients must also be separated.
You created a sole-tenant node group and added a node for each client.
You need to deploy the workloads on these dedicated hosts.
What should you do?
Answers
Explanations
Click on the arrows to vote for the correct answer
A. B. C. D.C.
https://cloud.google.com/compute/docs/nodes/provisioning-sole-tenant-vmsIn this scenario, the organization processing medical data requires that all workloads run on physically separated hardware, and workloads from different clients must also be separated. To achieve this, the solution architect created a sole-tenant node group and added a node for each client.
To deploy workloads on dedicated hosts, one option is to use node affinity labels when creating Compute Engine instances. Node affinity labels allow you to specify the characteristics of the physical hosts that an instance should run on.
Option A suggests adding the node group name as a network tag when creating Compute Engine instances to host each workload on the correct node group. However, network tags are used to apply firewall rules to instances based on the tags, and are not used to specify the host that an instance should run on.
Option B suggests adding the node name as a network tag when creating Compute Engine instances to host each workload on the correct node. However, network tags are not used to specify the host that an instance should run on.
Option C suggests using node affinity labels based on the node group name when creating Compute Engine instances to host each workload on the correct node group. This is the correct option as it allows you to specify that the instances should be placed on the hosts that belong to a particular node group. Node affinity labels are key-value pairs that are applied to instances and nodes, and can be used to control where instances run in a cluster of nodes.
Option D suggests using node affinity labels based on the node name when creating Compute Engine instances to host each workload on the correct node. This option is not ideal because it specifies a particular node by name, which can be problematic if that node goes down or is removed from the group.
In summary, the correct answer is option C, which suggests using node affinity labels based on the node group name when creating Compute Engine instances to host each workload on the correct node group.
