Generative AI Leader Practice Question: Embed a generative AI writing assistant into…

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

• ✗

  Google Workspace Add-ons with Vertex AI

  Why it's wrong here

  Add-ons extend Workspace UI but require custom Apps Script and Vertex AI wiring, not a built-in drafting assistant. They suit bespoke integrations exposing third-party services inside Docs. The stem asks which native Workspace feature already drafts content from prompts.

• ✗

  Vertex AI API integrated via Apps Script

  Why it's wrong here

  Integrating Vertex AI API via Apps Script necessitates custom development to build the writing assistant's interface and functionality directly within Google Docs, rather than leveraging an existing, ready-to-use Google Workspace feature for end-users. This approach is tempting because it offers extensive customisation and control, making it ideal for bespoke AI solutions or integrating proprietary, fine-tuned models for highly specific, complex tasks within Workspace applications.

• ✗

  Gmail Smart Compose

  Why it's wrong here

  Smart Compose autocompletes sentences inside Gmail only; it cannot draft reports in Docs nor accept free-form prompts. It is correct when the requirement is inline sentence suggestions while composing email. The stem needs prompt-driven drafting across Docs and reports.

• ✓

  Duet AI in Google Docs (Gemini for Google Workspace)

  Why this is correct

  Gemini for Google Workspace, previously Duet AI, embeds generative assistance directly inside Google Docs, letting users draft emails and reports from prompts without leaving the document. This satisfies the requirement to integrate a writing assistant into the existing Docs workflow.

Go deeper

Related to this question