CCNA Data for AI Questions

Option A is correct because Data Check in Salesforce monitors data freshness by tracking when records were last updated, ensuring that AI models use current data. Stale data can degrade model accuracy, so this practice directly supports data quality for AI.

Option B is correct because low confidence scores in Einstein Prediction Builder often stem from data quality issues such as missing values or outliers. These anomalies distort the model's ability to learn meaningful patterns, leading to uncertain predictions. Clean, complete data is essential for the model to produce high-confidence scores.

Oversampling underrepresented segments in the training data directly addresses the class imbalance that causes the model to favor high-revenue opportunities. By increasing the frequency of low-revenue examples, the model learns to treat all segments more equally, reducing bias in its recommendations. This is a standard data-level technique for mitigating bias in AI models.

Option D is correct because reconciliation rules in Salesforce Data Cloud define how records from different data sources are matched and merged into a unified profile. If a reconciliation rule is not configured for a data source, records from that source may not be properly linked to existing profiles, leading to missing records in the unified view. This is a common configuration step that must be completed after connecting a data stream.

The filter excludes all opportunities that are not 'Closed Won'. The model should be trained on both won and lost opportunities to predict close probability. The filter should be removed or include all stages.

Knowledge articles with a published status are the correct data source because they contain curated, approved, and structured information that Einstein Bot can reliably use to generate accurate responses. The bot leverages natural language processing to match customer questions against these articles, ensuring answers are based on verified content rather than unstructured or transient data.

Option C is correct because the error explicitly states "value not found in picklist values" for CustomLeadField__c. This indicates a picklist value mismatch. Insufficient permissions (A) would generate a different error; data type mismatch (B) would show conversion error; connection timeout (D) would show timeout.

Option B is correct because training a chatbot on varied phrasing (e.g., synonyms, different sentence structures) improves its ability to understand and generate natural language responses. This practice enhances the model's robustness and generalization, preventing overfitting to a narrow set of expressions and ensuring it can handle the diverse ways customers phrase their queries.

Option B is correct because missing values in the Conversions column directly impact the supervised learning target variable. If the label (conversion) is missing for a training instance, the model cannot learn the correct mapping from features to outcome, leading to biased or incomplete training. This is a critical data quality issue that must be addressed before training, typically via imputation or row removal.

Concept drift occurs when the statistical properties of the target variable change over time, causing the model's predictions to become less accurate even though the data schema remains unchanged. In Einstein Discovery, models are trained on historical data, and if the underlying patterns of customer churn evolve (e.g., due to market shifts or new competitor behavior), the model's learned relationships become stale. Since the data schema is confirmed unchanged, concept drift is the most likely cause of the accuracy drop.

Completeness (no missing values) and accuracy (correct values) are fundamental to model performance.

A is correct because a Data Stream object definition is required to specify the schema and fields for the data being ingested from Salesforce into Data Cloud. Without this definition, Data Cloud cannot interpret the structure of the incoming records, making it impossible to map or transform the data.

Einstein Forecasting can detect seasonality if the data contains enough history and a seasonality marker. Adding a 'quarter' feature explicitly helps the model capture recurring patterns.

Option B is correct because a Data Transform recipe can handle malformed rows by stripping extra commas or parsing with a delimiter that accommodates quoted fields. Manual editing is inefficient; rejecting the whole file loses data; increasing timeout does not fix parsing.

The SOQL query output shows '10 records returned' with no error or partial result indicator, confirming that the query completed successfully and returned exactly 10 records. In Salesforce SOQL, the query result includes a 'totalSize' field that reflects the total number of records matching the query criteria, and here it matches the number of records displayed, indicating a complete and successful retrieval.

Salesforce Data Cloud is designed to unify data from multiple sources into a single platform for AI and analytics. Exporting to a data lake adds complexity, using only Salesforce objects limits data scope, and storing flat files lacks governance.

Option C is correct because cyclic features using sine and cosine transformations preserve the circular nature of temporal data (e.g., month 12 and month 1 are adjacent, not far apart). This allows a model to learn both long-term trends (via the year component) and seasonal patterns (via the cyclic encoding of month and day) without imposing a false linear ordering. In contrast, simple numeric extraction treats time as linear, which can misrepresent seasonal cycles.

The error 'Field Amount cannot be null' indicates that the target field in the predictive model is configured to require a non-null value. When the data flow attempts to write records with null Amount values into that field, the transform fails. This is a common schema constraint mismatch where the source data contains nulls that violate the target field's nullability requirement.

Option B is correct because imputing missing values using the mode (most frequent value) of the 'PreferredChannel' field is a standard data preprocessing technique that preserves the dataset size and statistical distribution. In Einstein Next Best Action, missing categorical data can degrade model personalization, and mode imputation is a simple, effective way to handle this without losing records or altering the model structure.

Option B is correct because outliers can disproportionately influence model training, especially in algorithms like linear regression or k-means clustering, leading to biased predictions. Evaluating the presence and impact of outliers is critical for ensuring the model generalizes well to unseen data.

