A grants clerk notices Copilot invents a prior award amount that is not present in the attached municipal grant PDF. What should the clerk conclude?
Select an answer to reveal the explanation.
Short Explanation
Attached PDF doesn’t mean the calculator in Copilot is honest. If the award amount wasn’t in the packet, Copilot may just invent one that sounds right. Verify every dollar against the real grant file.
Full Explanation
The grants clerk should conclude that Copilot can fabricate figures when the source document does not contain that data, so award amounts must be verified. Attaching a municipal grant PDF does not guarantee numeric accuracy; the model may invent a prior award amount that sounds consistent with grant narratives. Verification against the PDF and official award records is mandatory before using the figure in city correspondence or applications.
The claim that any number Copilot writes is guaranteed accurate if a PDF was attached fails the grounding concept: attachment provides context opportunity, not a warranty of factual extraction.
The claim that fabricated award amounts only happen when Excel Copilot is used instead of Word Copilot invents an app-only boundary. Fabrication is a generative-model risk across surfaces, not a Word-versus-Excel exclusive.
The claim that invented figures prove the grant PDF was encrypted and Copilot decrypted it successfully confuses cryptography with hallucination. Fabrication does not demonstrate successful decryption of encrypted content.
Exam caveat: stems that mention an attached source plus a wrong number almost always test fabrication/verification, not encryption success or app exclusivity.
Operational check: highlight the award amount in the actual municipal grant PDF or awards database; if Copilot’s figure is absent, correct it manually and note the verified source in the grants file before submission.