Salesforce Agentforce Sales Consultant Practice Test | Free 150+ Questions

Salesforce Agentforce Sales Consultant Practice Test

Salesforce Agentforce Sales Consultant preparation is about learning how to turn sales requirements into a scalable, maintainable solution—not simply memorizing feature names. Students can Explore practice tests for leading certifications and use this guide to study the current Salesforce blueprint, understand the full sales lifecycle, practise consulting decisions, strengthen data knowledge, and review responsible AI use in clear, manageable sections.

What Is Salesforce Agentforce Sales Consultant?

Salesforce Certified Agentforce Sales Consultant is the current name of the credential previously known as Salesforce Certified Sales Cloud Consultant. Salesforce describes certified professionals as consultants who can design and implement sustainable, scalable Sales Cloud solutions that support long-term customer success.

The live Trailhead credential page lists Salesforce Certified Platform Administrator as the prerequisite. That requirement makes sense because this consultant-level certification assumes candidates already understand core platform concepts such as objects, fields, users, security, automation, reports, dashboards, and data administration.

The current certification code is Sales-Con-201. Older learning resources may still use the Sales Cloud Consultant name, but students should compare every resource with the live Salesforce guide. The present outline includes five domains, including a dedicated Predictive and Generative AI section.

This is not a general AI credential. Agentforce and Sales Cloud AI are part of the coverage, but most of the blueprint still tests sales-process design, implementation strategy, security, products, pricing, data, adoption, reporting, and consultant judgment. A balanced study plan needs all five areas.

Salesforce’s candidate description points to people with practical Salesforce and sales-process experience. Suitable learners may work as Salesforce consultants, administrators, business analysts, sales operations specialists, CRM implementation professionals, or solution designers.

Current Official Topics and Percentages

The current Salesforce certification guide lists five weighted domains.

These percentages total 100%. Consulting and Implementation Strategies is the largest domain at 25%, closely followed by Practical Application of Agentforce Sales Expertise at 24%. Together, they represent nearly half of the outline. However, the sales lifecycle, data, and AI domains frequently connect with implementation scenarios, so students should not study them as isolated subjects.

The following sections preserve Salesforce’s current topic names and translate the published objectives into easy, student-friendly explanations.

1. Sales Lifecycle — 20%

The Sales Lifecycle domain tests whether a consultant can understand a sales organization’s goals and recommend suitable Agentforce Sales and Sales Cloud capabilities. It covers business requirements, metrics, sales and marketing processes, related sales products, forecasts, AI, reports, and dashboards.

Connect requirements with the right solution

A consultant should begin with the business problem. A sales manager might want to increase lead-conversion speed, improve forecast accuracy, reduce stalled opportunities, or provide better visibility into seller activity. Each goal requires a different combination of process, data, automation, reporting, and user experience.

Before selecting a feature, ask:

• What outcome does the organization want?
• Which users are involved?
• What information do they need?
• Where does the process begin and end?
• Which metric will show improvement?
• Are there security, integration, or adoption constraints?

The strongest recommendation solves the stated need without unnecessary complexity.

Understand common sales and marketing processes

Students should follow the relationship between campaigns, leads, accounts, contacts, opportunities, products, quotes, and closed business. A typical process may begin with marketing outreach, continue through lead qualification and conversion, and then move into opportunity management, product selection, quoting, negotiation, and closure.

Not every company uses the same process. Some organizations sell directly, others use partners, and some manage long or highly regulated sales cycles. The consultant must understand the customer’s terminology and translate it into a Salesforce design.

Important implementation questions include:

• What makes a lead qualified?
• When should a lead be converted?
• Which information must transfer during conversion?
• How are opportunity stages defined?
• What activities are required at each stage?
• Which products and prices can each team sell?
• How are pipeline and revenue forecasts calculated?
• Which marketing interactions should be visible to sales users?

Know when to use related sales capabilities

The official objective names several products and features. Students should understand their business purpose rather than memorizing marketing descriptions.

Sales Engagement can help sales teams organize structured outreach and seller activity. It may support repeatable prospecting work where representatives need guided steps and productivity tools.

Salesforce Inbox and email integrations can bring Salesforce context into a seller’s email workflow and reduce manual activity. The consultant should consider user experience, supported features, access, data capture, and organizational policies.

