Salesforce Certified Agentforce Service Consultant free question 2 / 10 · Domain 2: Implementation Strategies
You are moving articles from Classic Knowledge to Lightning Knowledge with the Lightning Knowledge Migration Tool. In a pre-migration check you find articles still in Scheduled for Publish and Scheduled for Archive status whose scheduled dates have passed. Which handling matches the Help description?
- They migrate with the scheduled status, so correcting the scheduled dates after migration makes the schedules work again
- The migration tool runs the overdue publish and archive schedules at the start and then migrates the articles
- The scheduled status is returned to draft in migration, so publish the articles again afterward
- Scheduled articles are removed during the migration, so complete the publishing and archiving before you start
Show the answer and explanation
Answer: D
Why this is correct
In the table of limitations in the Help description of the migration tool, for Article Status, articles in Scheduled for Publish status whose date has passed and articles in Scheduled for Archive status whose date has passed are removed during the migration. So the Help topic asks you to publish the articles scheduled for publishing and archive the ones scheduled for archiving before starting. The migration tool has no mechanism that runs the schedules for you.
Why the other options are wrong
"The migration tool runs the overdue publish and archive schedules at the start and then migrates the articles" … The Help topic does not describe the migration tool running schedules. Overdue scheduled articles are among those removed, so a person completes the publishing and archiving before the migration.
"They migrate with the scheduled status, so correcting the scheduled dates after migration makes the schedules work again" … Overdue scheduled articles do not migrate with the scheduled status. They are removed during the migration, so nothing is left to correct the dates on afterward.
"The scheduled status is returned to draft in migration, so publish the articles again afterward" … There is no handling that returns them to draft and migrates them. They are removed, so they do not remain as drafts either. Publish any article you want to keep published before the migration.
Checking what does not migrate
The table of limitations also lists other things that do not migrate: soft-deleted records, unreleased article types, approval process history, and the automatic feed posts that show article changes. Before the migration, check one by one whether anything you want to keep falls under this table.