Microsoft AI-300 Practice Test 40
Question 390
During a production Azure Machine Learning model lifecycle incident, the following condition occurs: A real-time predictor appears healthy by mean request latency while high-value users face multi-second waits at the 99th percentile after a traffic spike. The operator must safeguard training reproducibility and serving continuity. Which diagnostic evidence most directly distinguishes the described AI operations failure?
- Inspect request payload schema, scoring script init/run implementation, model input signature, container logs and test invocation.
- Inspect reference data time window, drift feature metrics, alert threshold, seasonal segmentation and actual model outcomes.
- Examine Azure Monitor request latency percentiles, response codes, deployment load, compute utilization and per-client cohorts.
- Inspect model retraining pipeline graph, evaluation outputs, baseline comparison, deployment step conditions and release records.
Explanation
Correct Answer
C:Examine Azure Monitor request latency percentiles, response codes, deployment load, compute utilization and per-client cohorts. This is the most relevant evidence for endpoint latency average conceals tail degradation. Average endpoint latency can hide slow outliers; tail distributions and cohort behavior are needed for user-facing service assurance. The matching controlled remediation is: Configure tail-latency and error-rate dashboards with capacity remedies appropriate to the measured bottleneck.
Incorrect Answers
A:Inspect request payload schema, scoring script init/run implementation, model input signature, container logs and test invocation. This would investigate endpoint scoring script expects wrong json schema rather than the documented endpoint latency average conceals tail degradation issue. The relevant investigation is: Examine Azure Monitor request latency percentiles, response codes, deployment load, compute utilization and per-client cohorts.
B:Inspect reference data time window, drift feature metrics, alert threshold, seasonal segmentation and actual model outcomes. This would investigate data drift monitor uses wrong reference season rather than the documented endpoint latency average conceals tail degradation issue. The relevant investigation is: Examine Azure Monitor request latency percentiles, response codes, deployment load, compute utilization and per-client cohorts.
D:Inspect model retraining pipeline graph, evaluation outputs, baseline comparison, deployment step conditions and release records. This would investigate retraining pipeline deploys without model quality gate rather than the documented endpoint latency average conceals tail degradation issue. The relevant investigation is: Examine Azure Monitor request latency percentiles, response codes, deployment load, compute utilization and per-client cohorts.
Question 391
As an MLOps engineer reviews a model training or inference pipeline, the following condition occurs: An AutoML classification search reports near-perfect accuracy because the supplied training dataset includes a field recorded only after the real customer outcome is known. The resolution must preserve quality gates, documented artifacts and rollback options. What measured outcome validates the solution while preserving the stated constraints?
- An injected null-rate increase triggers a targeted alert while valid fluctuations remain within control limits.
- Holdout performance is credible against production-like inputs and candidate selection no longer uses post-outcome fields.
- Selected candidates improve the approved fraud-detection target while documented false-positive trade-offs remain acceptable.
- The approved run contains a loadable model artifact and the registration stage resolves its exact run and model path.
Explanation
Correct Answer
B:Holdout performance is credible against production-like inputs and candidate selection no longer uses post-outcome fields. Automated model search cannot correct information leakage caused by improperly constructed input data and validation boundaries. a direct corrective action is to remove target-leakage columns and rerun the AutoML search with an appropriate time-aware validation split and realistic available features. This matters here because as an MLOps engineer reviews a model training or inference pipeline, the following condition occurs: An AutoML….
Incorrect Answers
A:An injected null-rate increase triggers a targeted alert while valid fluctuations remain within control limits. That addresses a different configuration issue rather than the main requirement. Verify instead: Holdout performance is credible against production-like inputs and candidate selection no longer uses post-outcome fields.
C:Selected candidates improve the approved fraud-detection target while documented false-positive trade-offs remain acceptable. That addresses a different configuration issue rather than the main requirement. Verify instead: Holdout performance is credible against production-like inputs and candidate selection no longer uses post-outcome fields.
D:The approved run contains a loadable model artifact and the registration stage resolves its exact run and model path. That addresses a different configuration issue rather than the main requirement. Verify instead: Holdout performance is credible against production-like inputs and candidate selection no longer uses post-outcome fields.
Question 392
While deploying reproducible Azure Machine Learning infrastructure, the following condition occurs: A Bicep deployment provisions an Azure ML workspace but its associated storage, Key Vault and private endpoints are created after the workspace references them, producing intermittent deployment failures. The change must remain limited to authorized workspaces and avoid unreviewed production impact. Which production-safe remediation should the engineer apply to this AI workflow?
- Add Bicep validation, targeted what-if reviews and a controlled environment promotion stage before production apply.
- Request approved additional quota or rescope the job to a permitted compute size and region while retaining necessary GPU capability.
- Require protected pull requests and automated component tests before changes to production training code are merged.
- Declare proper resource references or explicit dependencies and staged network prerequisites in the reviewed Bicep deployment.
Explanation
Correct Answer
D:Declare proper resource references or explicit dependencies and staged network prerequisites in the reviewed Bicep deployment. This targets bicep workspace declaration misses dependent private resources. Declarative infrastructure still requires a valid resource dependency graph and stable networking prerequisites; syntax validation alone does not enforce desired provisioning order. Verify the failure through: Inspect Azure deployment operations, Bicep resource references, implicit dependency graph, private endpoint target IDs and pipeline parameter order. Validate success with: Repeated deployments converge on a valid workspace and all linked dependencies without manual reruns or temporary public access. This matters here because while deploying reproducible Azure Machine Learning infrastructure, the following condition occurs: A Bicep….
Incorrect Answers
A:Add Bicep validation, targeted what-if reviews and a controlled environment promotion stage before production apply. This could address iac workflow lacks repeatable infrastructure validation, but it does not solve the specified bicep workspace declaration misses dependent private resources failure. The matching remediation is: Declare proper resource references or explicit dependencies and staged network prerequisites in the reviewed Bicep deployment.
B:Request approved additional quota or rescope the job to a permitted compute size and region while retaining necessary GPU capability. This could address compute cluster cannot allocate requested gpu quota, but it does not solve the specified bicep workspace declaration misses dependent private resources failure. The matching remediation is: Declare proper resource references or explicit dependencies and staged network prerequisites in the reviewed Bicep deployment.
C:Require protected pull requests and automated component tests before changes to production training code are merged. This could address notebook merge bypasses protected evaluation tests, but it does not solve the specified bicep workspace declaration misses dependent private resources failure. The matching remediation is: Declare proper resource references or explicit dependencies and staged network prerequisites in the reviewed Bicep deployment.
Question 393
During a Microsoft Foundry generative AI deployment review, the following condition occurs: A customer assistant must handle Turkish and Arabic queries, yet the chosen model is approved based only on English benchmark scores and performs poorly in the required languages. The deployment must retain governed identities, endpoint contracts and auditable release history. Which acceptance test shows the AI operations defect is corrected?
- The workflow authenticates through a governed identity after old secrets are disabled and completes the intended evaluation without privileged keys in source control.
- The launched assistant meets approved quality thresholds for the supported languages without hiding poor results in a combined aggregate.
- A production-sized document completes evaluation without unintended context loss or unsupported token-limit errors.
- The prototype maintains acceptable response time with lower recurring idle capacity cost and production capacity remains unaffected.
Explanation
Correct Answer
B:The launched assistant meets approved quality thresholds for the supported languages without hiding poor results in a combined aggregate. Model selection for a multilingual workload requires evaluation in the actual languages and use cases rather than generic model rankings. a direct corrective action is to compare available candidate models on representative multilingual datasets and select one that meets the target-language quality and security gates.
Incorrect Answers
A:The workflow authenticates through a governed identity after old secrets are disabled and completes the intended evaluation without privileged keys in source control. That addresses a different configuration issue rather than the main requirement. Verify instead: The launched assistant meets approved quality thresholds for the supported languages without hiding poor results in a combined aggregate.
C:A production-sized document completes evaluation without unintended context loss or unsupported token-limit errors. That addresses a different configuration issue rather than the main requirement. Verify instead: The launched assistant meets approved quality thresholds for the supported languages without hiding poor results in a combined aggregate.
D:The prototype maintains acceptable response time with lower recurring idle capacity cost and production capacity remains unaffected. That addresses a different configuration issue rather than the main requirement. Verify instead: The launched assistant meets approved quality thresholds for the supported languages without hiding poor results in a combined aggregate.
Question 394
As an MLOps engineer reviews a model training or inference pipeline, the following condition occurs: An Azure ML training pipeline intermittently starts training before its feature-engineering output is ready because the training component references a static path instead of the upstream component's declared output. The resolution must preserve quality gates, documented artifacts and rollback options. Which acceptance test shows the AI operations defect is corrected?
- Repeat runs show explainable variance with recorded seeds and identical inputs where deterministic execution is supported.
- The feature job completes before training consumes its versioned output in repeated orchestrated executions.
- Trials execute predictably without persistent quota-induced queueing, and tuning still explores the intended search space.
- A representative rollback test restores known-good predictions and endpoint health within the recovery target.
Explanation
Correct Answer
B:The feature job completes before training consumes its versioned output in repeated orchestrated executions. Component dependency edges in Azure ML are determined by declared data bindings, not by visual position in a notebook or YAML file. a direct corrective action is to bind training input directly to the feature component's typed output to establish the correct pipeline dependency.
Incorrect Answers
A:Repeat runs show explainable variance with recorded seeds and identical inputs where deterministic execution is supported. That addresses a different configuration issue rather than the main requirement. Verify instead: The feature job completes before training consumes its versioned output in repeated orchestrated executions.
C:Trials execute predictably without persistent quota-induced queueing, and tuning still explores the intended search space. That addresses a different configuration issue rather than the main requirement. Verify instead: The feature job completes before training consumes its versioned output in repeated orchestrated executions.
D:A representative rollback test restores known-good predictions and endpoint health within the recovery target. That addresses a different configuration issue rather than the main requirement. Verify instead: The feature job completes before training consumes its versioned output in repeated orchestrated executions.
Question 395
As an MLOps engineer reviews a model training or inference pipeline, the following condition occurs: Two Azure ML training runs produce different validation scores but the team cannot determine whether learning rate or data version changed because the Python scripts log only final accuracy. The resolution must preserve quality gates, documented artifacts and rollback options. Select TWO actions: one decisive diagnostic and its corresponding targeted remediation.
- Inspect MLflow tracking URI and experiment name, run parameter history, metric logs, artifact URIs and the input data version of each job.
- Version the transformation component and inputs explicitly and disable or invalidate reuse where the effective computation has changed.
- Add MLflow parameter and dataset-version logging to the training script and group runs under a stable named experiment.
- Add appropriate privacy-respecting subgroup performance and fairness evaluation and document mitigation before promoting the model.
- Compare notebook kernel package list, managed job environment asset, dependency lock file and the remote import traceback.
Explanation
Correct Answers
A:Inspect MLflow tracking URI and experiment name, run parameter history, metric logs, artifact URIs and the input data version of each job. This is the most relevant evidence for mlflow experiment logs omit run parameters. MLflow experiment tracking associates metadata with run IDs, but unlogged hyperparameters and datasets cannot be recovered reliably from a final metric alone. The matching controlled remediation is: Add MLflow parameter and dataset-version logging to the training script and group runs under a stable named experiment. This matters here because as an MLOps engineer reviews a model training or inference pipeline, the following condition occurs: Two Azure ML….
C:Add MLflow parameter and dataset-version logging to the training script and group runs under a stable named experiment. This targets mlflow experiment logs omit run parameters. MLflow experiment tracking associates metadata with run IDs, but unlogged hyperparameters and datasets cannot be recovered reliably from a final metric alone. Verify the failure through: Inspect MLflow tracking URI and experiment name, run parameter history, metric logs, artifact URIs and the input data version of each job. Validate success with: A reviewer compares both runs and identifies the exact code, data, hyperparameters and metrics used without reconstructing them by hand. This matters here because as an MLOps engineer reviews a model training or inference pipeline, the following condition occurs: Two Azure ML….
Incorrect Answers
B:Version the transformation component and inputs explicitly and disable or invalidate reuse where the effective computation has changed. This is associated with pipeline cache reuses stale transform artifact, not the essential evidence-and-fix pair for mlflow experiment logs omit run parameters. First examine: Inspect MLflow tracking URI and experiment name, run parameter history, metric logs, artifact URIs and the input data version of each job. Then correct: Add MLflow parameter and dataset-version logging to the training script and group runs under a stable named experiment.
D:Add appropriate privacy-respecting subgroup performance and fairness evaluation and document mitigation before promoting the model. This is associated with responsible ai evaluation omits demographic cohort slices, not the essential evidence-and-fix pair for mlflow experiment logs omit run parameters. First examine: Inspect MLflow tracking URI and experiment name, run parameter history, metric logs, artifact URIs and the input data version of each job. Then correct: Add MLflow parameter and dataset-version logging to the training script and group runs under a stable named experiment.
E:Compare notebook kernel package list, managed job environment asset, dependency lock file and the remote import traceback. This is associated with notebook experiment installs packages only in interactive kernel, not the essential evidence-and-fix pair for mlflow experiment logs omit run parameters. First examine: Inspect MLflow tracking URI and experiment name, run parameter history, metric logs, artifact URIs and the input data version of each job. Then correct: Add MLflow parameter and dataset-version logging to the training script and group runs under a stable named experiment.
Question 396
During a Foundry generative AI quality and observability incident, the following condition occurs: An evaluation compares chatbot answers against an automatically rewritten query rather than the original user intent, rewarding responses that miss the real troubleshooting question. The fix must preserve evaluation validity and avoid unnecessary user-data collection. Which TWO complementary choices identify the issue and correct it? Select TWO.
- Inspect safety evaluator coverage, adversarial retrieval examples, trusted instruction hierarchy, tool-action traces and current release criteria.
- Bind relevance evaluation to the authentic user request and assess query rewriting as a separate retrieval-stage metric.
- Include appropriate complete conversation histories and tool events in the supported agent evaluation workflow while preserving privacy protections.
- Review user input field mapping, generated search query, response text, evaluator prompt and evaluation row samples.
- Use relevant retrieval context, justified response limits and supported caching after verifying quality on evaluation examples.
Explanation
Correct Answers
B:Bind relevance evaluation to the authentic user request and assess query rewriting as a separate retrieval-stage metric. This targets relevance evaluator uses wrong intended user query. Query rewriting aids retrieval but should not silently redefine what the user's response needs to accomplish. Verify the failure through: Review user input field mapping, generated search query, response text, evaluator prompt and evaluation row samples. Validate success with: The pipeline correctly flags answers that fail the user's original task even when they match an intermediate search query. This matters here because an evaluation compares chatbot answers against an automatically rewritten query rather than the original user….
D:Review user input field mapping, generated search query, response text, evaluator prompt and evaluation row samples. This is the most relevant evidence for relevance evaluator uses wrong intended user query. Query rewriting aids retrieval but should not silently redefine what the user's response needs to accomplish. The matching controlled remediation is: Bind relevance evaluation to the authentic user request and assess query rewriting as a separate retrieval-stage metric. This matters here because an evaluation compares chatbot answers against an automatically rewritten query rather than the original user….
Incorrect Answers
A:Inspect safety evaluator coverage, adversarial retrieval examples, trusted instruction hierarchy, tool-action traces and current release criteria. This is associated with content safety evaluation omits prompt injection tests, not the essential evidence-and-fix pair for relevance evaluator uses wrong intended user query. First examine: Review user input field mapping, generated search query, response text, evaluator prompt and evaluation row samples. Then correct: Bind relevance evaluation to the authentic user request and assess query rewriting as a separate retrieval-stage metric.
C:Include appropriate complete conversation histories and tool events in the supported agent evaluation workflow while preserving privacy protections. This is associated with multi-turn agent evaluation uses isolated last message only, not the essential evidence-and-fix pair for relevance evaluator uses wrong intended user query. First examine: Review user input field mapping, generated search query, response text, evaluator prompt and evaluation row samples. Then correct: Bind relevance evaluation to the authentic user request and assess query rewriting as a separate retrieval-stage metric.
E:Use relevant retrieval context, justified response limits and supported caching after verifying quality on evaluation examples. This is associated with prompt truncation strategy increases generated-token spend, not the essential evidence-and-fix pair for relevance evaluator uses wrong intended user query. First examine: Review user input field mapping, generated search query, response text, evaluator prompt and evaluation row samples. Then correct: Bind relevance evaluation to the authentic user request and assess query rewriting as a separate retrieval-stage metric.
Question 397
While deploying reproducible Azure Machine Learning infrastructure, the following condition occurs: A training job reads a similarly named blob container containing last quarter's features because its Azure ML datastore URI targets the staging location rather than the approved production store. The change must remain limited to authorized workspaces and avoid unreviewed production impact. Which targeted Azure AI operations change best addresses the documented problem?
- Replace the stale credential with a supported workspace identity-based datastore access path or rotate the authorized credential through secrets management.
- Update the datastore or data asset binding to the governed storage path with an explicitly pinned version and validated read access.
- Assign the minimum permitted storage data access role to the job identity at the relevant container scope without granting secret-key access.
- Restrict the federated identity subject to the protected deployment environment or branch and enforce repository approval rules.
Explanation
Correct Answer
B:Update the datastore or data asset binding to the governed storage path with an explicitly pinned version and validated read access. This targets datastore uri selects the incorrect storage container. A datastore connection and data asset version identify where training inputs come from; paths must be validated independently from authentication success. Verify the failure through: Compare the datastore URI and backing storage container, recorded data asset path, job input mount path and expected data version checksum. Validate success with: The job consumes the intended dataset version and staging files are not silently mixed into production runs. This matters here because while deploying reproducible Azure Machine Learning infrastructure, the following condition occurs: A training job….
Incorrect Answers
A:Replace the stale credential with a supported workspace identity-based datastore access path or rotate the authorized credential through secrets management. This could address datastore authentication relies on expiring account key, but it does not solve the specified datastore uri selects the incorrect storage container failure. The matching remediation is: Update the datastore or data asset binding to the governed storage path with an explicitly pinned version and validated read access.
C:Assign the minimum permitted storage data access role to the job identity at the relevant container scope without granting secret-key access. This could address job identity lacks blob reader data-plane rights, but it does not solve the specified datastore uri selects the incorrect storage container failure. The matching remediation is: Update the datastore or data asset binding to the governed storage path with an explicitly pinned version and validated read access.
D:Restrict the federated identity subject to the protected deployment environment or branch and enforce repository approval rules. This could address oidc subject filter trusts unreviewed pull-request branches, but it does not solve the specified datastore uri selects the incorrect storage container failure. The matching remediation is: Update the datastore or data asset binding to the governed storage path with an explicitly pinned version and validated read access.
Question 398
During a retrieval or model-customization performance review, the following condition occurs: A fine-tuned model endpoint cannot be recreated during disaster recovery because the training checkpoint and tokenizer artifacts were deleted after deployment. The change must keep citations, privacy and previously approved behavior intact. What should the engineer examine first to confirm the specific AI-300 workload issue?
- Inspect before-and-after safety evaluations, fine-tune dataset sources, refusal behavior, deployment policy and model version lineage.
- Check document effective dates, index filters, scoring profiles, vector/keyword rankings and available canonical document metadata.
- Inspect registered fine-tuned model version, retained checkpoints, base model lineage, tokenizer files, serving configuration and retention policy.
- Examine synthetic-generation input provenance, PII detection scans, privacy transformations, output similarity to real records and review approvals.
Explanation
Correct Answer
C:Inspect registered fine-tuned model version, retained checkpoints, base model lineage, tokenizer files, serving configuration and retention policy. This is the most relevant evidence for fine-tune production endpoint references deleted training artifact. Custom model lifecycle management includes training lineage and artifact retention; an online endpoint alone is not a durable source of the full fine-tuned model package. The matching controlled remediation is: Retain governed immutable fine-tune artifacts and record deployment lineage with tested restore/rollback procedures. This matters here because a fine-tuned model endpoint cannot be recreated during disaster recovery because the training checkpoint and….
Incorrect Answers
A:Inspect before-and-after safety evaluations, fine-tune dataset sources, refusal behavior, deployment policy and model version lineage. This would investigate fine-tuned model loses safety boundary after customization rather than the documented fine-tune production endpoint references deleted training artifact issue. The relevant investigation is: Inspect registered fine-tuned model version, retained checkpoints, base model lineage, tokenizer files, serving configuration and retention policy.
B:Check document effective dates, index filters, scoring profiles, vector/keyword rankings and available canonical document metadata. This would investigate hybrid retrieval double-counts outdated documents rather than the documented fine-tune production endpoint references deleted training artifact issue. The relevant investigation is: Inspect registered fine-tuned model version, retained checkpoints, base model lineage, tokenizer files, serving configuration and retention policy.
D:Examine synthetic-generation input provenance, PII detection scans, privacy transformations, output similarity to real records and review approvals. This would investigate synthetic training examples copy private customer identifiers rather than the documented fine-tune production endpoint references deleted training artifact issue. The relevant investigation is: Inspect registered fine-tuned model version, retained checkpoints, base model lineage, tokenizer files, serving configuration and retention policy.
Question 399
During a Foundry generative AI quality and observability incident, the following condition occurs: A production agent serves thousands of requests but its evaluation monitor collects only successful English FAQ interactions because failed sessions and other languages were excluded. The fix must preserve evaluation validity and avoid unnecessary user-data collection. Which acceptance test shows the AI operations defect is corrected?
- The responsible stage is identified and P95 user response time improves without gratuitous changes to healthy components.
- Average tokens per successful request falls while groundedness and task success remain within accepted limits.
- The monitoring dataset reflects significant live workflows and reveals failures in the previously omitted segments.
- An adversarial document cannot cause unapproved transactions while authorized research questions still succeed.
Explanation
Correct Answer
C:The monitoring dataset reflects significant live workflows and reveals failures in the previously omitted segments. Production GenAI quality monitoring is biased when sampling systematically excludes difficult or unsuccessful interactions. a direct corrective action is to apply privacy-conscious representative sampling or stratified monitoring that includes error and underrepresented user cohorts.
Incorrect Answers
A:The responsible stage is identified and P95 user response time improves without gratuitous changes to healthy components. That addresses a different configuration issue rather than the main requirement. Verify instead: The monitoring dataset reflects significant live workflows and reveals failures in the previously omitted segments.
B:Average tokens per successful request falls while groundedness and task success remain within accepted limits. That addresses a different configuration issue rather than the main requirement. Verify instead: The monitoring dataset reflects significant live workflows and reveals failures in the previously omitted segments.
D:An adversarial document cannot cause unapproved transactions while authorized research questions still succeed. That addresses a different configuration issue rather than the main requirement. Verify instead: The monitoring dataset reflects significant live workflows and reveals failures in the previously omitted segments.
Question 400
As an MLOps engineer reviews a model training or inference pipeline, the following condition occurs: A tuning experiment requests dozens of concurrent GPU trials with no bound, leaving the Azure ML workspace queued for hours under regional quota constraints. The resolution must preserve quality gates, documented artifacts and rollback options. Which investigation best verifies the cause before changing production configuration?
- Inspect model input data quality signals, null fractions, expected feature schema, training baseline and monitoring sampling.
- Inspect run metric definitions, test cohort composition, split timestamps, class prevalence and the comparison dashboard filter.
- Inspect sweep max_concurrent_trials, compute cluster maximum nodes, GPU family quota and job scheduling telemetry.
- Inspect notebook input connection, extraction timestamp, data asset versions, query filter and persisted run metadata.
Explanation
Correct Answer
C:Inspect sweep max_concurrent_trials, compute cluster maximum nodes, GPU family quota and job scheduling telemetry. This is the most relevant evidence for sweep concurrency overwhelms scarce gpu quota. Hyperparameter tuning parallelism and cloud compute quota must be planned together; more requested trials do not create physical capacity. The matching controlled remediation is: Set justified trial concurrency and sampling/early-termination limits so the sweep fits available GPU capacity.
Incorrect Answers
A:Inspect model input data quality signals, null fractions, expected feature schema, training baseline and monitoring sampling. This would investigate missing feature values escape input drift checks rather than the documented sweep concurrency overwhelms scarce gpu quota issue. The relevant investigation is: Inspect sweep max_concurrent_trials, compute cluster maximum nodes, GPU family quota and job scheduling telemetry.
B:Inspect run metric definitions, test cohort composition, split timestamps, class prevalence and the comparison dashboard filter. This would investigate run comparison uses incompatible validation populations rather than the documented sweep concurrency overwhelms scarce gpu quota issue. The relevant investigation is: Inspect sweep max_concurrent_trials, compute cluster maximum nodes, GPU family quota and job scheduling telemetry.
D:Inspect notebook input connection, extraction timestamp, data asset versions, query filter and persisted run metadata. This would investigate exploration notebook reads production data without reproducible snapshot rather than the documented sweep concurrency overwhelms scarce gpu quota issue. The relevant investigation is: Inspect sweep max_concurrent_trials, compute cluster maximum nodes, GPU family quota and job scheduling telemetry.