Exam Bundle

This signal belongs to the adjacent case “The PostgreSQL replication feed is failing because source publications were never configured,” whose remedy is Create the required source publication and replication slot with suitable privileges. The observed result for the present requirement is The scheduled import completes with the expected full snapshot records.

This signal belongs to the adjacent case “A PostgreSQL source must capture updates without reloading the full database on each run,” whose remedy is Configure Lakeflow Connect PostgreSQL CDC with supported logical replication. The observed result for the present requirement is The scheduled import completes with the expected full snapshot records.

Source inserts, updates and deletes propagate according to connector semantics pertains to a different control (Configure a supported Lakeflow Connect SQL Server CDC connector) and a different need (The source is SQL Server and the platform needs a managed incremental load). It cannot establish that Use a governed JDBC or supported query-based batch ingestion process met the stated goal.

This action solves a different issue: “An updated source table is missing from a configured publication.” Its normal signal is Changes for the newly included table flow into its intended target. Here the requested behavior is “An idle PostgreSQL logical replication slot retains WAL indefinitely and threatens source disk,” so that signal is not sufficient.

Drop the abandoned slot after verifying no other consumer depends on it is appropriate when “A connector was removed but its replication slot still exists”; it would be verified by The orphaned slot disappears and WAL retention decreases. It does not directly satisfy “An idle PostgreSQL logical replication slot retains WAL indefinitely and threatens source disk,” whose relevant acceptance evidence is Replication slot lag and WAL retention stay below the approved threshold.

Create a dedicated least-privilege replication identity for the UC connection belongs to the separate case “An administrator uses root database credentials inside the production ingestion pipeline,” where The pipeline authenticates as the restricted service identity, not admin would be expected. That differs from the condition in this stem: “An idle PostgreSQL logical replication slot retains WAL indefinitely and threatens source disk.”

That observation is a valid indicator for “An administrator uses root database credentials inside the production ingestion pipeline” when using Create a dedicated least-privilege replication identity for the UC connection. The scenario instead tests “An idle PostgreSQL logical replication slot retains WAL indefinitely and threatens source disk”; the relevant result is Replication slot lag and WAL retention stay below the approved threshold.

The connector establishes its session and ingests approved tables would demonstrate the separate action Grant only the documented replication and source-read privileges, which addresses “The database ingestion user lacks permissions to read the required tables.” It does not verify the requirement “An idle PostgreSQL logical replication slot retains WAL indefinitely and threatens source disk” following Monitor replication lag and control WAL retention and slot lifecycle.

This signal belongs to the adjacent case “An updated source table is missing from a configured publication,” whose remedy is Add that authorized table to the CDC publication and refresh gateway metadata. The observed result for the present requirement is Replication slot lag and WAL retention stay below the approved threshold.

Drop the abandoned slot after verifying no other consumer depends on it belongs to the separate case “A connector was removed but its replication slot still exists,” where The orphaned slot disappears and WAL retention decreases would be expected. That differs from the condition in this stem: “The database ingestion user lacks permissions to read the required tables.”

Monitor replication lag and control WAL retention and slot lifecycle is appropriate when “An idle PostgreSQL logical replication slot retains WAL indefinitely and threatens source disk”; it would be verified by Replication slot lag and WAL retention stay below the approved threshold. It does not directly satisfy “The database ingestion user lacks permissions to read the required tables,” whose relevant acceptance evidence is The connector establishes its session and ingests approved tables.

Add that authorized table to the CDC publication and refresh gateway metadata is appropriate when “An updated source table is missing from a configured publication”; it would be verified by Changes for the newly included table flow into its intended target. It does not directly satisfy “The database ingestion user lacks permissions to read the required tables,” whose relevant acceptance evidence is The connector establishes its session and ingests approved tables.

This signal belongs to the adjacent case “A connector was removed but its replication slot still exists,” whose remedy is Drop the abandoned slot after verifying no other consumer depends on it. The observed result for the present requirement is The connector establishes its session and ingests approved tables.

Changes for the newly included table flow into its intended target would demonstrate the separate action Add that authorized table to the CDC publication and refresh gateway metadata, which addresses “An updated source table is missing from a configured publication.” It does not verify the requirement “The database ingestion user lacks permissions to read the required tables” following Grant only the documented replication and source-read privileges.

That observation is a valid indicator for “An administrator uses root database credentials inside the production ingestion pipeline” when using Create a dedicated least-privilege replication identity for the UC connection. The scenario instead tests “The database ingestion user lacks permissions to read the required tables”; the relevant result is The connector establishes its session and ingests approved tables.

Monitor replication lag and control WAL retention and slot lifecycle is appropriate when “An idle PostgreSQL logical replication slot retains WAL indefinitely and threatens source disk”; it would be verified by Replication slot lag and WAL retention stay below the approved threshold. It does not directly satisfy “An administrator uses root database credentials inside the production ingestion pipeline,” whose relevant acceptance evidence is The pipeline authenticates as the restricted service identity, not admin.

Drop the abandoned slot after verifying no other consumer depends on it belongs to the separate case “A connector was removed but its replication slot still exists,” where The orphaned slot disappears and WAL retention decreases would be expected. That differs from the condition in this stem: “An administrator uses root database credentials inside the production ingestion pipeline.”

