Cyber Monday 2024! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Google Exam Professional Cloud Architect Topic 5 Question 98 Discussion

Actual exam question for Google's Professional Cloud Architect exam
Question #: 98
Topic #: 5
[All Professional Cloud Architect Questions]

You are working at an institution that processes medical dat

a. 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?

Show Suggested Answer Hide Answer
Suggested Answer: C

https://cloud.google.com/compute/docs/nodes/provisioning-sole-tenant-vms#provision_a_sole-tenant_vm

https://cloud.google.com/compute/docs/nodes/provisioning-sole-tenant-vms#gcloud_2

When you create a VM, you request sole-tenancy by specifying node affinity or anti-affinity, referencing one or more node affinity labels. You specify custom node affinity labels when you create a node template, and Compute Engine automatically includes some default affinity labels on each node. By specifying affinity when you create a VM, you can schedule VMs together on a specific node or nodes in a node group. By specifying anti-affinity when you create a VM, you can ensure that certain VMs are not scheduled together on the same node or nodes in a node group.


Contribute your Thoughts:

Elena
3 days ago
Ah, the old 'let's make everything as manual and complicated as possible' approach. Hard pass, I'm going with C and saving myself a headache.
upvoted 0 times
...
Meaghan
5 days ago
I'm not sure. Should we also consider adding the node group name as a network tag?
upvoted 0 times
...
Helene
6 days ago
I chuckled at the 'node name as a tag' option. It's like they're trying to make our lives harder! C is the way to go, no doubt about it.
upvoted 0 times
...
Kimbery
7 days ago
Haha, trying to use the node name as a tag? That's a good way to end up with a complete mess on your hands. C is the clear choice here.
upvoted 0 times
...
Elroy
7 days ago
Whoa, using individual node names as tags? That's just asking for trouble. Node affinity labels with the group name is the smart move.
upvoted 0 times
...
Fairy
18 days ago
I agree, C is the correct answer. Tagging the instances with the node group name would be way too manual and error-prone.
upvoted 0 times
...
Adolph
19 days ago
Option C is definitely the way to go here. Using node affinity labels with the node group name is the best way to ensure each workload is deployed on the correct dedicated host.
upvoted 0 times
Trinidad
1 days ago
It's important to follow company policies and keep workloads separated on physically separated hardware.
upvoted 0 times
...
Shawnna
3 days ago
I agree, option C is the most efficient way to deploy workloads on dedicated hosts.
upvoted 0 times
...
...
Horace
23 days ago
I agree with Tijuana. It's important to host each workload on the correct node group.
upvoted 0 times
...
Tijuana
25 days ago
I think we should use node affinity labels based on the node group name.
upvoted 0 times
...

Save Cancel
az-700  pass4success  az-104  200-301  200-201  cissp  350-401  350-201  350-501  350-601  350-801  350-901  az-720  az-305  pl-300  

Warning: Cannot modify header information - headers already sent by (output started at /pass.php:70) in /pass.php on line 77