Cert Notes/ Commute Study Notes
Roadmap
KOEN
CLF-C02 · FoundationalCloud Practitioner - Foundational
DVA-C02 · AssociateDeveloper - Associate
SAA-C03 · AssociateSolutions Architect - Associate
SOA-C02 · AssociateCloudOps Engineer - Associate
SAP-C02 · ProfessionalSolutions Architect - Professional
DOP-C02 · ProfessionalDevOps Engineer - Professional
SCS-C03 · SpecialtySecurity - Specialty
MLA-C01 · AssociateMachine Learning Engineer - Associate
AIF-C01 · FoundationalAI Practitioner - Foundational
  • Week 1
    • 1.The Relationship and Differences Between AI, Machine Learning, and Deep Learning
    • 2.Learning Types: Supervised, Unsupervised, and Reinforcement Learning
    • 3.Problems Where ML Fits vs. Problems Where It Doesn't
    • 4.Key Terms: Model, Training, Inference, Feature, Label, Overfitting
    • 5.Week 1 Wrap-Up: AI/ML Fundamentals Review
  • Week 2
    • 1.ML Lifecycle Overview: One Complete Cycle from Data to Operations
    • 2.Data: Structured vs Unstructured, Data Splitting, and the Power of Quality
    • 3.Model Evaluation Basics: Accuracy, Precision, Recall, and Overfitting/Underfitting
    • 4.The Human Role in ML Development: Labeling, Feedback, and Iterative Improvement
    • 5.Week 2 Summary: ML Lifecycle and Data at a Glance
  • Week 3
    • 1.What Is Generative AI: Difference from Traditional ML, and Foundation Models
    • 2.How LLMs Work: Tokens, Embeddings, Context Window, and Inference
    • 3.Prompt Engineering Basics: Good Prompts, Zero/Few-shot, and Limitations
    • 4.Limitations and Risks of Generative AI: Hallucinations, Bias, Non-determinism, and Appropriate Use Cases
    • 5.Week 3 Comprehensive Review: Wrapping Up Generative AI Fundamentals at a Glance
  • Week 4
    • 1.Amazon Bedrock: Fully Managed Service for Renting Foundation Models
    • 2.Amazon SageMaker: A Platform for Directly Training and Deploying ML Models
    • 3.AWS AI Services (1): Managed APIs Handling Images, Documents, Text, and Speech
    • 4.AWS AI Services (2) + Amazon Q: Chatbots, Search, Recommendations, Forecasting, and Generative Assistant
    • 5.Week 4 Comprehensive Review: Complete Map of AWS AI/ML Services
  • Week 5
    • 1.Principles of Responsible AI: Fairness, Bias, Transparency, Explainability, Robustness, Privacy
    • 2.AWS's Responsible AI Tools: SageMaker Clarify, Model Monitor, Bedrock Guardrails, AI Service Cards
    • 3.AI Security: Least Privilege IAM, Data Encryption, PII Protection, PrivateLink, Shared Responsibility Model
    • 4.Data Governance and Compliance: Data Origin·Quality, Model Governance, Audit·Logging, Legal and Ethical Considerations for Generative AI
    • 5.Week 5 Comprehensive Review: Binding Responsible AI·Security·Governance into One
  • Week 6
    • 1.Domain Review 1: AI/ML Fundamentals + Generative AI Fundamentals: Critical Summary
    • 2.Domain Review 2: Foundation Model Applications (AWS AI Services) Critical Summary
    • 3.Domain Review 3: Responsible AI + Security·Governance Critical Summary
    • 4.Full Mock Exam Pace: Five Domains Comprehensive Questions
    • 5.D-Day Wrap-Up: Exam Structure, Keyword → Service Translation Table, Frequently-Missed Traps
DEA-C01 · AssociateData Engineer - Associate
MLS-C01 · SpecialtyMachine Learning - Specialty
← AIF-C01/Week 1/Day 3
AIF-C01· AssociateWeek 1 · Day 3~14 min read

Day 3 - Problems Where ML Fits vs. Problems Where It Doesn't

Introduction

Machine learning is powerful, but it is not a universal tool suited to every problem. Today we will learn the criteria for distinguishing problems that suit machine learning well from those that do not, and compare how it differs from the traditional programming approach.

This judgment is very important in practice, because it is common to "adopt machine learning where it wasn't needed, only to increase costs and get worse results." The exam also frequently asks questions like "Is machine learning appropriate for this scenario?"

Traditional Programming vs. Machine Learning

First, let's sort out the fundamental difference between the two approaches.

