New Year Sale ! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Databricks Exam Databricks-Generative-AI-Engineer-Associate Topic 6 Question 6 Discussion

Actual exam question for Databricks's Databricks-Generative-AI-Engineer-Associate exam
Question #: 6
Topic #: 6
[All Databricks-Generative-AI-Engineer-Associate Questions]

A Generative Al Engineer is responsible for developing a chatbot to enable their company's internal HelpDesk Call Center team to more quickly find related tickets and provide resolution. While creating the GenAI application work breakdown tasks for this project, they realize they need to start planning which data sources (either Unity Catalog volume or Delta table) they could choose for this application. They have collected several candidate data sources for consideration:

call_rep_history: a Delta table with primary keys representative_id, call_id. This table is maintained to calculate representatives' call resolution from fields call_duration and call start_time.

transcript Volume: a Unity Catalog Volume of all recordings as a *.wav files, but also a text transcript as *.txt files.

call_cust_history: a Delta table with primary keys customer_id, cal1_id. This table is maintained to calculate how much internal customers use the HelpDesk to make sure that the charge back model is consistent with actual service use.

call_detail: a Delta table that includes a snapshot of all call details updated hourly. It includes root_cause and resolution fields, but those fields may be empty for calls that are still active.

maintenance_schedule -- a Delta table that includes a listing of both HelpDesk application outages as well as planned upcoming maintenance downtimes.

They need sources that could add context to best identify ticket root cause and resolution.

Which TWO sources do that? (Choose two.)

Show Suggested Answer Hide Answer
Suggested Answer: D, E

In the context of developing a chatbot for a company's internal HelpDesk Call Center, the key is to select data sources that provide the most contextual and detailed information about the issues being addressed. This includes identifying the root cause and suggesting resolutions. The two most appropriate sources from the list are:

Call Detail (Option D):

Contents: This Delta table includes a snapshot of all call details updated hourly, featuring essential fields like root_cause and resolution.

Relevance: The inclusion of root_cause and resolution fields makes this source particularly valuable, as it directly contains the information necessary to understand and resolve the issues discussed in the calls. Even if some records are incomplete, the data provided is crucial for a chatbot aimed at speeding up resolution identification.

Transcript Volume (Option E):

Contents: This Unity Catalog Volume contains recordings in .wav format and text transcripts in .txt files.

Relevance: The text transcripts of call recordings can provide in-depth context that the chatbot can analyze to understand the nuances of each issue. The chatbot can use natural language processing techniques to extract themes, identify problems, and suggest resolutions based on previous similar interactions documented in the transcripts.

Why Other Options Are Less Suitable:

A (Call Cust History): While it provides insights into customer interactions with the HelpDesk, it focuses more on the usage metrics rather than the content of the calls or the issues discussed.

B (Maintenance Schedule): This data is useful for understanding when services may not be available but does not contribute directly to resolving user issues or identifying root causes.

C (Call Rep History): Though it offers data on call durations and start times, which could help in assessing performance, it lacks direct information on the issues being resolved.

Therefore, Call Detail and Transcript Volume are the most relevant data sources for a chatbot designed to assist with identifying and resolving issues in a HelpDesk Call Center setting, as they provide direct and contextual information related to customer issues.


Contribute your Thoughts:

Charlie
1 months ago
Haha, I bet the HelpDesk team is just hoping the chatbot doesn't have a sense of humor and start making sarcastic remarks to the callers. 'Ah, I see the problem. You've tried turning it off and on again, but did you also try throwing it out the window?'
upvoted 0 times
Rosalyn
8 days ago
User 3: I can imagine the chatbot making some funny comments if it had access to transcript Volume!
upvoted 0 times
...
Derick
28 days ago
User 2: Agreed, those two sources would definitely help in identifying ticket root cause and resolution.
upvoted 0 times
...
Ivan
1 months ago
User 1: That would be hilarious! But I hope they choose call_rep_history and call_detail for the data sources.
upvoted 0 times
...
...
Kizzy
2 months ago
I agree, the call_detail and transcript Volume tables seem like the best options. The maintenance_schedule table could also be useful to understand any system downtime that may have contributed to the call.
upvoted 0 times
Rolande
1 months ago
Yes, having that information could give more context to the calls and help in finding solutions faster.
upvoted 0 times
...
Dylan
1 months ago
The maintenance_schedule table could also provide valuable information on system downtime.
upvoted 0 times
...
Linsey
1 months ago
Agreed, those tables would definitely help in identifying the root cause and resolution of tickets.
upvoted 0 times
...
Germaine
2 months ago
I think call_detail and transcript Volume are the best choices for this project.
upvoted 0 times
...
...
Ricki
2 months ago
I agree with Royce. Those two sources provide the most relevant information for resolving tickets efficiently.
upvoted 0 times
...
Royce
2 months ago
I think call_rep_history and call_detail are the best sources for identifying ticket root cause and resolution.
upvoted 0 times
...
Lorean
2 months ago
I think the call_detail and transcript Volume tables would be the most useful sources for this application. The call_detail table has the root cause and resolution fields, which could provide valuable context, and the transcript Volume could give additional details from the call recordings.
upvoted 0 times
Shayne
1 months ago
I think using both call_detail and transcript Volume would give a comprehensive view of the ticket details.
upvoted 0 times
...
Flo
1 months ago
Yes, the transcript Volume could also provide valuable information from the call recordings.
upvoted 0 times
...
France
2 months ago
I agree, the call_detail table seems like a good choice for identifying root cause and resolution.
upvoted 0 times
...
...

Save Cancel