The alternative Grant only the documented replication and source-read privileges has a distinct purpose—The database ingestion user lacks permissions to read the required tables. It would not establish the required outcome (An administrator uses root database credentials inside the production ingestion pipeline); the necessary verification concerns The pipeline authenticates as the restricted service identity, not admin.

Replication slot lag and WAL retention stay below the approved threshold would demonstrate the separate action Monitor replication lag and control WAL retention and slot lifecycle, which addresses “An idle PostgreSQL logical replication slot retains WAL indefinitely and threatens source disk.” It does not verify the requirement “An administrator uses root database credentials inside the production ingestion pipeline” following Create a dedicated least-privilege replication identity for the UC connection.

That observation is a valid indicator for “A connector was removed but its replication slot still exists” when using Drop the abandoned slot after verifying no other consumer depends on it. The scenario instead tests “An administrator uses root database credentials inside the production ingestion pipeline”; the relevant result is The pipeline authenticates as the restricted service identity, not admin.

Changes for the newly included table flow into its intended target pertains to a different control (Add that authorized table to the CDC publication and refresh gateway metadata) and a different need (An updated source table is missing from a configured publication). It cannot establish that Create a dedicated least-privilege replication identity for the UC connection met the stated goal.

Monitor replication lag and control WAL retention and slot lifecycle belongs to the separate case “An idle PostgreSQL logical replication slot retains WAL indefinitely and threatens source disk,” where Replication slot lag and WAL retention stay below the approved threshold would be expected. That differs from the condition in this stem: “A connector was removed but its replication slot still exists.”

Add that authorized table to the CDC publication and refresh gateway metadata is appropriate when “An updated source table is missing from a configured publication”; it would be verified by Changes for the newly included table flow into its intended target. It does not directly satisfy “A connector was removed but its replication slot still exists,” whose relevant acceptance evidence is The orphaned slot disappears and WAL retention decreases.

Create a dedicated least-privilege replication identity for the UC connection is appropriate when “An administrator uses root database credentials inside the production ingestion pipeline”; it would be verified by The pipeline authenticates as the restricted service identity, not admin. It does not directly satisfy “A connector was removed but its replication slot still exists,” whose relevant acceptance evidence is The orphaned slot disappears and WAL retention decreases.

The connector establishes its session and ingests approved tables pertains to a different control (Grant only the documented replication and source-read privileges) and a different need (The database ingestion user lacks permissions to read the required tables). It cannot establish that Drop the abandoned slot after verifying no other consumer depends on it met the stated goal.

The pipeline authenticates as the restricted service identity, not admin would demonstrate the separate action Create a dedicated least-privilege replication identity for the UC connection, which addresses “An administrator uses root database credentials inside the production ingestion pipeline.” It does not verify the requirement “A connector was removed but its replication slot still exists” following Drop the abandoned slot after verifying no other consumer depends on it.

Changes for the newly included table flow into its intended target would demonstrate the separate action Add that authorized table to the CDC publication and refresh gateway metadata, which addresses “An updated source table is missing from a configured publication.” It does not verify the requirement “A connector was removed but its replication slot still exists” following Drop the abandoned slot after verifying no other consumer depends on it.

The alternative Drop the abandoned slot after verifying no other consumer depends on it has a distinct purpose—A connector was removed but its replication slot still exists. It would not establish the required outcome (An updated source table is missing from a configured publication); the necessary verification concerns Changes for the newly included table flow into its intended target.

Monitor replication lag and control WAL retention and slot lifecycle is appropriate when “An idle PostgreSQL logical replication slot retains WAL indefinitely and threatens source disk”; it would be verified by Replication slot lag and WAL retention stay below the approved threshold. It does not directly satisfy “An updated source table is missing from a configured publication,” whose relevant acceptance evidence is Changes for the newly included table flow into its intended target.

Create a dedicated least-privilege replication identity for the UC connection belongs to the separate case “An administrator uses root database credentials inside the production ingestion pipeline,” where The pipeline authenticates as the restricted service identity, not admin would be expected. That differs from the condition in this stem: “An updated source table is missing from a configured publication.”

The pipeline authenticates as the restricted service identity, not admin would demonstrate the separate action Create a dedicated least-privilege replication identity for the UC connection, which addresses “An administrator uses root database credentials inside the production ingestion pipeline.” It does not verify the requirement “An updated source table is missing from a configured publication” following Add that authorized table to the CDC publication and refresh gateway metadata.

This signal belongs to the adjacent case “The database ingestion user lacks permissions to read the required tables,” whose remedy is Grant only the documented replication and source-read privileges. The observed result for the present requirement is Changes for the newly included table flow into its intended target.

Replication slot lag and WAL retention stay below the approved threshold would demonstrate the separate action Monitor replication lag and control WAL retention and slot lifecycle, which addresses “An idle PostgreSQL logical replication slot retains WAL indefinitely and threatens source disk.” It does not verify the requirement “An updated source table is missing from a configured publication” following Add that authorized table to the CDC publication and refresh gateway metadata.