Subdomain 1.2: Connecting enterprise data to Gemini Enterprise
1.A team wants an Agent Search data store to reflect the very latest rows in a rapidly changing BigQuery table without a copy of the data living inside Gemini Enterprise's index, even though search relevance may be lower than for indexed content. Which connection approach should they configure?
- A.Configure data ingestion so the table is indexed and periodically re-synced into the data store.
- B.Configure data federation so queries retrieve rows directly from BigQuery without copying them into an index.
- C.Create a custom connector that mirrors the table into Cloud Storage before indexing it.
- D.Enable OCR parsing on the table export so numeric fields are treated as searchable text.
Show answer & explanation
Correct answer: B — Configure data federation so queries retrieve rows directly from BigQuery without copying them into an index.
- A. Data ingestion copies data into the index to improve search relevance and speed, which contradicts the requirement of not storing a copy inside Gemini Enterprise.
- B. Data federation retrieves information directly from BigQuery at query time without copying it into an index, matching the requirement for a live, uncopied view even at some cost to relevance.
- C. Mirroring the table into Cloud Storage before indexing still produces a stored copy of the data, defeating the goal of avoiding duplication, and adds unnecessary pipeline complexity.
- D. OCR parsing extracts text from scanned or image-based content and has no bearing on structured BigQuery rows, so it does not address the federation-versus-ingestion decision.