Enterprise Territory Management helps assign accounts and sales responsibility through a territory structure. It is useful when sales coverage depends on geography, product line, industry, market segment, or another business rule rather than only the role hierarchy.

Opportunity Forecasting gives sales teams a structured view of expected revenue or quantities. Students should understand forecast categories, hierarchy, periods, adjustments, and the need for accurate opportunity data.

Agentforce Sales Einstein and related predictive or generative tools can support prioritization, insight, planning, prospecting, and seller productivity. AI recommendations are only useful when the underlying data and business process are trustworthy.

Turn outcomes and KPIs into reports and dashboards

The outline expects candidates to connect business outcomes and sales key performance indicators with analytics. A report should answer a real management question rather than display every available field.

Useful sales measures may include lead response time, conversion rate, pipeline coverage, opportunity age, stage movement, average deal size, win rate, sales-cycle length, forecast accuracy, activity levels, and closed revenue.

Students should understand the difference between:

• An activity metric, such as calls completed
• A process metric, such as lead-to-opportunity conversion
• An outcome metric, such as closed revenue or win rate

Dashboards should use clear source reports, relevant filters, appropriate groupings, and a consistent definition of each KPI. If business users disagree about what a metric means, the consultant must resolve that definition before building the dashboard.

2. Consulting and Implementation Strategies — 25%

This domain covers work before, during, and after a Sales Cloud implementation. It includes discovery, requirements, user experience, communication, training, change management, deployment, project lifecycle, adoption, access, and continuous improvement.

Prepare users and the organization before implementation

Successful CRM projects change how people work. Before configuration begins, the consultant should understand the current process, user difficulties, communication needs, training approach, change impact, and expected success measures.

Students should be able to identify key stakeholders, including executive sponsors, sales leaders, sales operations, marketing, representatives, administrators, security teams, integration owners, and support staff. Each group may have different goals and concerns.

A useful preparation framework includes:

1. Define the business outcomes.
2. Identify affected users and processes.
3. Document current pain points.
4. Agree on scope and priorities.
5. Plan communication and training.
6. Establish measurable adoption and business targets.

Conduct discovery workshops

Discovery workshops help consultants understand the business before designing the solution. The goal is not merely to collect a wish list. The consultant should explore the current process, exceptions, data, users, integrations, reporting, security, and future goals.

Good discovery questions are open enough to reveal how work happens. For example: “What prevents a representative from moving an opportunity forward?” is often more useful than “Do you want a new opportunity field?”

After gathering information, the consultant should convert needs into clear requirements or user stories, identify dependencies, and prioritize use cases by business value, risk, urgency, and effort.

Use the project management lifecycle

The project lifecycle usually includes initiation, planning, design, build, testing, deployment, training, launch, and improvement. The exact delivery method can vary, but students should understand how scope, schedule, quality, risk, resources, and stakeholder decisions affect each stage.

Agile approaches can support iterative delivery and feedback when requirements evolve. A more sequential approach may suit tightly defined work with fixed dependencies. The choice should reflect the customer’s needs rather than a preference for one label.

Consultants should also maintain decision logs, risk registers, requirements traceability, test plans, release plans, and acceptance criteria appropriate to the project.

Apply deployment considerations

A deployment moves approved configuration from a development or test environment into production. Students should consider environment strategy, dependencies, test coverage, data requirements, deployment sequence, validation, user communication, and rollback or recovery planning.

A technically successful deployment can still disrupt sellers if it arrives without training, accurate data, or clear support. Plan the technical release together with the business rollout.

Useful questions include:

• Which components and dependencies must move together?
• Which users will validate the release?
• Is data preparation required before or after deployment?
• How will existing automation behave?
• When should the release occur?
• What is the response plan if a serious problem appears?

Respond to low adoption after launch

Low adoption is a signal, not a complete diagnosis. Users may avoid Salesforce because the process is slow, data is unreliable, access is missing, training was unclear, or the system does not match the way they sell.

The consultant should use evidence such as login trends, record creation, activity capture, stage completeness, support requests, user interviews, and business results. The answer may involve process improvement, configuration, coaching, simplified pages, better automation, clearer ownership, or improved data.

Plan continuous improvement

Sales processes, teams, products, and goals change. A sustainable implementation includes governance for new requirements, access changes, releases, data quality, feedback, and platform maintenance.

