Cloud kicks intends to protect with backups by using the data by using the data export Service. Which two considerations should the administrator remember when Scheduling the export? Choose 2 Answers.

Question

Options

• AMetadata Backups are limited a sandbox refresh intervals.
• BData Backups are limited to weekly or monthly intervals.
• CData export service should be run from a sandbox.
• DMetadata backups must be run via a separate process.

• A
  88% (21)
• C
  8% (2)
• D
  4% (1)

Explanation

Salesforce's Data Export Service is a data-only tool, and both scheduling constraints in options A and B reflect real limitations administrators must plan around.

Why A and B are correct: The Data Export Service only exports record data - it cannot export metadata (configurations, custom objects, fields, etc.). Since metadata protection relies on sandbox refreshes, administrators are bound by sandbox refresh intervals for that layer of backup (A). For data itself, the service enforces a scheduling ceiling of weekly or monthly, meaning you cannot automate daily exports - a critical planning constraint when setting recovery point objectives (B).

Why C is wrong: The Data Export Service should always be run from your Production org, not a sandbox. Running it from a sandbox only captures sandbox data, which defeats the purpose of protecting real business data.

Why D is wrong: While metadata does require separate tooling (Metadata API, change sets, sandbox refresh), this isn't framed correctly as a scheduling consideration for the export service - the question focuses on what administrators must remember when scheduling, and D conflates a general architectural fact with a scheduling constraint, making it a distractor.

Memory tip: Think "W/M for Data, Sandbox for Metadata" - Data = Weekly/Monthly scheduling limit; Metadata = tied to Sandbox refresh cadence. Two separate clocks, two separate tools.

No community discussion yet for this question.