Which two tasks are essential when planning a dev/prod XSOAR deployment? (Choose two)

Question

Options

• AAutomatically syncing credentials between environments
• BEnsuring Elasticsearch clusters are identical versions
• CEstablishing a content promotion workflow for packs
• DMapping pack dependencies to avoid execution gaps
• EDisabling mappers in dev to avoid conflicts

• A
  30% (18)
• B
  8% (5)
• C
  44% (27)
• E
  18% (11)

Explanation

When planning a dev/prod XSOAR deployment, establishing a content promotion workflow (C) ensures that playbooks, integrations, and automations are systematically tested in dev before being promoted to production - without a defined process, untested content can break live incident response. Mapping pack dependencies (D) is equally critical because XSOAR packs often rely on other packs; if a dependent pack is missing or mismatched in prod, playbooks will fail mid-execution, creating dangerous gaps in your security operations.

Why the distractors are wrong:

• (A) Credentials are intentionally kept separate between environments for security isolation - auto-syncing them would defeat the purpose of environment separation.
• (B) Elasticsearch version matching is not an XSOAR planning requirement; XSOAR manages its own data layer and doesn't expose direct Elasticsearch dependency parity as a deployment concern.
• (E) Disabling mappers in dev is counterproductive - mappers translate incident fields and you need them active in dev to validate that data flows correctly before promoting to prod.

Memory tip: Think of it as a "shipping checklist" - you need a process to ship content (C = workflow) and a manifest of what each package needs (D = dependencies). Both answer "how do things move safely from dev to prod?"

No community discussion yet for this question.