Continuous improvement should be prioritized by measurable value. It should not become a stream of unrelated requests that gradually makes the solution harder to use and maintain.

3. Practical Application of Agentforce Sales Expertise — 24%

This domain asks students to apply Salesforce knowledge to end-to-end sales requirements. It includes lead-to-close design, security, products and pricing, campaigns, productivity tools, and decisions about standard, custom, or third-party solutions.

Build an end-to-end lead-to-close process

The official objective follows the journey from Lead to Opportunity to Quote to Close. Students should understand what each stage represents and how information moves between them.

Lead: A potential person or organization that has not yet been fully qualified. Qualification criteria should reflect the customer’s sales process.

Lead conversion: The point at which qualified information becomes the appropriate account, contact, and opportunity records. The design should preserve useful data and avoid duplicates.

Opportunity: A qualified sales deal. Stages, close dates, amounts, products, contact roles, competitors, activities, and next steps help teams manage progress.

Quote: A proposed combination of products, quantities, and prices for the customer. Quotes should align with the opportunity and the organization’s approval or pricing process.

Close: The sales result is recorded, related processes are completed, and reporting reflects the outcome accurately.

Students should also think about exceptions. A company may create opportunities without leads, use several sales processes, require approvals, sell through partners, or connect Salesforce with an external quoting system.

Support Campaigns, Leads, and Opportunities

Campaigns help organize marketing initiatives and associate people with marketing activity. Leads support early qualification, while opportunities represent active sales deals.

The consultant should decide how campaign responses reach sales, how qualified leads are assigned, which fields are required, how duplicates are handled, and how opportunities move through the chosen sales process.

Scenario practice should focus on business rules. For example, lead assignment should reflect ownership requirements; opportunity stages should match real milestones; and campaign influence or reporting should use consistent data.

Design the security model

The official outline calls out sharing rules, role hierarchy, Account Teams, Opportunity Teams, permission sets, and permission set groups.

These tools solve different access needs:

• Role hierarchy can provide upward visibility according to management structure.
• Sharing rules can extend record access to defined users or groups.
• Account Teams support collaboration around accounts with team roles and access.
• Opportunity Teams support collaboration on deals.
• Permission sets grant selected object, field, system, or feature permissions.
• Permission set groups combine permissions for a job function.

A good design starts with organization-wide defaults and the principle of least privilege. It then opens access only where the business requires it. Object access does not automatically create record access, and record access does not automatically provide field access.

Configure products, price books, opportunity products, and quotes

A Product represents something the organization sells. A Price Book is a collection of products and their prices. A Price Book Entry connects a product with a particular price book and price. An Opportunity Product represents a product added to a specific opportunity.

Students should understand standard and custom price books, product availability, quantity, sales price, list price, schedules where relevant, quotes, and approvals. Different regions, channels, or customer types may require different prices or product selections.

The Salesforce product and price-book documentation explains that price books organize products with associated list prices for specific uses.

Consider multi-currency

Multi-currency supports organizations that sell in more than one currency. The consultant should understand corporate currency, active currencies, conversion rates, opportunity currency, product prices, reports, forecasts, and the potential need for dated exchange rates through advanced currency management.

Currency configuration affects existing data and reporting. It should be planned carefully rather than enabled as an experiment in production.

Decide when to extend declarative functionality

Standard configuration and declarative automation should be considered first when they meet the requirement. A gap may justify custom development, a third-party application, another Salesforce product, or a productivity tool such as email integration, Slack, or Salesforce Mobile.

The decision should consider:

• Business fit
• User experience
• Security and compliance
• Data ownership
• Integration effort
• License and implementation cost
• Performance and scale
• Testing and support
• Upgrade and maintenance responsibility

“Use custom code” is not a complete recommendation. The consultant should explain why standard capabilities are insufficient and how the chosen extension will be governed.

4. Data Management — 18%

Sales processes depend on trusted data. This domain covers migrations, integrations, scalability, and sales data quality.

Plan data migration

A migration moves data from a legacy system, spreadsheet, or another source into Salesforce. Students should understand the full process:

1. Identify source data and owners.
2. Define field and object mappings.
3. Clean and deduplicate records.
4. Decide which data should be migrated.
5. Plan load order and record relationships.
6. Test in a suitable environment.
7. Validate totals, ownership, access, and business rules.
8. Prepare cutover and post-load support.

