@xdev-asia/xdev-knowledge-mcp 1.0.42 → 1.0.44

package/content/pages/xoa-du-lieu-nguoi-dung.md

@@ -0,0 +1,68 @@
+---
+id: 019cb2b9-4dc7-72a5-956a-93f58cbac568
+title: Xóa dữ liệu người dùng
+slug: xoa-du-lieu-nguoi-dung
+excerpt: Hướng dẫn yêu cầu xóa tài khoản và dữ liệu cá nhân trên xDev Asia.
+featured_image: null
+template: default
+show_in_header: false
+show_in_footer: true
+sort_order: 12
+meta:
+  meta_title: Xóa dữ liệu người dùng — xDev Asia
+  meta_description: Yêu cầu xóa tài khoản và toàn bộ dữ liệu cá nhân của bạn khỏi nền tảng xDev Asia.
+published_at: '2026-04-05T00:00:00.000000Z'
+---
+
+## Xóa dữ liệu người dùng
+
+Tại xDev Asia, chúng tôi tôn trọng quyền riêng tư và quyền kiểm soát dữ liệu cá nhân của bạn. Trang này hướng dẫn cách yêu cầu xóa tài khoản và toàn bộ dữ liệu liên quan.
+
+### Dữ liệu chúng tôi lưu trữ
+
+Khi bạn sử dụng xDev Asia (website và ứng dụng di động), chúng tôi có thể lưu trữ:
+
+- **Thông tin tài khoản:** Tên hiển thị, địa chỉ email, ảnh đại diện
+- **Lịch sử học tập:** Bài học đã hoàn thành, tiến độ khóa học
+- **Dữ liệu bookmark:** Bài viết và series đã lưu
+- **Kết quả quiz:** Điểm số và lịch sử thi thử
+
+### Cách yêu cầu xóa dữ liệu
+
+Bạn có thể yêu cầu xóa toàn bộ dữ liệu cá nhân theo một trong các cách sau:
+
+**Cách 1: Qua email**
+
+Gửi email đến **<admin@xdev.asia>a>a>a>** với tiêu đề **"Yêu cầu xóa tài khoản"** và nội dung bao gồm:
+
+- Địa chỉ email đã đăng ký
+- Tên hiển thị trên tài khoản
+- Xác nhận bạn muốn xóa toàn bộ dữ liệu
+
+**Cách 2: Qua GitHub**
+
+Tạo một issue tại [github.com/xdev-asia-labs](https://github.com/xdev-asia-labs) với tiêu đề **"Data Deletion Request"**.
+
+### Thời gian xử lý
+
+Chúng tôi sẽ xử lý yêu cầu trong vòng **30 ngày** kể từ khi nhận được. Sau khi hoàn tất, bạn sẽ nhận được thông báo qua email xác nhận dữ liệu đã được xóa.
+
+### Dữ liệu được xóa
+
+Khi yêu cầu được chấp thuận, chúng tôi sẽ xóa:
+
+- Tài khoản và thông tin cá nhân
+- Lịch sử học tập và tiến độ
+- Bookmark và dữ liệu tùy chỉnh
+- Kết quả quiz và điểm số
+
+**Lưu ý:** Một số dữ liệu đã được ẩn danh hóa và tổng hợp (ví dụ: thống kê lượt xem) có thể không bị xóa vì chúng không thể được liên kết lại với bạn.
+
+### Liên hệ
+
+<admin@xdev.asia>
+Nếu bạn có câ<admin@xdev.asia>riêng tư hoặc xử lý dữ liệu, vui lòng liên hệ:
+<admin@xdev.asia>
+
+- **Email:** <admin@xdev.asia>
+- **Chính sách bảo mật:** [xdev.asia/pages/chinh-sach-quyen-rieng-tu/](/pages/chinh-sach-quyen-rieng-tu/)

package/content/series/luyen-thi/luyen-thi-aws-ml-specialty/chapters/01-phan-1-data-engineering/lessons/01-bai-1-data-repositories-ingestion.md

@@ -0,0 +1,198 @@
+---
+id: 14a964b2-b4b7-46e5-95b0-7d91d9cacdf5
+title: 'Bài 1: Data Repositories & Ingestion — S3, Kinesis, Glue'
+slug: bai-1-data-repositories-ingestion
+description: >-
+  S3 data lake cho ML. Kinesis Data Streams/Firehose cho streaming ingestion.
+  AWS Glue ETL jobs và Data Catalog. Lake Formation. Data Wrangler.
+  Chiến lược lưu trữ: Parquet, ORC, CSV, JSON.
+duration_minutes: 60
+is_free: true
+video_url: null
+sort_order: 1
+section_title: "Phần 1: Data Engineering (20%)"
+course:
+  id: 019c9619-lt02-7002-c002-lt0200000002
+  title: 'Luyện thi AWS Certified Machine Learning - Specialty'
+  slug: luyen-thi-aws-ml-specialty
+---
+
+<div style="text-align: center; margin: 2rem 0;">
+<img src="/storage/uploads/2026/04/aws-mls-bai1-data-ingestion.png" alt="AWS ML Data Repositories & Ingestion" style="max-width: 800px; width: 100%; border-radius: 12px;" />
+<p><em>Data Repositories & Ingestion: S3, Kinesis, Glue và Lake Formation trong ML pipeline</em></p>
+</div>
+
+<h2 id="overview"><strong>1. Tổng quan Data Engineering trong MLS-C01</strong></h2>
+
+<p>Domain Data Engineering chiếm <strong>20% đề thi MLS-C01</strong>. Đây là phần bắt buộc phải nắm vững — đề thi thường hỏi "Which service should be used to ingest/store/transform data for ML?"</p>
+
+<blockquote>
+<p><strong>Exam tip:</strong> Phần lớn câu hỏi Data Engineering sẽ cho một scenario và hỏi service phù hợp. Key pattern: batch → S3 + Glue; streaming → Kinesis; structured/SQL → Athena; catalog → Glue Data Catalog.</p>
+</blockquote>
+
+<h2 id="s3-ml"><strong>2. Amazon S3 — ML Data Lake</strong></h2>
+
+<p><strong>Amazon S3</strong> là nền tảng lưu trữ dữ liệu ML trên AWS. Mọi pipeline ML đều bắt đầu và kết thúc từ S3: training data, model artifacts, predictions.</p>
+
+<h3 id="s3-storage-classes"><strong>2.1. S3 Storage Classes cho ML</strong></h3>
+
+<table>
+<thead><tr><th>Storage Class</th><th>Use Case</th><th>Cost</th></tr></thead>
+<tbody>
+<tr><td><strong>S3 Standard</strong></td><td>Active training data, frequent access</td><td>Cao nhất</td></tr>
+<tr><td><strong>S3 Intelligent-Tiering</strong></td><td>Mixed access patterns (tự động tier)</td><td>Tự động tối ưu</td></tr>
+<tr><td><strong>S3 Standard-IA</strong></td><td>Backup datasets, infrequent access</td><td>Thấp hơn Standard</td></tr>
+<tr><td><strong>S3 Glacier Instant Retrieval</strong></td><td>Archived datasets, occasional retrieval</td><td>Thấp</td></tr>
+<tr><td><strong>S3 Glacier Deep Archive</strong></td><td>Long-term compliance archives</td><td>Thấp nhất</td></tr>
+</tbody>
+</table>
+
+<h3 id="s3-file-formats"><strong>2.2. File Formats for ML</strong></h3>
+
+<table>
+<thead><tr><th>Format</th><th>Type</th><th>Best For</th><th>Compression</th></tr></thead>
+<tbody>
+<tr><td><strong>Parquet</strong></td><td>Columnar</td><td>Analytics, large datasets, feature stores</td><td>Excellent</td></tr>
+<tr><td><strong>ORC</strong></td><td>Columnar</td><td>Hive/EMR workloads</td><td>Excellent</td></tr>
+<tr><td><strong>CSV</strong></td><td>Row-based</td><td>Simple, SageMaker training input</td><td>Poor</td></tr>
+<tr><td><strong>JSON</strong></td><td>Semi-structured</td><td>Nested data, APIs</td><td>Poor</td></tr>
+<tr><td><strong>RecordIO</strong></td><td>Binary</td><td>SageMaker Pipe Mode training</td><td>Good</td></tr>
+</tbody>
+</table>
+
+<blockquote>
+<p><strong>Exam tip:</strong> Khi đề hỏi về <em>performance optimization</em> cho large-scale training, đáp án thường là chuyển sang <strong>Parquet</strong> (columnar, compressed) và dùng <strong>Pipe Mode</strong> thay vì File Mode trong SageMaker.</p>
+</blockquote>
+
+<pre><code class="language-text">S3 Data Lake Architecture for ML:
+
+┌─────────────────────────────────────────────────────────┐
+│                    Amazon S3 Buckets                     │
+├──────────────┬──────────────┬──────────────┬────────────┤
+│  Raw Zone    │ Processed    │  Features    │  Models    │
+│  (landing)   │  Zone        │  Zone        │  & Output  │
+│              │              │              │            │
+│  CSV/JSON    │  Parquet/ORC │  Feature     │  Model     │
+│  original    │  cleaned     │  Store       │  Artifacts │
+│  data        │  transformed │  snapshots   │  Predictions│
+└──────────────┴──────────────┴──────────────┴────────────┘
+       ↑                ↑                ↑
+   Kinesis          AWS Glue         SageMaker
+  (streaming)        (ETL)           Processing
+</code></pre>
+
+<h2 id="kinesis"><strong>3. Amazon Kinesis — Streaming Ingestion</strong></h2>
+
+<p>Kinesis là họ dịch vụ cho <strong>real-time data streaming</strong>. Đây là topic quan trọng trong đề thi — cần phân biệt rõ 4 services.</p>
+
+<table>
+<thead><tr><th>Service</th><th>Function</th><th>Destination</th><th>ML Use Case</th></tr></thead>
+<tbody>
+<tr><td><strong>Kinesis Data Streams (KDS)</strong></td><td>Custom real-time processing</td><td>Custom consumers</td><td>Real-time feature engineering</td></tr>
+<tr><td><strong>Kinesis Data Firehose</strong></td><td>Managed delivery (no code)</td><td>S3, Redshift, ES, Splunk</td><td>Batch loading to data lake</td></tr>
+<tr><td><strong>Kinesis Data Analytics</strong></td><td>SQL/Flink on streams</td><td>S3, Redshift</td><td>Real-time aggregations, anomaly detect</td></tr>
+<tr><td><strong>Kinesis Video Streams</strong></td><td>Video ingestion</td><td>Rekognition, SageMaker</td><td>Computer vision pipelines</td></tr>
+</tbody>
+</table>
+
+<blockquote>
+<p><strong>Exam tip:</strong> Câu hỏi phổ biến: "IoT sensors gửi data liên tục, cần store vào S3 cho ML training mà không cần custom code?" → Kinesis <strong>Data Firehose</strong> (managed, no code). "Cần xử lý real-time với custom logic?" → Kinesis <strong>Data Streams</strong>.</p>
+</blockquote>
+
+<h3 id="kinesis-shards"><strong>3.1. KDS Shards & Capacity</strong></h3>
+
+<pre><code class="language-text">Kinesis Data Streams Capacity:
+
+┌─────────────────────────────────────────────┐
+│  Each Shard:                                │
+│  • Ingest:  1 MB/s OR 1,000 records/s       │
+│  • Read:    2 MB/s                          │
+│  • Retention: 24 hours (default) → 7 days  │
+└─────────────────────────────────────────────┘
+
+Stream with N shards:
+• Total ingest: N × 1 MB/s
+• Total read:   N × 2 MB/s
+</code></pre>
+
+<h2 id="glue"><strong>4. AWS Glue — ETL for ML</strong></h2>
+
+<p><strong>AWS Glue</strong> là fully managed ETL service. Trong ML pipeline, Glue dùng để <strong>transform và clean data</strong> trước khi đưa vào training.</p>
+
+<h3 id="glue-components"><strong>4.1. Glue Components</strong></h3>
+
+<table>
+<thead><tr><th>Component</th><th>Function</th></tr></thead>
+<tbody>
+<tr><td><strong>Glue Data Catalog</strong></td><td>Central metadata repository — schemas, tables, partitions</td></tr>
+<tr><td><strong>Glue Crawlers</strong></td><td>Auto-discover schema từ S3/RDS/Redshift và populate Data Catalog</td></tr>
+<tr><td><strong>Glue ETL Jobs</strong></td><td>Spark-based transformation jobs (Python/Scala)</td></tr>
+<tr><td><strong>Glue DataBrew</strong></td><td>No-code visual data preparation (250+ pre-built transforms)</td></tr>
+<tr><td><strong>Glue Studio</strong></td><td>Visual ETL job builder (drag-and-drop)</td></tr>
+</tbody>
+</table>
+
+<blockquote>
+<p><strong>Exam tip:</strong> <strong>Glue Data Catalog</strong> là metadata store chung cho Athena, EMR, Redshift Spectrum. Khi đề hỏi "centralized schema management" → Glue Data Catalog. Khi hỏi "no-code data cleaning" → Glue DataBrew.</p>
+</blockquote>
+
+<h2 id="lake-formation"><strong>5. AWS Lake Formation</strong></h2>
+
+<p><strong>Lake Formation</strong> build trên S3 + Glue để management <strong>data lake security và governance</strong>. Key feature: column-level và row-level access control.</p>
+
+<pre><code class="language-text">Lake Formation Architecture:
+
+  IAM Users ──→ Lake Formation ──→ S3 Data Lake
+  IAM Roles       (Security         (Raw/Processed)
+                   & Governance)
+                       ↓
+                  Column/Row
+                  Level Access
+                  Control
+</code></pre>
+
+<h2 id="cheat-sheet"><strong>6. Cheat Sheet — Data Ingestion Services</strong></h2>
+
+<table>
+<thead><tr><th>Scenario</th><th>Service</th></tr></thead>
+<tbody>
+<tr><td>Streaming → S3 với no-code</td><td>Kinesis Data Firehose</td></tr>
+<tr><td>Real-time processing với custom logic</td><td>Kinesis Data Streams</td></tr>
+<tr><td>SQL on streaming data</td><td>Kinesis Data Analytics (Flink)</td></tr>
+<tr><td>Batch ETL Spark-based</td><td>AWS Glue ETL Jobs</td></tr>
+<tr><td>No-code visual data prep</td><td>Glue DataBrew</td></tr>
+<tr><td>Schema discovery from S3</td><td>Glue Crawlers + Data Catalog</td></tr>
+<tr><td>SQL queries on S3</td><td>Amazon Athena</td></tr>
+<tr><td>Data lake governance</td><td>AWS Lake Formation</td></tr>
+<tr><td>Large-scale Spark/Hadoop</td><td>Amazon EMR</td></tr>
+</tbody>
+</table>
+
+<h2 id="practice"><strong>7. Practice Questions</strong></h2>
+
+<p><strong>Q1:</strong> A company wants to ingest IoT sensor data into Amazon S3 for ML training. The data arrives continuously and no custom processing is required. Which service is the MOST cost-effective?</p>
+<ul>
+<li>A) Amazon Kinesis Data Streams with a Lambda consumer</li>
+<li>B) Amazon Kinesis Data Firehose ✓</li>
+<li>C) Amazon EMR with Spark Streaming</li>
+<li>D) AWS Glue ETL jobs on a schedule</li>
+</ul>
+<p><em>Explanation: Kinesis Data Firehose is fully managed and requires no custom code — it directly delivers streaming data to S3, Redshift, or Elasticsearch. Data Streams requires custom consumers, EMR is heavy lift, and Glue is for batch ETL.</em></p>
+
+<p><strong>Q2:</strong> A data engineer wants to query raw CSV files in S3 using SQL without loading them into a database. Which service should be used?</p>
+<ul>
+<li>A) Amazon RDS</li>
+<li>B) Amazon DynamoDB</li>
+<li>C) Amazon Athena ✓</li>
+<li>D) Amazon Redshift</li>
+</ul>
+<p><em>Explanation: Amazon Athena is serverless and allows SQL queries directly on S3 data without loading. It reads files in-place and supports formats like CSV, Parquet, ORC, JSON.</em></p>
+
+<p><strong>Q3:</strong> Which file format provides the BEST performance for columnar analytics queries on large ML datasets stored in Amazon S3?</p>
+<ul>
+<li>A) CSV</li>
+<li>B) JSON</li>
+<li>C) XML</li>
+<li>D) Apache Parquet ✓</li>
+</ul>
+<p><em>Explanation: Parquet is a columnar format with excellent compression and predicate pushdown support. Columnar formats allow reading only the required columns, dramatically reducing I/O for analytical queries.</em></p>

