- LPU MCA Semester 1
- CAB107
- Unit 1
CAB107 · Unit 1: Foundations of AI and data science
AI lifecycle and data science process
10 practice questions · in the MTE and ETE syllabus
Key points
- Start with problem understanding, end with deployment and monitoring
- Data preparation usually takes the most time
- Evaluation uses unseen data
- The lifecycle is iterative, and models need retraining after drift
The data science or AI lifecycle is a structured sequence of stages that turns a business problem into a working, monitored solution. A common framework is CRISP-DM.
- Business or problem understanding: define the objective and the success metric.
- Data collection and understanding: gather and explore data.
- Data preparation: clean, transform and engineer features. This is usually the largest share of project time because real data is messy.
- Modelling: train candidate models.
- Evaluation: measure performance on data the model has not seen.
- Deployment: release the model.
- Monitoring and maintenance: watch for drift and retrain.
The lifecycle is iterative: results from later stages often send the team back, for instance to collect more data, fix a faulty join, or redefine the problem. Iteration happens inside one project.
Worked example: a model scores 98 percent on training data but 71 percent on held-out data. That gap signals overfitting, so the team returns to modelling to regularise or simplify rather than deploying.
A model whose accuracy falls months after launch because customer behaviour changed shows data drift; the fix is monitoring and retraining on recent data.
Exam trap: without a clear objective and success metric the team cannot judge whether the model is useful. Training score alone never justifies deployment.
Try two questions
Why is the data science lifecycle described as iterative?
- Each stage must be repeated exactly three times in a fixed order before the project is considered valid
- Only the deployment stage can ever be repeated, while every earlier stage is run exactly once and then permanently frozen in place
- Results from later stages often send the team back to earlier ones, such as to collect more data or redefine the problem
- The team must abandon the project and start a brand new one after every single metric report is produced
Show the answer
C. Findings in evaluation or exploration often reveal data gaps or a poorly defined goal.
Why not A: No fixed repetition count is required.
Why not B: Any stage may be revisited, not only deployment.
Why not D: Iteration happens inside one project; no new project is needed.
During modelling a team finds the target column has many errors because of a wrong data join. Which action best follows the iterative lifecycle?
- Continue to deployment and fix the faulty join after the release
- Accept the errors because modelling has already started for the team
- Go back to data preparation, fix the join, and rebuild the model
- Delete the target column and then report that the model works
Show the answer
C. Errors discovered later require returning to the data stages.
Why not A: Shipping a model trained on faulty labels would spread the error.
Why not B: Poor labels will degrade every metric and should not be accepted.
Why not D: Without the target, a supervised model cannot be trained or evaluated.