More data is not always better. Old, incomplete, or unused information can reduce trust and slow adoption. The organization should make an intentional retention decision.

Understand integration considerations

An integration keeps Salesforce connected with systems such as marketing automation, finance, order management, data warehouses, product platforms, or communication tools.

The consultant should identify the system of record, data direction, frequency, volume, latency, security, error handling, and monitoring needs. A real-time integration may be appropriate for an urgent sales process, while a scheduled batch may be simpler and more reliable for periodic updates.

Students should also consider duplicate creation, ownership changes, field mapping, failed transactions, and what users see when connected data is unavailable.

Design for scalability

A solution that works with a few hundred records may struggle at larger volumes. Scalability includes data volume, automation, sharing, reporting, integration load, user growth, and transaction behavior.

Learners should recognize designs that create excessive record processing, repeated updates, slow reports, complicated sharing recalculation, or fragile integrations. The goal is not to memorize every platform limit. It is to understand that architecture choices must fit expected scale.

Maintain sales data quality

Data quality includes accuracy, completeness, consistency, uniqueness, timeliness, and valid ownership. Common controls include required fields, validation rules, standardized values, duplicate rules, matching rules, automated enrichment, stewardship processes, and quality reports.

Avoid making every field required. Too many required inputs can encourage users to enter meaningless values. Capture the information that truly supports selling, reporting, service, integration, or compliance.

Data quality is also an operating responsibility. Assign owners, monitor trends, fix root causes, and train users. A one-time cleanup cannot solve a process that continues producing poor data.

5. Predictive and Generative AI — 13%

The current blueprint explicitly tests generative AI tools available in Agentforce for Sales, predictive AI tools available in Sales Cloud, and ethical challenges addressed through Salesforce’s Trusted AI Principles.

Understand the difference between predictive and generative AI

Predictive AI uses patterns in data to estimate a likely outcome or score. In sales, it may help prioritize leads, assess opportunities, identify risks, or support forecasting.

Generative AI creates new content or responses based on instructions and grounded information. In sales, it may assist with summaries, prospect research, outreach drafts, planning, or conversational support.

The two approaches can work together. A predictive model might identify a high-priority opportunity, while a generative tool helps summarize context or suggest a seller action. The consultant should still validate that the use case, data, permissions, and user review are appropriate.

Study Agentforce for Sales use cases

The official outline asks learners to understand which generative tools are available in Agentforce for Sales. Study supported use cases such as prospecting, account or opportunity research, sales planning, summaries, and coaching as they appear in current Salesforce documentation.

Do not assume an AI agent should make every sales decision. Good use cases are clear, bounded, measurable, grounded in suitable data, and supported by escalation or human review when necessary.

Study predictive Sales Cloud tools

Predictive capabilities can include scoring or insights that help sellers decide where to focus. Students should understand the purpose of lead and opportunity scoring, forecasting support, and other current Einstein capabilities rather than attempting to calculate the underlying model manually.

Prediction quality depends on data quality and relevance. A score may be technically available but unhelpful when historical data is incomplete, biased, too limited, or different from the new sales process.

Apply Trusted AI Principles

The official objective asks candidates to identify ethical challenges and apply Salesforce’s Trusted AI Principles to sales scenarios. Important concerns include fairness, transparency, privacy, accuracy, accountability, security, and human oversight.

When evaluating an AI-supported sales use case, ask:

• Is the business purpose appropriate and clear?
• Is the system using data the organization is authorized to use?
• Could the outcome unfairly disadvantage a group?
• Can users understand what the AI is doing and its limitations?
• Is generated content checked before an important action?
• Are permissions and sensitive fields respected?
• Can the organization monitor results and correct problems?

A responsible solution does not treat AI output as automatically correct. It defines where people review, approve, edit, or override the result.

How Our Practice System Strengthens Sales-Consulting Judgment

A useful Salesforce Agentforce Sales Consultant practice test should reveal whether learners can apply the published topics to realistic business requirements. It should not claim to reproduce live Salesforce questions. Its purpose is to strengthen decision-making, explain concepts, and identify gaps.

When students prepare with our practice approach, they can benefit from:

