Practice
Solution
Step 1: Identify the role of each component.
Embedding tables handle sparse features, fully connected layers process dense features, and batch normalization normalizes inputs.Step 2: Eliminate wrong options.
Embedding tables (A) and fully connected layers (C) do not specifically capture interactions. Batch normalization (D) is unrelated to feature interactions.Final Answer:
Option A -> Option AQuick Check:
Cross-product for interactions in DLRM. [OK]
Solution
Step 1: Identify the component for real-time scoring.
The real-time scoring engine is designed to evaluate transactions as they occur.Step 2: Eliminate wrong options.
Batch processing engine (A) is for batch jobs, Data warehouse (C) is for storage, and Offline model training (D) is for model development.Final Answer:
Option A -> Option AQuick Check:
Real-time scoring needs a real-time engine. [OK]
Solution
Step 1: Consider sophistication of bots.
Sophisticated bots can mimic device fingerprints but struggle with human-like behavior.Step 2: Eliminate wrong options.
Device fingerprinting is easier to spoof; implementation ease is irrelevant to detection capability.Final Answer:
Option A -> Option AQuick Check:
Sophisticated bots struggle with human behavior [OK]
Solution
Step 1: Understand lineage tracking purpose
Lineage tracking ensures that all steps and data leading to a model's creation are documented, aiding reproducibility.Step 2: Eliminate wrong options
Increased model training time is incorrect as lineage doesn't affect training time. Higher model deployment costs is wrong because deployment costs aren't directly related to lineage. Decreased model accuracy is incorrect as accuracy isn't directly impacted by lineage tracking.Final Answer:
Option A -> Option AQuick Check:
Lineage = Reproducibility [OK]
Solution
Step 1: Consider scaling impacts.
As query volume increases, the database must handle more retrieval requests, potentially becoming a bottleneck.Step 2: Eliminate wrong options.
Models scale with compute resources, but database I/O can become a limiting factor.Final Answer:
Option B -> Option BQuick Check:
Database I/O limits scale. [OK]
