Free Google Professional Cloud DevOps Actual Exam Questions - Question 10 Discussion
You use Cloud Build to build your application. You want to reduce the build time while minimizing
cost and development effort. What should you do?
Maybe C—smaller steps can run in parallel and spot slow parts fast.
C is worth considering here because breaking the build into smaller steps can help identify bottlenecks and potentially run some steps in parallel, speeding up the overall process without needing extra resources. It also doesn’t increase costs like bigger VMs would, and it’s less complex than setting up Jenkins agents. Plus, smaller steps can sometimes let you skip unnecessary parts if nothing changed there, indirectly reducing build time. This approach keeps things simple while still aiming to cut down total execution time, which fits the goal of minimizing development effort and cost.
The build time can definitely be reduced by caching as in A, but that assumes your build process generates cacheable intermediate artifacts. If your build isn’t very modular or doesn’t create reusable outputs, caching won’t help much. D is a simpler approach because just upgrading the VM size can speed up everything without changing the build steps or adding overhead. Plus, it’s easier to manage since you don’t have to set up or maintain caches, which fits the “minimizing development effort” part of the question well.
A imo, caching intermediate artifacts is a straightforward way to cut build times since it avoids rebuilding things that haven’t changed. Unlike just throwing more power at the VM like in D, caching doesn’t necessarily hike costs much and keeps your build pipeline simple. Plus, Cloud Build supports this natively, so it needs minimal extra work compared to setting up Jenkins agents or breaking down builds into smaller steps.
Cloud Build’s built-in caching makes A effective without extra setup or cost.
A/D? I get why D is appealing for speed, but bigger VMs can ramp up costs and might be overkill for smaller projects. A seems smarter cost-wise since caching avoids rebuilding unchanged parts, so you trim build time without throwing more hardware at it. Jenkins agents (B) would mean extra setup and cost, plus C might not help if steps are already optimized. So between A and D, I’d pick A for balancing faster builds and keeping costs low.
It’s D because bigger VMs can speed up builds without needing to change the build logic or add complexity, which keeps costs predictable and development effort low.
A imo, caching artifacts in Cloud Storage cuts time and cost without complicating builds.
It’s A, caching saves time without extra cost or complex setups.
Probably D makes sense since bigger VMs can handle tasks faster, cutting build time without adding complex setup like Jenkins or caching layers. It might cost more but minimal dev effort compared to other options.
Option A sounds best here since caching intermediate artifacts in Cloud Storage can speed up builds without extra cost or complexity. Option B might add more overhead, and D increases cost. C doesn’t really reduce build time effectively.