AspectTraditional programmingMachine learning
Who creates the rulesHumans (developers)Learned from data
InputData + rulesData + answers (examples)
OutputResults (answers)Rules (a model)
Suitable situationsRules are clear and unchangingRules are complex or hard for humans to define

In traditional programming, "a human writes the rules and the computer executes them as-is." In contrast, the key difference with machine learning is that "given data and answer examples, the computer produces the rules (a model)."

💡 Related theory: Traditional programming is data + rules → results, while machine learning is data + results → rules. It's easy to remember if you think of the inputs and outputs as swapped.

Problems Where Machine Learning Fits

The more of the following conditions are met, the better a choice machine learning is.

  1. The rules are too complex or too hard for a human to write out one by one
    • Example: It is practically impossible for a human to write code rules for recognizing a cat in a photo.
  2. Patterns exist but are hard to express explicitly
    • Example: The characteristics of spam email keep changing and are subtle, making them hard to pin down as fixed rules.
  3. Sufficient quantity and quality of data is available
    • You need plenty of historical data (examples) to train on.
  4. Some margin of error is acceptable
    • Machine learning is not 100% accurate. It gives probabilistically good answers.
  5. The rules must change as circumstances change
    • The model can be retrained on new data to adapt to change.

Suitable Examples

  • Image/speech/natural language recognition
  • Recommendation systems (products, movies)
  • Spam and fraud detection
  • Demand and price forecasting
  • Customer churn prediction

Problems Where Machine Learning Doesn't Fit

Conversely, in the following cases machine learning is overkill or inappropriate.

  1. The rules are clear and simple
    • Example: "VAT is 10% of the amount" is just multiplication. No machine learning needed.
  2. There is almost no data
    • Without enough examples to learn from, machine learning cannot work properly.
  3. 100% accuracy and complete explainability are mandatory
    • When legal or safety requirements allow zero error and every decision must have a clearly explained basis, machine learning — probabilistic and sometimes a "black box" — can be risky.
  4. Simple calculation or lookup is sufficient
    • Database lookups, fixed formula calculations, and the like are more accurate and cheaper with the traditional approach.

Unsuitable Examples

ProblemBetter approachReason
Computing the sum of two numbersTraditional programmingThe rule is clear
Calculating a 10% taxTraditional programmingSimple formula
Looking up employee info by employee IDDatabase lookupAn exact lookup is sufficient
A prediction with only 10 data recordsAcquire data firstInsufficient training data

💡 Related theory: Avoid the misconception that "machine learning is always smarter." Applying machine learning to problems with clear rules can increase costs and actually reduce accuracy. Choosing the simplest method that is sufficient is good design.

Decision Flowchart

Here is a quick order of checks for deciding whether to adopt machine learning.

Can a human write the rules easily and clearly?
   └ Yes → Use traditional programming (machine learning unnecessary)
   └ No ↓
Is there enough data to train on?
   └ No → Acquire data first (machine learning is difficult for now)
   └ Yes ↓
Is some margin of error acceptable?
   └ No → Review carefully (machine learning may be risky)
   └ Yes → Machine learning is likely a good fit

Striking a Realistic Balance

In practice, the two approaches are often used together. For example, clear rules are handled with traditional code, and only the complex judgments are delegated to machine learning. What matters is the perspective of "picking the right tool for the problem," not "only one of the two is correct."

Today's Summary

  • Traditional programming is data + rules → results; machine learning is data + results → rules.
  • Machine learning fits when the rules are complex, data is plentiful, and some margin of error is acceptable.
  • It can be a poor fit when the rules are clear, data is scarce, or 100% accuracy is mandatory.
  • Choosing the simplest method that is sufficient is good design.

📝 Practice Questions

Click a choice to reveal the answer and explanation.

Question 1

For which of the following problems is traditional programming more appropriate than machine learning?

Question 2

Which statement most accurately describes the input/output relationship of traditional programming and machine learning?

Question 3

In a certain business task, there are only a handful of historical records available for training, and the results must be legally 100% accurate and fully explainable. Which judgment is most appropriate for this situation?

Question 4

Which of the following is hard to consider a characteristic of problems suited to adopting machine learning?

PreviousLearning Types: Supervised, Unsupervised, and Reinforcement LearningWeek 1 · Day 2Next Key Terms: Model, Training, Inference, Feature, Label, OverfittingWeek 1 · Day 4

On this page

  • Introduction
  • Traditional Programming vs. Machine Learning
  • Problems Where Machine Learning Fits
  • Suitable Examples
  • Problems Where Machine Learning Doesn't Fit
  • Unsuitable Examples
  • Decision Flowchart
  • Striking a Realistic Balance
  • Today's Summary
  • Practice Questions