The error about data quality in Einstein Vision typically occurs when the dataset has only one label per category. For binary classification (defective vs. non-defective), each category must contain at least two distinct labels to allow the model to learn meaningful patterns. With only one label per category, the model cannot differentiate between variations within a class, leading to a data quality error.

Options B and D are correct. Item metadata (B) and user-item interactions (D) are essential for recommendation models. User profile data (A) is optional; external product prices (C) are not required; sales reports (E) are not a standard input.

Active learning iteratively selects the most informative unlabeled data points for labeling, typically those with low prediction confidence from a preliminary model. This minimizes labeling effort while maximizing model performance, which is the core principle of active learning.

Einstein Segment Creation works with Data Cloud unified profiles.

The error shown in the exhibit is a division-by-zero runtime error, which occurs when a formula in a data transform attempts to divide a value by a field that contains zero. In Pega, data transforms execute field-level calculations, and if a divisor field holds a zero, the system throws a 'Divide by zero' exception. Option D correctly identifies this as the most likely cause because the error message explicitly indicates a division operation failed due to a zero divisor.

Option D is correct because it addresses both the missing data (impute using region-specific averages to preserve regional patterns) and the class imbalance (stratified sampling ensures balanced representation across regions during training). Option A removes Region, losing valuable information; Option B uses synthetic data which may introduce artificial patterns; Option C only rebalances but does not fix missing data which could still bias the model.

Missing values in critical fields (Option A) are a common data quality issue because many AI models, particularly those relying on statistical or gradient-based optimization, cannot handle null or NaN inputs without imputation or removal. If missing values are not addressed, the model may learn biased patterns or fail to converge, leading to degraded predictive performance.

Option C is correct because Einstein Discovery natively supports text fields as categorical predictors, automatically encoding them for model training. The platform handles string values like 'Active', 'Inactive', and 'Churned' without requiring manual transformation, preserving the semantic meaning and cardinality of the data.

Option D is correct because the data ingestion step is responsible for bringing raw data into the pipeline, including format conversions like CSV to Parquet. Converting to Parquet at ingestion improves storage efficiency and query performance for downstream processing, as Parquet uses columnar storage and compression.

Option A is correct because Einstein Next Best Action (NBA) requires historical interaction data showing which actions were offered and whether they were accepted to train the predictive model. This feedback loop enables the AI to learn which actions are most effective for specific customer contexts, directly improving recommendation accuracy.

Option C is correct because Einstein Article Recommendations rely on user interaction data, specifically article view events, to generate personalized recommendations. If these events are not being captured, the model has no input to learn from, and recommendations will not appear. Checking event capture is a fundamental first step in troubleshooting data pipeline issues.

Option A is correct because Einstein Engagement Scoring models have a maximum scoring capacity (e.g., 2 million scored records per model). When new donors are added but the model stops generating scores, the most likely cause is that the model has reached this capacity and requires retraining to incorporate new records. Retraining resets the scoring queue and allows the model to score newly added donors.

Option A is correct because Salesforce Data Cloud can ingest third-party demographic data from external sources (e.g., data enrichment providers) to enrich customer profiles. This data, when combined with first-party data, enables AI models to generate more accurate predictions and segmentations. Data Cloud’s Data Streams and Data Lake objects support structured ingestion of such external datasets.

Completeness, timeliness, and consistency are fundamental data quality dimensions. Volume is not a quality dimension; uniqueness is related to consistency but not always required.

Data preprocessing is essential for AI models because raw historical sales data often contains missing values, inconsistent formats, and noise. Cleaning (e.g., handling nulls in 'Amount') and transforming (e.g., encoding 'Lead_Source' into numerical features) ensure the model can learn patterns effectively, directly impacting training accuracy and convergence.

Option D is correct because a schema mismatch between source and target is the most common cause of pipeline failures in data integration workflows. When the source data structure (e.g., column names, data types, or nested fields) does not match the target schema, the pipeline cannot map or transform the data correctly, leading to errors during ingestion or transformation stages. This is especially relevant in tools like Apache NiFi, AWS Glue, or Azure Data Factory, where schema validation is enforced at runtime.

Options A and D are correct. Consent management (A) ensures legal basis; data masking of PII (D) protects sensitive data. Data compression (B) and color coding (C) are not privacy measures; indexing speed (E) is performance related.

With extreme imbalance, oversampling the minority class (e.g., SMOTE) generates synthetic fraud examples, helping the model learn fraud patterns and improve recall without discarding legitimate data.

Einstein Prediction Builder requires historical data with known outcomes to train a supervised machine learning model. Historical case records containing actual resolution times provide the labeled examples needed for the model to learn patterns and predict future case resolution times. Without this ground truth data, the model cannot be trained to make accurate predictions.

Option C is correct because high cardinality (many unique values) can hurt model performance. Frequency encoding or binning reduces cardinality while retaining information. Removing the field or converting to numeric may lose information; increasing model complexity is not recommended.