package/content/series/luyen-thi/luyen-thi-aws-ml-specialty/chapters/01-phan-1-data-engineering/lessons/02-bai-2-data-transformation.md

@@ -0,0 +1,183 @@
+---
+id: 621b7555-2901-469d-8b0b-a800506c8212
+title: 'Bài 2: Data Transformation & Feature Engineering'
+slug: bai-2-data-transformation
+description: >-
+  SageMaker Processing Jobs cho data prep. SageMaker Feature Store.
+  Xử lý missing values, encoding, normalization, scaling.
+  Text preprocessing, imbalanced data techniques.
+duration_minutes: 60
+is_free: true
+video_url: null
+sort_order: 2
+section_title: "Phần 1: Data Engineering (20%)"
+course:
+  id: 019c9619-lt02-7002-c002-lt0200000002
+  title: 'Luyện thi AWS Certified Machine Learning - Specialty'
+  slug: luyen-thi-aws-ml-specialty
+---
+
+<div style="text-align: center; margin: 2rem 0;">
+<img src="/storage/uploads/2026/04/aws-mls-bai2-feature-engineering.png" alt="AWS ML Data Transformation Pipeline" style="max-width: 800px; width: 100%; border-radius: 12px;" />
+<p><em>Feature Engineering & Data Transformation: Glue, SageMaker Data Wrangler, và xử lý missing values</em></p>
+</div>
+
+<h2 id="overview"><strong>1. Data Transformation trong ML Pipeline</strong></h2>
+
+<p>Trước khi train model, raw data phải qua nhiều bước transformation. Đây là nguồn gốc của câu nói nổi tiếng: <em>"Garbage in, garbage out"</em>. Đề thi MLS-C01 thường hỏi kỹ thuật xử lý data và tools phù hợp.</p>
+
+<h2 id="processing-jobs"><strong>2. SageMaker Processing Jobs</strong></h2>
+
+<p><strong>SageMaker Processing Jobs</strong> là managed service để chạy data processing scripts (Python, Spark) trên ephemeral compute clusters.</p>
+
+<table>
+<thead><tr><th>Processor Type</th><th>Framework</th><th>Use Case</th></tr></thead>
+<tbody>
+<tr><td><strong>ScriptProcessor</strong></td><td>Custom Docker container</td><td>Any custom script</td></tr>
+<tr><td><strong>SKLearnProcessor</strong></td><td>scikit-learn</td><td>Classic ML preprocessing</td></tr>
+<tr><td><strong>PySparkProcessor</strong></td><td>Apache Spark</td><td>Large-scale distributed processing</td></tr>
+<tr><td><strong>FrameworkProcessor</strong></td><td>TensorFlow/PyTorch</td><td>Deep learning data prep</td></tr>
+</tbody>
+</table>
+
+<pre><code class="language-text">SageMaker Processing Job Flow:
+
+S3 (input data)
+      ↓
+┌─────────────────────┐
+│  Processing Job     │
+│  (compute cluster)  │
+│                     │
+│  - Preprocess data  │
+│  - Feature engineer │
+│  - Split train/test │
+└─────────────────────┘
+      ↓
+S3 (output: train/, validation/, test/)
+</code></pre>
+
+<h2 id="missing-values"><strong>3. Xử lý Missing Values</strong></h2>
+
+<table>
+<thead><tr><th>Strategy</th><th>Method</th><th>When to Use</th></tr></thead>
+<tbody>
+<tr><td><strong>Deletion</strong></td><td>Drop rows/columns</td><td>MCAR, ít missing (&lt;5%)</td></tr>
+<tr><td><strong>Mean/Median Imputation</strong></td><td>Điền giá trị trung bình</td><td>Numeric, MCAR/MAR</td></tr>
+<tr><td><strong>Mode Imputation</strong></td><td>Điền giá trị phổ biến nhất</td><td>Categorical</td></tr>
+<tr><td><strong>KNN Imputation</strong></td><td>Dùng K neighbors gần nhất</td><td>Patterns in data, không quá lớn</td></tr>
+<tr><td><strong>Model-based (MICE)</strong></td><td>Multiple imputation</td><td>Complex missingness patterns</td></tr>
+<tr><td><strong>Indicator Feature</strong></td><td>Thêm cột is_missing</td><td>Khi missingness chứa thông tin</td></tr>
+</tbody>
+</table>
+
+<blockquote>
+<p><strong>Exam tip:</strong> Ba loại missing data: <strong>MCAR</strong> (Missing Completely At Random) — deletion an toàn; <strong>MAR</strong> (Missing At Random) — imputation phù hợp; <strong>MNAR</strong> (Missing Not At Random) — cần indicator feature hoặc domain knowledge.</p>
+</blockquote>
+
+<h2 id="encoding"><strong>4. Categorical Encoding</strong></h2>
+
+<table>
+<thead><tr><th>Encoding</th><th>Method</th><th>When to Use</th><th>Issues</th></tr></thead>
+<tbody>
+<tr><td><strong>One-Hot Encoding</strong></td><td>Binary columns mỗi category</td><td>Nominal (no order), ít categories</td><td>High cardinality → curse of dimensionality</td></tr>
+<tr><td><strong>Label Encoding</strong></td><td>0, 1, 2, 3...</td><td>Ordinal (có thứ tự)</td><td>Implies false order for nominal</td></tr>
+<tr><td><strong>Target Encoding</strong></td><td>Mean of target per category</td><td>High cardinality nominal</td><td>Data leakage risk nếu không cẩn thận</td></tr>
+<tr><td><strong>Embeddings</strong></td><td>Dense vector representation</td><td>Text, high cardinality</td><td>Cần đủ data để learn</td></tr>
+</tbody>
+</table>
+
+<h2 id="scaling"><strong>5. Normalization & Scaling</strong></h2>
+
+<table>
+<thead><tr><th>Technique</th><th>Formula</th><th>Output Range</th><th>Best For</th></tr></thead>
+<tbody>
+<tr><td><strong>Min-Max Normalization</strong></td><td>(x - min) / (max - min)</td><td>[0, 1]</td><td>Neural networks, distance-based</td></tr>
+<tr><td><strong>Standardization (Z-score)</strong></td><td>(x - mean) / std</td><td>Mean=0, SD=1</td><td>Linear models, SVM, PCA</td></tr>
+<tr><td><strong>Robust Scaler</strong></td><td>(x - median) / IQR</td><td>Centered</td><td>Outliers present</td></tr>
+<tr><td><strong>Log Transform</strong></td><td>log(x)</td><td>Compressed</td><td>Skewed distributions</td></tr>
+</tbody>
+</table>
+
+<h2 id="imbalanced"><strong>6. Xử lý Imbalanced Data</strong></h2>
+
+<p>Class imbalance (e.g., fraud detection: 99% normal, 1% fraud) khiến model bias về majority class.</p>
+
+<table>
+<thead><tr><th>Technique</th><th>Method</th><th>Direction</th></tr></thead>
+<tbody>
+<tr><td><strong>Oversampling</strong></td><td>Duplicate minority class samples</td><td>↑ minority</td></tr>
+<tr><td><strong>SMOTE</strong></td><td>Synthetic Minority Oversampling Technique — generate synthetic samples</td><td>↑ minority</td></tr>
+<tr><td><strong>Undersampling</strong></td><td>Remove majority class samples</td><td>↓ majority</td></tr>
+<tr><td><strong>Class Weights</strong></td><td>Penalize misclassification of minority more</td><td>No data change</td></tr>
+<tr><td><strong>Ensemble Methods</strong></td><td>BalancedBagging, EasyEnsemble</td><td>Algorithm-level</td></tr>
+</tbody>
+</table>
+
+<blockquote>
+<p><strong>Exam tip:</strong> Metric phù hợp cho imbalanced data: <strong>F1 Score, AUC-ROC, Precision-Recall</strong> — KHÔNG dùng Accuracy (misleading). AWS SageMaker Clarify có thể detect class imbalance.</p>
+</blockquote>
+
+<h2 id="feature-store"><strong>7. SageMaker Feature Store</strong></h2>
+
+<p><strong>SageMaker Feature Store</strong> là centralized repository để store, share và reuse ML features.</p>
+
+<pre><code class="language-text">Feature Store Architecture:
+
+          Feature Groups
+         ┌──────────────────────────────┐
+         │  user_features               │
+         │  ┌──────┬────────┬────────┐  │
+         │  │ id   │ age    │ recency│  │
+         │  └──────┴────────┴────────┘  │
+         └──────────────────────────────┘
+               ↓ writes              ↑ reads
+    ┌──────────────────┐   ┌──────────────────┐
+    │  Offline Store   │   │  Online Store    │
+    │  (S3 - training) │   │  (DynamoDB -     │
+    │  batch reads     │   │  low-latency     │
+    │                  │   │  inference)      │
+    └──────────────────┘   └──────────────────┘
+</code></pre>
+
+<h2 id="cheat-sheet"><strong>8. Cheat Sheet — Feature Engineering</strong></h2>
+
+<table>
+<thead><tr><th>Problem</th><th>Solution</th></tr></thead>
+<tbody>
+<tr><td>High cardinality categorical</td><td>Target encoding hoặc embeddings</td></tr>
+<tr><td>Missing values (numeric)</td><td>Median imputation + indicator feature</td></tr>
+<tr><td>Skewed distribution</td><td>Log transform hoặc Box-Cox</td></tr>
+<tr><td>Outliers</td><td>Robust Scaler hoặc clip/winsorize</td></tr>
+<tr><td>Imbalanced classes</td><td>SMOTE + class weights + AUC metric</td></tr>
+<tr><td>Reuse features across teams</td><td>SageMaker Feature Store</td></tr>
+</tbody>
+</table>
+
+<h2 id="practice"><strong>9. Practice Questions</strong></h2>
+
+<p><strong>Q1:</strong> A dataset for fraud detection has 98% negative (non-fraud) and 2% positive (fraud) examples. Which metric is MOST appropriate to evaluate the model?</p>
+<ul>
+<li>A) Accuracy</li>
+<li>B) R-squared</li>
+<li>C) AUC-ROC ✓</li>
+<li>D) Mean Absolute Error</li>
+</ul>
+<p><em>Explanation: Accuracy is misleading for imbalanced data (predicting all negative gives 98% accuracy). AUC-ROC measures the model's ability to distinguish classes across all thresholds, making it ideal for imbalanced classification.</em></p>
+
+<p><strong>Q2:</strong> Which technique generates SYNTHETIC samples to address class imbalance?</p>
+<ul>
+<li>A) Random undersampling</li>
+<li>B) SMOTE (Synthetic Minority Oversampling Technique) ✓</li>
+<li>C) Class weighting</li>
+<li>D) Feature scaling</li>
+</ul>
+<p><em>Explanation: SMOTE creates new synthetic samples for the minority class by interpolating between existing minority class examples, rather than just duplicating them.</em></p>
+
+<p><strong>Q3:</strong> A company wants to share engineered features between their training pipeline and real-time inference service. Which SageMaker feature addresses this?</p>
+<ul>
+<li>A) SageMaker Processing Jobs</li>
+<li>B) SageMaker Experiments</li>
+<li>C) SageMaker Feature Store ✓</li>
+<li>D) SageMaker Data Wrangler</li>
+</ul>
+<p><em>Explanation: SageMaker Feature Store provides both an offline store (S3, for batch training) and online store (DynamoDB-backed, for low-latency real-time inference), ensuring feature consistency between training and serving.</em></p>

