A community dark-sky event desk will let testers chat with a model about story wording. Which LLMOps concerns are highlighted on that chatbot path?
Select an answer to reveal the explanation.
Short Explanation
Even a simple story-wording chat still carries privacy, security, and cost. Pick a platform with enough assurances — or host an in-house open-source-licensed model for more control. Vendor brand names are not required.
Full Explanation
On the chatbot LLMOps path, highlighted concerns include managing data privacy and security and optimizing cost—choosing a service platform only with sufficient assurances, or preferring in-house open-source-licensed models when greater control is needed. A community dark-sky event desk that lets testers chat about story wording still processes test-related text, so privacy and cost remain live concerns. Ignoring privacy and cost because chatbots never process test-related text is false for civic testing chats that may touch stories, defects, or resident-facing wording. Requiring neuron-coverage gates before any story-wording chat imports CT-AI SUT measurement into a chatbot operating-path item. Mandating a single commercial vendor SKU by name on every project is product branding, not the syllabus privacy-and-cost emphasis. Exam caveat: detailed privacy-attack techniques remain Chapter 3; this item focuses on the chatbot operating path’s privacy, security, and cost posture. Operational check: before enabling dark-sky story chats, verify the platform’s data-handling assurances or the control benefits of an in-house open-source-licensed option, and track recurring chat cost. Keep civic testware subject to the same review discipline you would apply to human-authored packs.