Prepare and test your skills

Prepare and test your skills

Free sample question with answers and detailed explanation below. The Associate Cloud Engineer practice bank has an additional 2,014 practice questions.Try 10 free realistic questions: instant score, no credit card, and no account required.
An organization is deploying an internal batch-processing application on Google Cloud Compute Engine. The workload requires a non-standard configuration of 6 vCPUs and 26 GB of RAM to operate efficiently without over-allocating unused resources.
Which requirement must the cloud engineer satisfy when configuring the custom machine type for this VM instance?
Arbitrary sizing assumes that virtual machine creation on Google Cloud allows totally unrestricted entry of odd vCPU numbers (such as 3, 5, or 7 vCPUs) and arbitrary RAM values without any upper or lower bounds per core.
Compute Engine possessed no architectural hardware bounds, validation schemas, or hypervisor memory-to-core ratios when creating custom compute instances.
Custom machine types in Google Cloud Compute Engine enable administrators to independently configure the exact number of vCPUs and amount of system memory for a virtual machine. This flexibility prevents overprovisioning compute resources when an application does not align with predefined machine shape ratios.
When creating a custom machine type (such as within the N1, N2, or E2 series), Compute Engine enforces fundamental platform validation rules:

Configuring the instance with 6 vCPUs and 26 GB of RAM (which is 26,624 MB, a valid multiple of 256 MB) satisfies both the vCPU and memory ratio rules without forcing the administrator to purchase an expensive predefined 8-vCPU or 32 GB standard instance.
Power-of-two core allocation refers to selecting compute configurations that double sequentially (such as 1, 2, 4, 8, 16, 32, 64). Many predefined machine types follow this pattern in their standard catalog offerings.
The engineer were restricted exclusively to standard predefined machine type tiers (such as n2-standard-4 or n2-standard-8) rather than utilizing Compute Engine's custom machine type capability.
Configuring virtual machine capacity strictly in whole gigabyte (1024 MB) increments with a rigid 4 GB per vCPU cap represents an assumption derived from traditional fixed virtualization templates rather than Google Cloud's actual custom machine specification rules.
A virtualization platform strictly enforced integer gigabyte memory stepping and hard-capped standard instance shapes at a 1:4 vCPU-to-memory ratio without supporting custom machine types or extended memory configurations.
Answer them yourself and get your score the moment you finish. No account needed.
Full access includes
Keep the momentum going with these hand-picked practice scenarios
Last updated