• Blueprint-aligned practice: Sessions can be organized around all five official domains and current percentages.
• Plain explanations: Review material can show why a solution fits the requirement and why alternatives are less suitable.
• Scenario reasoning: Learners practise identifying outcomes, constraints, users, data, and trade-offs.
• Domain-level progress: Results can show whether the main weakness is lifecycle, implementation, application, data, or AI.
• Timed review: Mixed sessions can help students improve reading pace and concentration.
• Repeatable learning: Later assessments can show whether targeted review improved understanding.

Students following a broader Salesforce path can Explore Salesforce practice tests by certification while keeping each credential connected to its own current official guide.

How to Use Practice Assessments Effectively

Begin with a diagnostic assessment

Take one mixed-domain practice set before intensive study. Record the topic, result, confidence, and reasoning for every difficult item. A correct guess should still be reviewed.

Extract the requirement before selecting a feature

Rewrite the scenario as one short requirement. For example: “Sales managers need visibility by territory,” or “Representatives must use different prices by region.” Then identify the relevant process, data, security, and feature choices.

Compare trade-offs

Consultant scenarios often contain more than one technically possible option. Compare them using business fit, standard capability, maintenance, scale, security, cost, user experience, and long-term ownership.

Maintain an error log

Use four columns:

1. Topic
2. Why the original reasoning failed
3. Correct concept
4. Follow-up activity

The follow-up might be a Trailhead unit, official documentation review, configuration exercise, process diagram, security matrix, or data-mapping task.

Retest with different scenarios

Do not repeat the same questions immediately. Apply the corrected concept, wait until the next review session, and use a different set. This reduces answer memorization.

Six-Week Student-Friendly Study Plan

Week 1: Map the sales lifecycle

• Review the five official domains.
• Trace Campaign to Lead to Account, Contact, Opportunity, Quote, and Close.
• Define common sales KPIs.
• Build a simple pipeline report and dashboard plan.
• Review when Sales Engagement, Inbox, territories, and forecasting may help.

Week 2: Learn discovery and project strategy

• Create stakeholder and user maps.
• Practise discovery questions.
• Turn business needs into prioritized requirements.
• Review change management, communication, training, and success metrics.
• Map the project lifecycle from discovery through continuous improvement.

Week 3: Apply core Sales Cloud design

• Build a fictional lead-to-close process.
• Compare Account Teams and Opportunity Teams.
• Review role hierarchy, sharing rules, permission sets, and permission set groups.
• Map campaigns, lead assignment, conversion, opportunity stages, and approvals.
• Complete a domain-focused practice session.

Week 4: Study products, quotes, and extension choices

• Create products and price-book examples.
• Trace products from the catalog to an opportunity and quote.
• Review multi-currency considerations.
• Compare declarative, custom, third-party, and other Salesforce solutions.
• Review email, Slack, and mobile productivity use cases.

Week 5: Build data-management skill

• Create a migration mapping and load-order plan.
• Identify systems of record in an integration scenario.
• Review volume, latency, error handling, and monitoring.
• Design practical duplicate and validation controls.
• Build a data-quality dashboard outline.

Week 6: Add AI knowledge and integrate all domains

• Compare predictive and generative AI.
• Review current Agentforce for Sales and Einstein use cases.
• Apply Trusted AI Principles to sales scenarios.
• Take mixed, timed assessments.
• Review the error log and revisit only weak concepts.

Practical Activities That Improve Retention

Draw a complete sales process

Create a diagram from marketing campaign through closed business. Add ownership, required data, approvals, products, quotes, reporting, and integrations.

Build a security matrix

List sales representatives, managers, sales operations, finance, marketing, and administrators. Define the minimum objects, fields, records, and capabilities each group needs.

Compare three solution approaches

Choose one requirement, such as guided prospecting or regional pricing. Write a standard Salesforce option, an extended or custom option, and a third-party option. Compare the trade-offs.

Plan a data migration

Use fictional accounts, contacts, leads, opportunities, products, and activities. Decide the load order, external IDs, ownership, deduplication, validation, and reconciliation checks.

Evaluate an AI use case

Select a safe fictional use case, such as summarizing opportunity notes. Document the purpose, data source, access, human review, possible error, monitoring, and success measure.

Diagnose an adoption problem

Imagine that opportunity updates dropped after launch. List evidence to collect before recommending a fix. Separate process, access, data, usability, training, and management causes.

Common Preparation Mistakes

Using only an older Sales Cloud Consultant outline

