Your company has a BigQuery data mart that provides analytics information to hundreds of employees. One user of wants to run jobs without interrupting important workloads. This user isn't concerned ab

Question

Options

• AAsk the user to run the jobs as batch jobs.
• BCreate a separate project for the user to run jobs.
• CAdd the user as a job.user role in the existing project.
• DAllow the user to run jobs when important workloads are not running.

• A
  75% (47)
• B
  8% (5)
• C
  3% (2)
• D
  14% (9)

Explanation

BigQuery batch queries are queued and executed using idle slots from the shared slot pool whenever they become available. Because they do not compete for on-demand or reserved slots used by interactive queries, they inherently avoid interrupting important workloads. Batch queries also have lower priority scheduling, making them a zero-effort, zero-additional-cost solution. Option B (separate project) adds administrative overhead and separate billing, increasing both cost and effort. Option C (job.user role) only grants permission to run jobs in the existing project but does not isolate or deprioritize them. Option D (manual scheduling) requires ongoing human intervention and is not practical or reliable.

No community discussion yet for this question.