Correct Answer: A  🗳️

Explanation: Only visible for PremiumVCEDump members. You can sign-up / login (it's free).

Correct Answer:

Explanation:
Input feature distributions differ from training data: Analyze dataset drift metrics Model accuracy drops without code changes: Review prediction and ground truth trends Endpoint latency increases under load: Investigate scaling and infrastructure metrics When input feature distributions differ from training data , the correct action is to analyze dataset drift metrics . Azure Machine Learning model monitoring detects data drift by comparing the statistical distributions of production model inputs against reference data, commonly the original training dataset.
Supported measures include Population Stability Index, Jensen-Shannon distance, normalized Wasserstein distance, and statistical tests such as Kolmogorov-Smirnov.
When model accuracy drops without code changes , the next investigation should focus on prediction and ground-truth trends . Azure Machine Learning model-performance monitoring compares production predictions with collected actual outcomes and can calculate classification metrics such as accuracy, precision, and recall. A declining score without deployment changes may indicate concept drift, prediction drift, or changing relationships between input features and target outcomes.
When endpoint latency increases under load , the issue is operational rather than primarily statistical. The team should investigate scaling and infrastructure metrics , including request latency, requests per minute, CPU/memory utilization, throttling, and replica capacity. Microsoft recommends using endpoint metrics to determine whether compute must scale up or out.
Rebuild the inference container image is not indicated by any of the observed signals.
Study Guide Reference: Implement machine learning model lifecycle and operations - production monitoring, data drift, model-performance monitoring, endpoint observability, and scaling.

Correct Answer:

Explanation:

Correct Answer:

Explanation:
A system requesting predictions synchronously during customer interactions needs sub-second responses, while a system submitting files with millions of records can tolerate minutes of processing time. For real-time synchronous serving, a Managed Online Endpoint provisions a persistent always-on container behind an HTTPS REST endpoint that returns predictions within milliseconds. For large-batch asynchronous scoring, a Batch Endpoint accepts a data asset input, distributes scoring across a compute cluster, and writes results back to storage. Online endpoints support auto-scaling based on request volume and traffic splitting. Batch endpoints are invoked on-demand or on a schedule, automatically provisioning and de-provisioning compute, keeping costs low for intermittent large jobs. Each deployment type is purpose-built for its usage pattern and should not be swapped.
Microsoft Learn Reference Topic: Deploy and score models with managed online endpoints and batch endpoints - Azure Machine Learning