100% Latest & Updated Google Professional Cloud Architect Practice Test Questions, Exam Dumps & Verified Answers!
30 Days Free Updates, Instant Download!
Question 370
A GKE service experiences occasional memory spikes and engineers need resource evidence without turning on verbose debug logging. Which implementation choice most directly delivers safe profiling enablement?
- Configure service identity and supported profiler instrumentation with performance safeguards
- Enable high-overhead unbounded profiling globally without safeguards
- Allow profiler exports to unauthorized broad users
- Disable all request instrumentation during performance changes
Explanation
Correct Answer
A:Instrumentation should not create uncontrolled production overhead or expose secrets
Incorrect Answers
B:Can perturb service latency. Instrumentation should not create uncontrolled production overhead or expose secrets.
C:May expose diagnostic data. Instrumentation should not create uncontrolled production overhead or expose secrets.
D:Prevents correlation. Instrumentation should not create uncontrolled production overhead or expose secrets.
Question 371
A GKE service experiences occasional memory spikes and engineers need resource evidence without turning on verbose debug logging. Which validation would best establish proof a hot code path is identified?
- Inspect total memory usage alone without a call profile
- Benchmark unrelated network bandwidth as the memory test
- Correlate profiling samples with the affected release and load interval
- Read only one synthetic idle profile
Explanation
Correct Answer
C:A total container memory chart alone does not attribute allocation to code paths
Incorrect Answers
A:Cannot identify allocation site. A total container memory chart alone does not attribute allocation to code paths.
B:Not causal evidence. A total container memory chart alone does not attribute allocation to code paths.
D:Misses load-specific spikes. A total container memory chart alone does not attribute allocation to code paths.
Question 372
A GKE service experiences occasional memory spikes and engineers need resource evidence without turning on verbose debug logging. Which operational action best maintains profiling-driven regression prevention after launch?
- Increase resource requests at every release without code review
- Track representative profiles after releases and fix persistent expensive functions
- Discard profiles when changing versions
- Optimize functions chosen by intuition instead of sample evidence
Explanation
Correct Answer
B:Optimizing the actual dominant path yields more value than arbitrary resource increases
Incorrect Answers
A:Can mask inefficient functions. Optimizing the actual dominant path yields more value than arbitrary resource increases.
C:Loses regression baseline. Optimizing the actual dominant path yields more value than arbitrary resource increases.
D:May not fix dominant cost. Optimizing the actual dominant path yields more value than arbitrary resource increases.
Question 373
A SaaS front end changes daily, but operators need controlled promotion with immediate recovery after a failed release. Which architecture most directly meets the need for progressive release management?
- Use versioned revisions and gradual promotion with automatic health-based rollback controls
- Shift all users to each newly built revision immediately
- Keep no stable fallback version once a canary starts
- Use deployment success as proof the application behaves well
Explanation
Correct Answer
A:Small canaries limit blast radius while a stable version remains available
Incorrect Answers
B:Large blast radius. Small canaries limit blast radius while a stable version remains available.
C:Not rollback-ready. Small canaries limit blast radius while a stable version remains available.
D:Build status is not runtime health. Small canaries limit blast radius while a stable version remains available.
Question 374
A SaaS front end changes daily, but operators need controlled promotion with immediate recovery after a failed release. Which implementation choice most directly delivers promote only approved artifact content?
- Promote mutable images without artifact digest approval
- Pin release artifacts by digest and require quality gates before shifting production traffic
- Disable health gates to speed promotion
- Permit unlogged production releases by any developer
Explanation
Correct Answer
B:Mutable build tags can hide unreviewed bytes behind a familiar version name
Incorrect Answers
A:Reviewed bytes can change. Mutable build tags can hide unreviewed bytes behind a familiar version name.
C:Creates unsafe progression. Mutable build tags can hide unreviewed bytes behind a familiar version name.
D:Authorization gap. Mutable build tags can hide unreviewed bytes behind a familiar version name.
Question 375
A SaaS front end changes daily, but operators need controlled promotion with immediate recovery after a failed release. Which validation would best establish proof automatic rollback works?
- Test only the normal successful canary
- Count version tags but never inject errors
- Inspect a static config file rather than live traffic routing
- Inject a canary error-rate regression and verify automated traffic reversal
Explanation
Correct Answer
D:Healthy deployment on a normal day does not prove the rollback trigger fires
Incorrect Answers
A:Does not prove rollback trigger. Healthy deployment on a normal day does not prove the rollback trigger fires.
B:Not automated recovery evidence. Healthy deployment on a normal day does not prove the rollback trigger fires.
C:May not match actual behavior. Healthy deployment on a normal day does not prove the rollback trigger fires.
Question 376
A SaaS front end changes daily, but operators need controlled promotion with immediate recovery after a failed release. Which operational action best maintains release quality feedback after launch?
- Review failed canaries, rollback time and SLO impact to improve promotion policy
- Wait for weekly customer reports before undoing a bad release
- Delete previous stable artifact after canary starts
- Ignore failed canary gates as transient without investigation
Explanation
Correct Answer
A:Release management should turn failures into concrete guardrail improvements
Incorrect Answers
B:Extends impact. Release management should turn failures into concrete guardrail improvements.
C:Removes rollback route. Release management should turn failures into concrete guardrail improvements.
D:Risk repeated incident. Release management should turn failures into concrete guardrail improvements.
Question 377
A mobile backend team has conflicting hotfix and feature changes and needs an auditable production release timeline. Which architecture most directly meets the need for controlled source-to-production history?
- Push emergency changes without any review identity
- Use mutable branch names with no build digest mapping
- Permit every production operator to alter immutable release history
- Use a release pipeline that records approved commit, artifact and target environment
Explanation
Correct Answer
D:Every production change should map to a reviewable immutable source revision
Incorrect Answers
A:Loses accountability. Every production change should map to a reviewable immutable source revision.
B:Cannot trace hotfix bytes. Every production change should map to a reviewable immutable source revision.
C:Undermines audit trail. Every production change should map to a reviewable immutable source revision.
Question 378
A mobile backend team has conflicting hotfix and feature changes and needs an auditable production release timeline. Which implementation choice most directly delivers clear emergency hotfix lane?
- Define emergency approvals and independent retrospective review without bypassing all gates
- Give permanent emergency override to all engineers
- Skip retrospective review after urgent deploys
- Treat a ticket number as sufficient deployment authorization regardless of actor
Explanation
Correct Answer
A:Urgency changes the timing of review, not accountability for production changes
Incorrect Answers
B:Becomes a standing bypass. Urgency changes the timing of review, not accountability for production changes.
C:No separation check. Urgency changes the timing of review, not accountability for production changes.
D:Not accountable. Urgency changes the timing of review, not accountability for production changes.
Question 379
A mobile backend team has conflicting hotfix and feature changes and needs an auditable production release timeline. Which validation would best establish proof of approved emergency hotfix promotion?
- Check only the deployed commit hash without verifying its emergency approver
- Inspect deployment timestamps without the temporary emergency permissions used
- Check service uptime and close the hotfix ticket without comparing approval records
- Inspect emergency approval identities, time-limited bypass records, and the deployed hotfix revision
Explanation
Correct Answer
D:A closed incident ticket alone does not establish that the emergency exception was authorized and reconciled
Incorrect Answers
A:Does not establish that an exceptional promotion was authorized. A closed incident ticket alone does not establish that the emergency exception was authorized and reconciled.
B:Does not prove bypass privileges were controlled. A closed incident ticket alone does not establish that the emergency exception was authorized and reconciled.
C:A healthy service does not establish authorized emergency change. A closed incident ticket alone does not establish that the emergency exception was authorized and reconciled.
Question 380
A mobile backend team has conflicting hotfix and feature changes and needs an auditable production release timeline. Which operational action best maintains ongoing release governance after launch?
- Close incident as soon as hotfix ships with no audit reconciliation
- Keep no prior production artifact for rollback
- Monitor unreviewed hotfixes and reconcile emergency access after incidents
- Ignore release logging failures during on-call response
Explanation
Correct Answer
C:Temporary deployment privileges must not become permanent hidden bypasses
Incorrect Answers
A:May leave bypass permissions. Temporary deployment privileges must not become permanent hidden bypasses.
B:Weak recovery. Temporary deployment privileges must not become permanent hidden bypasses.
D:Loses evidence. Temporary deployment privileges must not become permanent hidden bypasses.
Google Cloud Certified - Professional Cloud Architect (Professional Cloud Architect) Practice Tests