Model-based imputation (Option B) is best because it uses relationships between features (e.g., education, job role) to predict missing 'annual income' values, preserving data distribution and minimizing bias. This approach avoids the distortion caused by simple mean/zero imputation and retains sample size better than deletion.

The OutOfMemoryError indicates that the Java Virtual Machine (JVM) heap space is exhausted while processing large CSV files. Increasing the heap memory (e.g., using -Xmx flag) allocates more memory to the application, allowing it to handle larger datasets without crashing. This directly addresses the root cause of insufficient memory for the data pipeline's processing workload.

Option D is correct because grouping regions into broader categories like 'Americas', 'EMEA', and 'APAC' reduces high cardinality and sparsity in categorical features, which improves model stability and prevents overfitting in Einstein Prediction Builder. This approach ensures each region group has sufficient training data to learn meaningful patterns, enabling the model to generalize better across all regions without introducing bias from rare categories.

Using diverse human labelers with clear guidelines ensures label consistency and reduces bias. Automated keyword matching is error-prone, a single expert may introduce personal bias, and using only positive labels would create an unbalanced dataset.

Option C is correct because imputing missing values using mean or median is a standard practice that preserves the dataset size and statistical properties, allowing the AI model to learn from all available features without introducing bias from data removal. This approach is particularly effective for numerical features in customer churn prediction, where missing values are often random and imputation maintains the distribution for algorithms like logistic regression or gradient boosting.

In Salesforce CRM Analytics, a dataset is the foundational data structure that transforms raw data into an optimized, columnar format for analytics and AI features like Einstein Discovery. It is created by extracting, cleaning, and aggregating data from sources such as Salesforce objects or external connectors, enabling efficient querying, dashboarding, and machine learning model training. This makes option A correct because the primary purpose is to prepare data specifically for AI and analytics workloads.

Option B is correct because deleting rows with missing values is a straightforward technique to handle missing data, especially when the missingness is random and the dataset is large enough that removing a few rows does not significantly impact model performance. This approach avoids introducing bias from imputation methods but can lead to loss of valuable information if too many rows are removed.

Option A is correct because multi-select picklists are not supported as predictors in Einstein Discovery. Numeric, picklist, and date fields are supported.

Imputing missing purchase data with a sensible default (e.g., average purchase frequency) gives the model signal for new customers, improving recommendations without discarding data.

Option A is correct because 'data_scientist' is in allowedUsers, so they are allowed. Option B is not in policy, C the policy filters amounts >0 and <10000, so 5000 is included, D the fields are in the policy, so they should be accessible.

Option B is correct because duplicate records can cause data leakage by allowing the model to see the same or highly similar data in both training and validation splits, leading to overfitting and inflated performance metrics. Removing duplicates ensures that the model generalizes to unseen data rather than memorizing repeated instances.

In-memory data stores (e.g., Redis, Memcached) store data in RAM rather than on disk, providing sub-millisecond read/write latencies essential for real-time AI applications that need immediate access to customer interaction data. This eliminates disk I/O bottlenecks and enables high-throughput, low-latency data retrieval for time-sensitive inference or decision-making.

Einstein Discovery requires a date or timestamp field to perform time series analysis, which is essential for identifying trends, seasonality, and patterns in historical sales data. Without this field, the model cannot properly order observations or forecast future values based on temporal dependencies.

Option B is correct because excluding rows with missing Stage (a picklist that may correlate with outcome) can introduce selection bias. Filling with median (A) or default (C) are common imputation methods; ignoring Description (D) is generally safe as it treats missing as information.

Accuracy of values (Option B) is a fundamental dimension of data quality because AI models learn patterns from training data; if the data contains incorrect values, the model will learn and propagate those errors, leading to unreliable predictions. For example, in a dataset of customer ages, a single erroneous entry of '200' can skew the model's understanding of age distributions, directly impacting model performance.

The HAVING clause references alias TotalAmount, but SOQL does not allow aliases in HAVING; the aggregated expression must be repeated.

Option B is correct because Einstein Next Best Action requires real-time or near-real-time data to personalize recommendations based on recent customer behavior. Streaming data from Data Cloud captures website interactions as they happen, enabling the recommendation engine to use the most current signals (e.g., page views, clicks) to adjust offers dynamically.

Data augmentation techniques like back-translation generate synthetic French samples, effectively increasing the minority language's representation and helping the model learn better.

Option B is correct because multicollinearity occurs when two or more features are highly correlated, which can destabilize model coefficients and reduce interpretability. In Salesforce's predictive models, such as those built with Einstein Discovery, correlated features can inflate variance and lead to unreliable predictions. Avoiding multicollinearity ensures that the model's feature importance estimates are trustworthy and that the model generalizes well to new data.

Normalizing text by correcting common typos and expanding slang reduces vocabulary sparsity and helps the model learn consistent word associations, improving intent recognition.