WGU D607 - Cloud Databases
Task 2: Cloud Database Design and Implementation
CedarBridge Outfitters | Google Cloud SQL for PostgreSQL
October 2026
Contents
Executive Summary 2
A. Business Requirements and Implementation Objectives 2
A1. Business problem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
A2. Implementation objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
A3. Requirements traceability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
B. Cloud Platform and Implementation Environment 3
B1. Platform selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
B2. Target configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
B3. Reproducible deployment sequence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
C. Database Design 4
C1. Relational model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
C2. Entity relationships . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
C3. Primary and foreign keys . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
C4. Data types and physical design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
C5. Normalization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
C6. Index strategy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
D. Database Structure Implementation 6
D1. Schema creation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
D2. Core table definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
D3. Transaction processing considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
E. Database Population 7
E1. Synthetic records . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
E2. Customer and product examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
E3. Inventory sample . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
E4. Orders, payment events and returns . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
F. SQL Data Retrieval and Reporting 8
F1. Record-count verification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
F2. Order status distribution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
F3. Gross order-line values by category . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
F4. Inventory availability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
F5. Header-to-line reconciliation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
F6. Captured payments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
G. Data Integrity and Validation 9
G1. Database-enforced checks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
G2. Cross-record checks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
1
, WGU D607 | CLOUD DATABASES TASK 2
G3. Local compatibility-check results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
H. Security and Access Control 10
H1. Authentication and authorization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
H2. Networking and credential protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
H3. Scope of security demonstration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
I. Backup, High Availability, and Recovery 10
I1. Backups and point-in-time recovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
I2. Zonal availability and regional recovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
I3. Recovery validation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
J. Cloud Deployment Evidence Plan 11
K. Evaluation of the Proposed Implementation 11
L. Conclusion 11
References 11
Appendix A. Complete PostgreSQL Schema and Synthetic Records 12
Appendix B. Complete SQL Validation and Reporting Queries 13
Appendix C. Acceptance Tests and Assessment Coverage 14
C1. Implementation acceptance checks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
C2. Assessment-related coverage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Scope and evidence statement. CedarBridge Outfitters is a fictional organization; all records are synthetic.
This original implementation study extends the Task 1 architecture. The complete current WGU Task 2 scenario
and rubric were unavailable. The accompanying SQL scripts were checked using a local SQLite-compatible
relational test, not deployed to Google Cloud SQL. Cloud provisioning, execution screenshots, and PostgreSQL-
specific tests are therefore proposed activities, not claimed accomplishments.
Executive Summary
CedarBridge Outfitters requires a centralized database environment that supports customer accounts, products, store inven-
tory, orders, payment-status records, and returns. Its distributed systems create inconsistencies in inventory visibility and
complicate accurate reporting. Task 1 recommended Google Cloud Platform (GCP), with Cloud SQL for PostgreSQL as the
authoritative transactional database and BigQuery as a separate analytical service.
This implementation translates that architecture into a relational schema comprising eight related tables: customers, prod-
ucts, locations, inventory, customer_orders, order_items, payment_transactions, and returns. Primary and for-
eign keys maintain entity relationships; uniqueness and check constraints enforce important business rules. Six supporting
indexes address anticipated joins and lookup patterns. A reproducible SQL script creates the schema and loads 41 synthetic
records; a second script contains eight validation and business-reporting queries.
The demonstration data represents five customer orders, including three paid orders, one fulfilled order, and one pending
order. Four captured payment records total $815, and a fifth authorization is not counted as a capture. A local SQLite-
compatible relational check found consistent order totals and no invalid inventory rows. That result establishes an internal
consistency baseline; it does not certify execution in PostgreSQL or deployment in Cloud SQL. Production implementation
still requires authorized cloud provisioning, role configuration, actual SQL execution, and evidence capture.
A. Business Requirements and Implementation Objectives
A1. Business problem
CedarBridge operates retail stores, distribution centers, and an online sales channel. To execute sales correctly, it must connect
customer profiles to orders, order lines to products, and location-specific inventory to available stock. Historical order prices
must be preserved if product catalog prices change. The system must also identify the state of payment transactions and
record returns without losing their link to the original purchase.
2
Task 2: Cloud Database Design and Implementation
CedarBridge Outfitters | Google Cloud SQL for PostgreSQL
October 2026
Contents
Executive Summary 2
A. Business Requirements and Implementation Objectives 2
A1. Business problem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
A2. Implementation objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
A3. Requirements traceability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
B. Cloud Platform and Implementation Environment 3
B1. Platform selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
B2. Target configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
B3. Reproducible deployment sequence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
C. Database Design 4
C1. Relational model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
C2. Entity relationships . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
C3. Primary and foreign keys . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
C4. Data types and physical design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
C5. Normalization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
C6. Index strategy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
D. Database Structure Implementation 6
D1. Schema creation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
D2. Core table definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
D3. Transaction processing considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
E. Database Population 7
E1. Synthetic records . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
E2. Customer and product examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
E3. Inventory sample . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
E4. Orders, payment events and returns . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
F. SQL Data Retrieval and Reporting 8
F1. Record-count verification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
F2. Order status distribution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
F3. Gross order-line values by category . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
F4. Inventory availability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
F5. Header-to-line reconciliation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
F6. Captured payments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
G. Data Integrity and Validation 9
G1. Database-enforced checks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
G2. Cross-record checks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
1
, WGU D607 | CLOUD DATABASES TASK 2
G3. Local compatibility-check results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
H. Security and Access Control 10
H1. Authentication and authorization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
H2. Networking and credential protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
H3. Scope of security demonstration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
I. Backup, High Availability, and Recovery 10
I1. Backups and point-in-time recovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
I2. Zonal availability and regional recovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
I3. Recovery validation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
J. Cloud Deployment Evidence Plan 11
K. Evaluation of the Proposed Implementation 11
L. Conclusion 11
References 11
Appendix A. Complete PostgreSQL Schema and Synthetic Records 12
Appendix B. Complete SQL Validation and Reporting Queries 13
Appendix C. Acceptance Tests and Assessment Coverage 14
C1. Implementation acceptance checks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
C2. Assessment-related coverage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Scope and evidence statement. CedarBridge Outfitters is a fictional organization; all records are synthetic.
This original implementation study extends the Task 1 architecture. The complete current WGU Task 2 scenario
and rubric were unavailable. The accompanying SQL scripts were checked using a local SQLite-compatible
relational test, not deployed to Google Cloud SQL. Cloud provisioning, execution screenshots, and PostgreSQL-
specific tests are therefore proposed activities, not claimed accomplishments.
Executive Summary
CedarBridge Outfitters requires a centralized database environment that supports customer accounts, products, store inven-
tory, orders, payment-status records, and returns. Its distributed systems create inconsistencies in inventory visibility and
complicate accurate reporting. Task 1 recommended Google Cloud Platform (GCP), with Cloud SQL for PostgreSQL as the
authoritative transactional database and BigQuery as a separate analytical service.
This implementation translates that architecture into a relational schema comprising eight related tables: customers, prod-
ucts, locations, inventory, customer_orders, order_items, payment_transactions, and returns. Primary and for-
eign keys maintain entity relationships; uniqueness and check constraints enforce important business rules. Six supporting
indexes address anticipated joins and lookup patterns. A reproducible SQL script creates the schema and loads 41 synthetic
records; a second script contains eight validation and business-reporting queries.
The demonstration data represents five customer orders, including three paid orders, one fulfilled order, and one pending
order. Four captured payment records total $815, and a fifth authorization is not counted as a capture. A local SQLite-
compatible relational check found consistent order totals and no invalid inventory rows. That result establishes an internal
consistency baseline; it does not certify execution in PostgreSQL or deployment in Cloud SQL. Production implementation
still requires authorized cloud provisioning, role configuration, actual SQL execution, and evidence capture.
A. Business Requirements and Implementation Objectives
A1. Business problem
CedarBridge operates retail stores, distribution centers, and an online sales channel. To execute sales correctly, it must connect
customer profiles to orders, order lines to products, and location-specific inventory to available stock. Historical order prices
must be preserved if product catalog prices change. The system must also identify the state of payment transactions and
record returns without losing their link to the original purchase.
2