ANC-301 Practice Questions

:

In CRM Analytics, when a CSV file is uploaded and errors occur during the upload process, an error

log is generated. However, only the user who uploaded the external data file can download the error

log, even if other users have administrative permissions. This restriction ensures that only the user

responsible for the data upload can access the details to resolve the issues.

Reference: The limitations and permissions surrounding external data uploads and error logs are

outlined in CRM Analytics permissions documentation.

To determine whether a subscription is new or a renewal from the Opportunity records in Salesforce,

the consultant should utilize a Custom Formula in the data transformation process. Here’s the

rationale:

Custom Formula Usage: By employing a custom formula, the consultant can create a logical

expression that checks the historical data associated with each account. If an account has previous

closed-won opportunities, any new opportunities can be labeled as renewals; otherwise, they are

considered new subscriptions.

Data Insight: This method provides a straightforward way to derive new insights (new vs. renewal)

directly from existing data without altering the data structure itself, making it a non-invasive and

efficient solution.

Implementation: The custom formula can be applied in a recipe or directly within a dataflow in CRM

Analytics, offering flexibility in how and where the transformation is executed.

:

Enhancing accessibility, especially for users with color vision challenges, is critical. Adding up and

down arrows next to the KPIs:

Visual Cues: Provides a non-color dependent method to indicate whether metrics are positive (up

arrow) or negative (down arrow).

Accessibility: Improves understanding for users with color vision deficiencies, ensuring that the

dashboard is inclusive.

User Experience: Enhances the overall usability of the dashboard by making the interpretation of

data straightforward and less reliant on color.

In addressing the requirements of Universal Containers to ensure proper visibility of order data

across different levels of the sales hierarchy, the use of a security predicate based on role hierarchies

is paramount. Here’s why Option B is the ideal approach:

Flatten Operation on Role Hierarchy: This operation is essential as it allows for the creation of a

simplified or "flattened" view of the hierarchical relationships within the organization. This flattened

view enables the dataset to understand and respect the hierarchical structure in security

implementations.

Creating a Multi-value Attribute ('ParentRoleIDs'): By creating this attribute, the recipe can hold

multiple role IDs that a particular user has visibility permissions for. This is crucial in a hierarchical

organization like UC where data visibility needs to cascade down the hierarchy.

Security Predicate: The predicate ('ParentRoleIDs' == "$User.UserRoleld" || 'TeamMember.Id' ==

'$User.Id' || 'Ownerld' == "$User.Id") effectively enforces that:

A user can see all orders where their role matches any of the role IDs in the 'ParentRoleIDs' list

(hierarchical visibility).

A user can see all orders where they are specifically listed as a team member.

A user can see all orders where they are the owner.

This approach aligns with best practices for implementing row-level security in CRM Analytics,

ensuring data visibility is managed correctly according to the defined organizational hierarchy and

individual data ownership.

Upon reviewing the data model and noticing the high correlation alert between 'Store' and daily

sales quantity, the appropriate action is to verify with the client their expectations regarding the

influence of the Store field on daily sales. Here’s the rationale:

Understanding the Role of 'Store' in the Model: Before making any changes to the model, it's crucial

to understand whether the 'Store' field is expected to be a strong predictor based on the business

context. If the client expects that different stores inherently have different sales volumes due to

factors like location, size, or customer base, this correlation may be both meaningful and desired.

Potential Data Leakage: High correlation warnings can sometimes indicate data leakage, where a

predictor (like 'Store') might inadvertently include information about the outcome variable (daily

sales quantity). It's essential to verify whether this correlation makes sense logically or if it's skewing

the model predictions.

Client Consultation: Consulting with the client helps ensure that any modeling decisions align with

their business knowledge and expectations. It’s about validating the model against real-world

expectations and ensuring it remains a useful tool for decision-making.

By taking these steps, the consultant not only adheres to best practices in data science by validating

model inputs and their implications but also ensures that the model aligns with the client’s business

strategies and operational realities.

In CRM Analytics, when dealing with incomplete data, specifically when certain respondents have

not filled out fields like income, the Predict Missing Values transformation in a recipe is highly

effective. This transformation allows you to predict values for missing fields based on patterns from

the existing data. Since the consultant finds this field informative despite having data from only 1% of

respondents, applying this transformation can estimate these missing values, which ensures that the

dataset remains useful for predictive purposes without discarding important variables.

Reference: CRM Analytics Recipes and Predict Missing Values

For uploading target data that changes on a monthly basis and includes historical data (previous

years’ targets), the appropriate operation is "Overwrite." This ensures that each time the CSV file is

uploaded, the existing data in the dataset is replaced with the new data. This is critical because the

target data includes both current and historical data, and using "Overwrite" will update the entire

dataset while maintaining historical accuracy.

"Append" would add new data without replacing the old records, leading to duplication, and

"Update" is not suitable for completely replacing data in this context.

Reference: The usage of the "Overwrite" operation for updating datasets with changing data is

covered in the Analytics External Data API documentation, as well as in the Wave Analytics Explorer

module.

To address issues with unauthorized access to sensitive data and dashboards, the best practice is to

create separate apps, datasets, and dashboards for different user groups and then manage their

sharing settings appropriately. This allows you to maintain data security while ensuring that users

only access the data and insights that are relevant to their roles. In this scenario, applying separate

apps for managers with defined sharing rules will prevent users who shouldn’t have access from

seeing sensitive data.

Reference: Managing Data Access and Sharing in CRM Analytics