Prepare and test your skills

Prepare and test your skills

Free sample question with answers and detailed explanation below. The Professional Cloud Database Engineer practice bank has an additional 769 practice questions.Try 10 free realistic questions: instant score, no credit card, and no account required.
Your team is preparing to perform an in-place major version upgrade on a production Cloud SQL for PostgreSQL 15 instance to PostgreSQL 16. Before modifying production, you need to address the following environment details and requirements:
force_parallel_mode and vacuum_defer_cleanup_age.Which pre-upgrade strategy should you follow?
Attempting an in-place major version upgrade directly on production without resolving incompatible flags or testing in staging relies entirely on automated error handling and rollback mechanisms during a live maintenance window.
vacuum_defer_cleanup_age or force_parallel_mode is enabled, the major version upgrade is blocked and fails until you manually delete those flags.pg_ivm), and views referencing changed system catalogs must be resolved before the upgrade can succeed.If you had already completed release-note analysis, removed blocking flags and incompatible objects, and validated the upgrade in a cloned staging environment—leaving only the final production execution during a low-traffic window.
This approach establishes a manual backup for safety but defers schema and extension compatibility fixes until after the production upgrade and assumes database flag defaults remain unchanged across major versions.
pg_stat_activity) cause pre-upgrade check errors and block the upgrade. You must drop those views before upgrading and recreate them afterward.ALTER EXTENSION ... UPDATE) after the upgrade.ANALYZE after the upgrade is essential so the query planner has accurate statistics, but it does not substitute for pre-upgrade compatibility testing.If the question asked specifically about post-upgrade tasks—such as updating supported extension catalogs, recreating previously dropped views, and running ANALYZE—after a successful staging test and pre-upgrade remediation had already occurred.
This approach attempts to isolate precheck overhead onto a read replica, keep legacy database flags active to avoid query planner changes, and depend on the post-upgrade backup as a rollback mechanism.
RUNNING state. Executing a precheck against a read replica is not supported and will fail.force_parallel_mode (renamed to debug_parallel_query in PostgreSQL 16) and vacuum_defer_cleanup_age (deprecated in PostgreSQL 16) prevents the major version upgrade from running. Furthermore, force_parallel_mode is a debugging parameter, not a stable production optimizer setting.No valid scenario supports running the upgrade precheck on a read replica or using a post-upgrade backup to revert to an earlier major version.
vacuum_defer_cleanup_age and force_parallel_mode, run the upgrade precheck, and test a dry-run upgrade on a cloned staging instance after verifying backups.A structured pre-upgrade compatibility and validation workflow combines engine release-note analysis, configuration remediation, automated readiness checks, and isolated dry-run testing before any production change is executed. In Cloud SQL for PostgreSQL, major version upgrades modify internal system catalogs and binary formats, making proactive verification essential.
vacuum_defer_cleanup_age is deprecated and force_parallel_mode is renamed to debug_parallel_query. Removing both flags prior to the upgrade prevents validation errors.pg_stat_activity), surfacing issues before downtime begins.Unlike approaches that skip staging dry runs, leave deprecated flags intact, or target read replicas for prechecks, this strategy resolves every known blocker ahead of time and validates both schema compatibility and application stability in isolation.
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 Validated