Q: 4
A Generative AI Engineer wants to build an LLM-based solution to help a restaurant improve its
online customer experience with bookings by automatically handling common customer inquiries.
The goal of the solution is to minimize escalations to human intervention and phone calls while
maintaining a personalized interaction. To design the solution, the Generative AI Engineer needs to
define the input data to the LLM and the task it should perform.
Which input/output pair will support their goal?
Options
Discussion
Option B makes sense, since letting the LLM read chat logs and then present booking options as buttons helps automate actual bookings without human help. The others don't really drive the booking flow. I think B is best for this use case, but open to other takes.
Option B, saw something super similar in a practice exam and B was correct there too.
C or D for me. Grouping chat logs by users (A) seems more like analysis after the fact, not direct customer help. If the LLM outputs cancellation options (D), that could reduce human escalations for people trying to cancel, which is a common scenario too. Pretty sure B is better for bookings, but if the focus is on cancellations, D might be solid. Anyone else think C could fit if sentiment matters for escalation routing?
B
B
Grouping chat logs by users makes sense to me here. A
B lines up with what’s in the official study guide and matches what I’ve seen on similar practice tests.
B tbh, had something like this in a mock. Using chat logs as input and giving booking detail buttons keeps the LLM handling bookings directly, which should cut down on escalations. Pretty sure that's what they're looking for.
I see what you mean, but B still makes more sense to me for minimizing escalations. If the LLM takes chat logs and offers booking option buttons, it can guide customers step by step without needing a human. A and D don't really let the AI take action directly in the booking process. I think it's B, but could be missing something subtle.
Probably B, the button interface avoids escalation traps that D and A might cause. C is about reviews, not bookings.
Be respectful. No spam.