Dataford
Interview QuestionsInterview GuidesExperiencesCoaching
New
Pricing
Get started
Dataford
Popular roles
Software EngineerData AnalystData ScientistData EngineerBusiness AnalystAI EngineerMachine Learning EngineerProduct Manager
Browse
Browse All RolesEvery role hub, from analyst to MLBrowse All CompaniesCompany-specific interview loopsAll Interview GuidesThe full guide library
Top questions by role
Software EngineerData AnalystData ScientistData EngineerBusiness AnalystAI EngineerMachine Learning EngineerProduct Manager
Top questions by skill
SQLPythonStatisticsMachine LearningA/B TestingSystem DesignGenerative AIProduct SenseMetricsBehavioral
Browse all questions →Try a mock interview
Experiences
Practice
Mock InterviewsTimed interview simulations with feedbackCoaching1:1 coaching with people at your target companiesSuccess PathYour 6-week structured planModulesCurated lessons by topicWebinarsTalks from ex-Big Tech data leadsPlaygroundA free-form scratch editor
Learn
BlogInterview strategy and career adviceTech Job Market ReportHiring trends across data and AI rolesFor UniversitiesDataford for career centersAbout DatafordWho we are and how we build
Pricing
Build my plan

Debug Multimodal Pipeline with CosmosDB Issue

HardSystem Design00:00
Practice interviewer
In session
5 left
00:00

Your question is Debug Multimodal Pipeline with CosmosDB Issue. Take a moment with it on the right.

Talk me through your thinking if you like. When you're confident, submit your answer and I'll grade it like a real screen (7/10 or better passes).

You need to log in / sign up to chat or submit.

Problem

We have a multimodal chatbot that processes documents containing both text and images. We use a Vision Model for image summarisation and store everything in Azure CosmosDB (NoSQL). The pipeline works fine initially, but after processing 15-16 chunks, we encounter a 'CosmosDB not found' error, but only for documents containing both text and images. Debug it.

Asked in the Round 4 stage. The interviewer answered clarifying questions and suggested considering the async factor. Reported follow-ups: Why specifically a 'DB not found' error? Are text and image summarisation payloads sent separately or merged?