The current credential includes updated Agentforce naming and a dedicated Predictive and Generative AI domain. Always compare study material with the live Salesforce guide.

Studying only AI because Agentforce is in the name

AI accounts for 13% of the current outline. Sales process, implementation, security, solution application, and data still make up most of the coverage.

Memorizing objects without following the business process

Knowing what an opportunity is does not prove that you can design lead qualification, conversion, products, quotes, approvals, forecasting, and closure.

Ignoring adoption and change management

Sales Cloud success depends on user behavior. Communication, training, coaching, usability, and feedback are part of the consultant role.

Choosing custom code before standard features

Standard and declarative capabilities are often easier to maintain. Custom or third-party options should solve a confirmed gap and have a clear ownership plan.

Treating security tools as interchangeable

Profiles, permission sets, role hierarchy, sharing rules, account teams, and opportunity teams solve different access problems. Identify whether the requirement concerns objects, fields, records, or collaboration.

Ignoring data quality in AI scenarios

Predictive and generative tools rely on appropriate data. Poor, incomplete, or unauthorized data can produce weak or unsafe results.

Repeating practice without learning from errors

Repeated scores are not useful when learners memorize answers. Review the underlying concept and complete a practical follow-up activity.

Readiness Checklist

You are moving toward readiness when you can:

• Name all five official domains and current percentages.
• Trace the sales lifecycle from campaign and lead through quote and close.
• Connect business outcomes with meaningful KPIs, reports, and dashboards.
• Explain the purpose of Sales Engagement, Inbox, territories, forecasting, and sales AI.
• Conduct discovery and prioritize requirements.
• Plan communication, training, change management, and adoption measurement.
• Explain deployment dependencies, validation, and business rollout needs.
• Design a lead-to-close process for more than one sales scenario.
• Select the appropriate security tool for a stated access requirement.
• Explain Products, Price Books, Price Book Entries, Opportunity Products, and Quotes.
• Identify important multi-currency considerations.
• Compare declarative, custom, third-party, and productivity-tool options.
• Plan a migration with mapping, order, quality, and validation steps.
• Explain integration direction, timing, ownership, errors, and monitoring.
• Identify scalability risks in data, automation, sharing, and reporting.
• Distinguish predictive AI from generative AI.
• Apply Trusted AI Principles and human review to a sales use case.
• Review practice mistakes without using copied or confidential content.

Frequently Asked Questions

What does Salesforce Agentforce Sales Consultant cover?

The current blueprint covers Sales Lifecycle, Consulting and Implementation Strategies, Practical Application of Agentforce Sales Expertise, Data Management, and Predictive and Generative AI.

Is this the same credential as Sales Cloud Consultant?

Agentforce Sales Consultant is the current name used by Salesforce for the credential previously called Sales Cloud Consultant. Older resources may use the former name, so learners should verify that the domains and percentages match the live guide.

Which domain has the highest weighting?

Consulting and Implementation Strategies is the largest domain at 25%. Practical Application of Agentforce Sales Expertise follows closely at 24%.

Is Salesforce Platform Administrator required first?

Yes. Salesforce’s current credential page lists Salesforce Certified Platform Administrator as the prerequisite.

Is the certification mainly about Agentforce AI?

No. Predictive and Generative AI represents 13% of the current blueprint. The remaining coverage focuses on sales processes, consulting, implementation, security, core Sales Cloud functionality, and data.

What is the difference between predictive and generative AI?

Predictive AI estimates likely outcomes or scores from data patterns. Generative AI creates new content or responses based on instructions and grounded information. Both require suitable data, access controls, monitoring, and responsible use.

Why are products and price books important?

Products represent what the organization sells. Price books organize available products and prices for a particular use. They support correct product selection and pricing on opportunities and quotes.

Are practice tests enough by themselves?

No. Practice is most useful with the official guide, Trailhead, Salesforce Help, hands-on configuration, and real sales-process knowledge. Mock assessments should identify gaps and strengthen reasoning.

How should students divide their study time?

Use the official weights as a starting point. Give extra time to the 25% implementation domain and 24% practical-application domain, but keep enough time for the lifecycle, data, and AI topics because they connect with larger scenarios.

Where can learners continue preparing?

Begin with the official Salesforce sources below and use independent practice to check understanding. Learners can also Discover certification preparation with Edurely when organizing a wider professional learning plan.