Palo Alto Networks Certified Security Automation Engineer (PCSAE)IntegrationsEasy
A security architect is tasked with creating multiple integration instances for the same integration type (e.g., multiple instances of a 'VirusTotal' integration, each with a different API key or proxy setting, to handle different organizational units' needs). The architect needs to ensure that these instances are isolated from each other and can be configured independently without affecting other instances of the same integration. What is the fundamental concept in Cortex XSOAR that allows this independent configuration and execution?
- AIntegration Code
- BIntegration Instance
- CIntegration Engine
- DIntegration Pack
Show answer & explanationAnswer & explanation
Correct answer: B. Integration Instance
An 'Integration Instance' is the runtime configuration of an integration. It allows administrators to deploy multiple, independently configured instances of the same integration type, each with its own parameters (like API keys, URLs, proxy settings), ensuring isolation and flexibility.
Why the other options are wrong
- A. Integration code defines the logic, not the individual configurations.
- C. An Integration Engine is where the integration code runs, but it doesn't define the individual instance configurations.
- D. An Integration Pack bundles related content, but the instance is the configurable deployment unit.
Integration Instance
A specific, configurable deployment of an integration type in Cortex XSOAR, allowing for multiple independent connections to external services.
- Each instance has its own configuration parameters.
- Enables connecting to multiple accounts or environments of the same service.
- Can be assigned to different engines.
Memory trick: Instances are individual doors to the same integration house.