package/content/series/luyen-thi/luyen-thi-aws-ml-specialty/chapters/01-phan-1-data-engineering/lessons/03-bai-3-data-analysis.md

@@ -0,0 +1,159 @@
+---
+id: 1a81b42d-c09e-43ef-b9f6-3158ca64b6c1
+title: 'Bài 3: Data Analysis & Visualization'
+slug: bai-3-data-analysis
+description: >-
+  EDA trên SageMaker notebooks. Amazon Athena cho SQL analytics.
+  Amazon QuickSight cho BI dashboards. Phát hiện data quality issues.
+  Detect class imbalance, outliers, correlations, data drift.
+duration_minutes: 45
+is_free: true
+video_url: null
+sort_order: 3
+section_title: "Phần 1: Data Engineering (20%)"
+course:
+  id: 019c9619-lt02-7002-c002-lt0200000002
+  title: 'Luyện thi AWS Certified Machine Learning - Specialty'
+  slug: luyen-thi-aws-ml-specialty
+---
+
+<div style="text-align: center; margin: 2rem 0;">
+<img src="/storage/uploads/2026/04/aws-mls-bai3-eda-data-analysis.png" alt="Exploratory Data Analysis trên AWS" style="max-width: 800px; width: 100%; border-radius: 12px;" />
+<p><em>EDA & Data Analysis: thống kê mô tả, phát hiện outliers, feature correlation trên AWS</em></p>
+</div>
+
+<h2 id="eda"><strong>1. Exploratory Data Analysis (EDA)</strong></h2>
+
+<p><strong>EDA</strong> là bước phân tích dữ liệu ban đầu để hiểu structure, patterns, và anomalies trước khi modeling. SageMaker cung cấp nhiều tools để thực hiện EDA ở scale lớn.</p>
+
+<h2 id="eda-tools"><strong>2. AWS Tools cho Data Analysis</strong></h2>
+
+<table>
+<thead><tr><th>Tool</th><th>Use Case</th><th>Interface</th></tr></thead>
+<tbody>
+<tr><td><strong>SageMaker Studio Notebooks</strong></td><td>Interactive EDA, Python/R analysis</td><td>JupyterLab-based IDE</td></tr>
+<tr><td><strong>SageMaker Data Wrangler</strong></td><td>Visual data prep, 300+ transforms, auto-insights</td><td>Drag-and-drop GUI</td></tr>
+<tr><td><strong>Amazon Athena</strong></td><td>SQL queries on S3 data</td><td>SQL console</td></tr>
+<tr><td><strong>Amazon QuickSight</strong></td><td>BI dashboards, executive reports</td><td>Visual BI tool</td></tr>
+<tr><td><strong>Amazon Redshift</strong></td><td>Large-scale data warehousing, SQL analytics</td><td>SQL</td></tr>
+<tr><td><strong>AWS Glue DataBrew</strong></td><td>No-code data profiling và cleaning recipes</td><td>Visual tool</td></tr>
+</tbody>
+</table>
+
+<blockquote>
+<p><strong>Exam tip:</strong> <strong>Data Wrangler</strong> = visual data prep cho ML (generates SageMaker Processing code). <strong>DataBrew</strong> = data analyst/BI (no ML context). <strong>QuickSight</strong> = BI dashboards for business users, không phải ML.</p>
+</blockquote>
+
+<h2 id="data-quality"><strong>3. Data Quality Issues</strong></h2>
+
+<p>Đề thi thường hỏi về nhận biết và xử lý các vấn đề chất lượng data phổ biến.</p>
+
+<table>
+<thead><tr><th>Issue</th><th>Detection Method</th><th>Impact on Model</th></tr></thead>
+<tbody>
+<tr><td><strong>Missing Values</strong></td><td>Null counts, missing rate per column</td><td>Errors, biased results</td></tr>
+<tr><td><strong>Outliers</strong></td><td>Box plots, Z-score > 3, IQR method</td><td>Skewed weights, poor generalization</td></tr>
+<tr><td><strong>Class Imbalance</strong></td><td>Class distribution histogram</td><td>Biased toward majority class</td></tr>
+<tr><td><strong>Feature Correlation</strong></td><td>Correlation matrix, VIF score</td><td>Multicollinearity → unstable coefficients</td></tr>
+<tr><td><strong>Data Leakage</strong></td><td>Features with suspiciously high correlation to target</td><td>Over-optimistic eval, fails in production</td></tr>
+<tr><td><strong>Distribution Skew</strong></td><td>Histogram, skewness metric</td><td>Violated model assumptions</td></tr>
+</tbody>
+</table>
+
+<h3 id="data-leakage"><strong>3.1. Data Leakage — Critical Concept</strong></h3>
+
+<p><strong>Data leakage</strong> là khi information từ outside the training set rò rỉ vào features, khiến model có accuracy cao trong training nhưng thất bại khi production.</p>
+
+<pre><code class="language-text">Common Data Leakage Patterns:
+
+❌ Target leakage:
+   Feature "loan_default_flag" → predicting "credit_risk"
+   (feature derived from target)
+
+❌ Future data leakage:
+   Using tomorrow's stock price to predict today's trade
+
+❌ Train/test contamination:
+   Scaling data BEFORE splitting (test mean leaks into train)
+
+✅ Correct approach:
+   Split data FIRST → fit scaler on train only → transform both
+</code></pre>
+
+<blockquote>
+<p><strong>Exam tip:</strong> Always <strong>split before transforming</strong>. StandardScaler.fit() chỉ được gọi trên training set. Sau đó transform() trên cả train và test. Fit+transform trên toàn bộ dataset là data leakage.</p>
+</blockquote>
+
+<h2 id="athena"><strong>4. Amazon Athena</strong></h2>
+
+<p>Athena cho phép chạy SQL queries directly trên S3 without loading data vào database. <strong>Pay per scan</strong> — tối ưu bằng cách dùng Parquet + partitioning.</p>
+
+<pre><code class="language-text">Cost Optimization Tips:
+┌────────────────────────────────────────────────┐
+│  Partition data by date/region/category:       │
+│  s3://bucket/data/year=2024/month=01/          │
+│  → Query chỉ scan the required partitions      │
+│                                                │
+│  Use columnar formats (Parquet/ORC):           │
+│  → Read only needed columns                   │
+│                                               │
+│  Compress data (Snappy, Gzip):                │
+│  → Reduce scan size → reduce cost             │
+└────────────────────────────────────────────────┘
+</code></pre>
+
+<h2 id="quicksight"><strong>5. Amazon QuickSight</strong></h2>
+
+<p>QuickSight là <strong>BI service</strong>, không phải ML tool. Key feature: <strong>SPICE</strong> (in-memory engine) cho fast dashboards.</p>
+
+<table>
+<thead><tr><th>Feature</th><th>Description</th></tr></thead>
+<tbody>
+<tr><td><strong>SPICE</strong></td><td>Super-fast Parallel In-memory Calculation Engine — cached dataset</td></tr>
+<tr><td><strong>ML Insights</strong></td><td>Built-in anomaly detection, forecasting trên dashboards</td></tr>
+<tr><td><strong>Q (NLQ)</strong></td><td>Natural language queries — "show me sales by region last month"</td></tr>
+</tbody>
+</table>
+
+<h2 id="cheat-sheet"><strong>6. Cheat Sheet — Analysis Tools</strong></h2>
+
+<table>
+<thead><tr><th>Scenario</th><th>Tool</th></tr></thead>
+<tbody>
+<tr><td>Interactive Python EDA on large data</td><td>SageMaker Studio Notebooks</td></tr>
+<tr><td>Visual no-code ML data prep</td><td>SageMaker Data Wrangler</td></tr>
+<tr><td>SQL on S3 data (serverless)</td><td>Amazon Athena</td></tr>
+<tr><td>Business dashboards và reporting</td><td>Amazon QuickSight</td></tr>
+<tr><td>Large data warehouse SQL</td><td>Amazon Redshift</td></tr>
+<tr><td>No-code data profiling recipes</td><td>AWS Glue DataBrew</td></tr>
+</tbody>
+</table>
+
+<h2 id="practice"><strong>7. Practice Questions</strong></h2>
+
+<p><strong>Q1:</strong> A data scientist standardized features using the mean and standard deviation of the ENTIRE dataset before splitting into train/test sets. What problem does this cause?</p>
+<ul>
+<li>A) Model underfitting</li>
+<li>B) Slow training convergence</li>
+<li>C) Data leakage from test set statistics into training ✓</li>
+<li>D) Class imbalance</li>
+</ul>
+<p><em>Explanation: Fitting a scaler on the entire dataset causes data leakage — the test set statistics (mean, std) influence the training data transformation. Always fit transformers on training data only, then apply the fitted transformer to both train and test sets.</em></p>
+
+<p><strong>Q2:</strong> A business analyst needs to create executive dashboards from S3 data with fast interactive visualizations. Which AWS service is BEST suited?</p>
+<ul>
+<li>A) Amazon SageMaker Studio</li>
+<li>B) Amazon Athena</li>
+<li>C) Amazon QuickSight ✓</li>
+<li>D) AWS Glue DataBrew</li>
+</ul>
+<p><em>Explanation: Amazon QuickSight is the AWS BI service designed for business dashboards and visualizations with SPICE in-memory engine for fast interactive queries. SageMaker Studio is for ML development, Athena is SQL querying, DataBrew is data preparation.</em></p>
+
+<p><strong>Q3:</strong> A model trained on customer churn data has 99% training accuracy but performs poorly on production data. Investigation shows "days_since_last_call" is more predictive than expected. What is the MOST likely cause?</p>
+<ul>
+<li>A) Overfitting due to too many features</li>
+<li>B) Underfitting due to low model complexity</li>
+<li>C) Data leakage — the feature is derived from post-churn activity ✓</li>
+<li>D) Class imbalance</li>
+</ul>
+<p><em>Explanation: This is classic target leakage — "days_since_last_call" may reflect churn behavior after the fact (customers call to cancel). This future information isn't available in production, causing the model to fail.</em></p>