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 migrating an Oracle 19c database to Cloud SQL for PostgreSQL using Database Migration Service (DMS) conversion workspaces. After the initial deterministic schema conversion, your schema analysis reveals several requirements to maintain functional parity with the application:
NUMBER columns defined without precision must convert to PostgreSQL INTEGER instead of DECIMAL or BIGINT.dates_and_times in the events table must convert to TIMESTAMP.Which approach should you use to apply these DDL and data type conversions?
The interactive SQL editor inside a DMS conversion workspace is a built-in code editor that lets database engineers review and modify generated PostgreSQL DDL and PL/pgSQL statements before applying the converted schema to the destination database.
This approach fails because DMS restricts which database object types can be modified in the built-in editor. Tables, schemas, and user-defined object types are explicitly excluded from interactive editing. As a result, you cannot open the events table in the SQL editor to change the dates_and_times column to TIMESTAMP, rewrite NUMBER columns to INTEGER, or adjust table and column identifier casing.
The conversion issues were confined to editable objects such as stored procedures, functions, views, or triggers containing dialect-specific SQL differences (for example, unsupported PL/SQL syntax or exception-handling discrepancies), rather than table-level data type mappings and global identifier casing.
A conversion mapping file in Database Migration Service (DMS) is a plain-text configuration file containing conversion directives that override or customize the default deterministic schema conversion rules when migrating between heterogeneous database engines, such as Oracle and PostgreSQL.
Uploading a mapping file with the specified directives addresses every schema conversion constraint simultaneously:
EXPORT_SCHEMA 1: Satisfies the mandatory directive required in every conversion mapping file so DMS knows to export and map source schemas to destination schemas.DEFAULT_NUMERIC integer: Overrides the default conversion behavior for Oracle NUMBER columns declared without precision or scale, forcing them to map to PostgreSQL INTEGER rather than DECIMAL or BIGINT.MODIFY_TYPE events:dates_and_times:TIMESTAMP: Targets a single column (dates_and_times in the events table) and converts it specifically to TIMESTAMP without altering other columns of the same source data type.CASE_HANDLING PRESERVE_ORIGINAL: Overrides the default lowercase conversion globally across the workspace so that table and column names retain their original Oracle casing for case-sensitive PostgreSQL queries.CASE_HANDLING, DEFAULT_NUMERIC) and per-column overrides (MODIFY_TYPE).Because DMS does not allow editing table definitions directly in the interactive SQL editor, using a conversion mapping file is the intended, repeatable mechanism to enforce data type mappings, column-level overrides, and identifier casing rules during heterogeneous DDL conversion.
Gemini quality assessments are AI-powered analysis tools integrated into DMS conversion workspaces. They evaluate converted PostgreSQL code against the original source database code and generate diagnostic reports highlighting potential correctness issues, semantic discrepancies, or behavioral differences.
Quality assessments are purely analytical and diagnostic; they do not execute deterministic data type overrides, configure column-level mappings, or enforce global identifier casing rules on table DDL. While Gemini features can assist with code conversion, quality assessments specifically inspect and report on functional equivalence rather than applying structured configuration rules like mapping precisionless NUMBER columns to INTEGER or preserving source object casing.
DEFAULT_NUMERIC, MODIFY_TYPE, or CASE_HANDLING directives when strict schema naming and data type contracts are required by downstream applications.You needed to validate whether converted stored procedures, functions, or triggers maintain functional equivalence with the original Oracle logic and wanted an automated review report identifying subtle dialect or exception-handling discrepancies before testing.
DATA_TYPE directive and source modification doThe DATA_TYPE conversion directive maps an entire source data type (such as NUMBER(4,0) or REAL) globally to a specified PostgreSQL data type across all objects in the targeted schema. Modifying the source Oracle database directly alters the live production metadata before DMS pulls a schema snapshot.
This approach introduces critical data corruption risks and unnecessary operational overhead:
NUMBER globally to TIMESTAMP via DATA_TYPE would convert numeric columns (such as IDs, quantities, and financial amounts) into timestamps rather than targeting only the dates_and_times column in the events table, which requires MODIFY_TYPE.NUMBER rule: It does not configure DEFAULT_NUMERIC integer to handle NUMBER declarations lacking precision and scale.CASE_HANDLING PRESERVE_ORIGINAL handles identifier casing safely inside the conversion workspace.DATA_TYPE vs. MODIFY_TYPE: Use DATA_TYPE when every column of a given source type needs a uniform PostgreSQL type; use MODIFY_TYPE when overriding a single table column's target type.Every column of a specific source data type across the entire schema needed to map uniformly to a single PostgreSQL type (such as mapping all REAL columns to DOUBLE PRECISION), and the source database contained broken DDL requiring direct remediation.
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