Stakeholders who do not write scripts want to explore a lane-booking story in plain language for quick clarification. Which GenAI interaction choice fits best?
Select an answer to reveal the explanation.
Short Explanation
When people who never touch scripts want to poke at a story in everyday words, hand them a chatbot. Pipelines are great for batch jobs, not for hallway questions. Chat opens the door wider for onboarding and clarification.
Full Explanation
A chatbot fits stakeholders who do not write scripts but want to explore a lane-booking story in plain language for quick clarification. Conversational access widens non-technical participation in civic recreation systems and supports onboarding without forcing keyword literacy. Pipeline-only script emitters optimize batch automation and intentionally lack that exploratory surface.
A scheduled pipeline job that only emits keyword scripts with no conversational interface fails the plain-language exploration need. A CT-AI metamorphic suite that scores the booking model’s hidden layers treats models as products under test rather than helping stakeholders read a story. A foundation-model pretraining cluster reserved for infrastructure engineers is irrelevant to stakeholder clarification.
Exam caveat: non-technical clarification and exploration → chatbot. Batch script emission → application/pipeline. Do not confuse stakeholder access with model-training infrastructure.
Operational check: give recreation stakeholders a moderated chatbot on the lane-booking story; keep keyword generation on the automation pipeline; capture clarification questions that still need owner answers; update the civic access model so both channels stay purposeful.