What are key elements of monitoring capabilities in Adobe RT-CDP? (Select two.)

Question

Options

• ATracking ingestion failures and processing delays.
• BConfiguring governance policies for data activation.
• CAnalyzing profile update errors.
• DExporting unified profiles to batch workflows.

• A
  76% (19)
• B
  16% (4)
• D
  8% (2)

Explanation

Monitoring in Adobe RT-CDP centers on observability into data health, which is why A (tracking ingestion failures and processing delays) and C (analyzing profile update errors) are correct - both directly address the platform's built-in dashboards for surfacing problems with data flowing in and profile records being updated. These are native monitoring features accessible in the Sources and Profile dashboards within the platform.

B is wrong because governance policy configuration is an access control and compliance feature (Data Governance/DULE), not a monitoring capability - it's about restricting data use, not observing system health.

D is wrong because exporting profiles to batch workflows is a data activation operation (Destinations), not a monitoring function - it's what you do with data, not how you watch over it.

Memory tip: Think "monitoring = watching for problems." If the answer choice describes doing something (configuring, exporting), it's not monitoring. If it describes detecting something going wrong (failures, errors, delays), it is.

No community discussion yet for this question.