I85PREP
⌘ K
Adobe Analytics Developer Expert study materials
Adobe Analytics Developer Expert study resources

Adobe Analytics Developer Expert practice questions

One question at a time. Build your Adobe Analytics Developer Expert understanding.

First 50 of 200 questions. Each one lists the choices, the correct answer, and an explanation. The checker at the top of this page saves progress in this browser when it is available.

Continue in the practice tool above to load more questions, 50 at a time.

Question 1Implementation planning and requirements gathering

Which document is the primary deliverable that defines what will be measured and why, before any Analytics code is written?

  1. The tag management audit
  2. The data layer specification
  3. The solution design reference Correct answer.
  4. The implementation timeline

Explanation

A solution design reference captures the business requirements, metrics, dimensions, and reporting intent that drive every implementation decision. It is the master reference against which the build is validated. Other artifacts support it but do not define measurement intent.

Question 2Implementation planning and requirements gathering

During requirements gathering, a stakeholder asks for a report on "customer satisfaction." What is the most appropriate next step for the developer?

  1. Ask what business decision the report will drive and how satisfaction is defined Correct answer.
  2. Build a survey page and start collecting responses
  3. Add a satisfaction variable to the data layer immediately
  4. Recommend a third-party survey tool instead

Explanation

Vague requests must be translated into measurable, decision-oriented requirements before design. Clarifying the business question and the operational definition of the concept prevents unusable dimensions. Implementation choices follow from that clarity.

Question 3Implementation planning and requirements gathering

Which set of elements belongs in a well-formed business requirements document for an Analytics implementation?

  1. JavaScript library versions and CDN endpoints
  2. Server hardware specs, network diagrams, and firewall rules
  3. KPI definitions, report consumers, and success criteria Correct answer.
  4. Cookie lifetimes and browser support matrices

Explanation

A business requirements document focuses on what the organization needs to know and who will use it. It defines KPIs, audiences, and how success will be judged. Technical specifications belong in separate design artifacts.

Question 4Implementation planning and requirements gathering

A client wants to track every click on a page. Which requirement-gathering question best scopes this request?

  1. Which clicks inform a business decision and what action follows? Correct answer.
  2. Which JavaScript framework renders the page?
  3. What is the current site traffic volume?
  4. How many pages exist on the site?

Explanation

Tracking every click creates noise and inflates data volume without answering a question. Scoping to clicks tied to business decisions keeps the design lean and maintainable. The other questions do not resolve what should be measured.

Question 5Implementation planning and requirements gathering

In a solution design reference, what is the primary purpose of mapping each variable to its report suite and expiration setting?

  1. To document how the variable behaves so reports remain interpretable over time Correct answer.
  2. To reduce the number of server calls
  3. To satisfy a legal disclosure requirement
  4. To determine the JavaScript file size

Explanation

The SDR records variable behavior, including scope and expiration, so future maintainers understand how data persists and reports are built. It is a governance and interpretation aid. It does not change server call counts or file size.

Question 6Implementation planning and requirements gathering

A stakeholder requests a dimension for "marketing channel" that must classify traffic from paid search, organic search, and email. What should the developer confirm during requirements gathering?

  1. The color palette for the dashboard
  2. The preferred report suite name
  3. The classification rules and the source of truth for each channel Correct answer.
  4. The number of marketing team members

Explanation

Classification logic determines whether the dimension will produce consistent, defensible reporting. Confirming the rules and the authoritative data source prevents ambiguous channel attribution. Other items do not affect measurement correctness.

Question 7Implementation planning and requirements gathering

Which artifact best captures the technical contract between the website's data layer and the tag management system?

  1. The data layer specification Correct answer.
  2. The stakeholder interview notes
  3. The KPI scorecard
  4. The business requirements document

Explanation

A data layer specification documents the exact variable names, types, and population timing that tags rely on. It serves as the contract between page developers and tag implementers. Business documents describe intent rather than the technical interface.

Question 8Implementation planning and requirements gathering

A client asks for a report on "time spent on page." Which clarification is most important before designing the metric?

  1. Whether the site uses responsive design
  2. How the metric should handle idle users and background tabs Correct answer.
  3. Whether the page has a footer
  4. Which browser versions are supported

Explanation

Time-based metrics are sensitive to idle behavior and tab switching, which can distort results. Defining how those cases are handled makes the metric interpretable. Layout and browser support do not define the metric's semantics.

Question 9Implementation planning and requirements gathering

Which question is most useful for identifying the report consumers of a proposed Analytics implementation?

  1. Which teams will make decisions from these reports? Correct answer.
  2. Which CDN hosts the JavaScript library?
  3. Which developer wrote the current tags?
  4. How many server calls does the site generate?

Explanation

Identifying decision-makers clarifies the audiences, cadence, and granularity the implementation must support. Report consumers shape requirements for dimensions and metrics. The other questions concern technical or historical details.

Question 10Implementation planning and requirements gathering

A stakeholder wants conversion data segmented by new versus returning visitors. Which requirement detail must be resolved to avoid ambiguity?

  1. The site's domain name
  2. The font used in the conversion confirmation page
  3. The number of products in the catalog
  4. How visitor status is determined and over what window Correct answer.

Explanation

New versus returning depends on how visitor identity is established and the lookback window applied. Specifying this prevents inconsistent segmentation. The other items do not affect visitor classification.

Question 11Implementation planning and requirements gathering

When gathering requirements for an e-commerce funnel, which sequence best represents the order of implementation planning?

  1. Define KPIs, then validate reports, then design variables
  2. Implement tags, then define KPIs, then validate reports
  3. Define KPIs and funnel steps, then design variables, then implement tags Correct answer.
  4. Build tags, then interview stakeholders, then define KPIs

Explanation

Measurement intent precedes design, and design precedes implementation. Defining KPIs and funnel steps first ensures variables and tags serve a clear purpose. Validation follows implementation.

Question 12Implementation planning and requirements gathering

What is the main risk of skipping a formal requirements phase and building the Analytics implementation directly from a stakeholder's verbal request?

  1. The tag management system will reject the container
  2. The JavaScript library will fail to load
  3. The implementation may measure the wrong things and require costly rework Correct answer.
  4. The report suite will be deleted automatically

Explanation

Without documented requirements, the implementation may not match business needs, leading to rework and unreliable data. The other outcomes are not consequences of skipping requirements.

Question 13Implementation planning and requirements gathering

A client wants to track form abandonment. Which specification detail is essential to define the abandonment event correctly?

  1. The form's hosting provider
  2. The form's background color
  3. Which fields are mandatory and when a submission counts as complete Correct answer.
  4. The number of form pages on the site

Explanation

Abandonment is defined relative to what constitutes a completed submission and which fields matter. Specifying mandatory fields and completion criteria makes the metric well-defined. Styling, page count, and hosting do not define the event.

Question 14Implementation planning and requirements gathering

Which requirement-gathering technique is most effective for uncovering undocumented reporting needs across multiple teams?

  1. Counting the number of pages on the site
  2. Conducting structured interviews with representatives from each team Correct answer.
  3. Reading the site's HTML source
  4. Reviewing the CDN configuration

Explanation

Structured interviews surface needs that are not written down and reveal cross-team dependencies. Technical inspection cannot reveal business intent. Interviews are a standard elicitation method for this purpose.

Question 15Implementation planning and requirements gathering

A stakeholder requests that a campaign dimension capture both the campaign name and the creative variant. What design decision should the developer raise during planning?

  1. Whether to use a single concatenated value or two separate dimensions Correct answer.
  2. Whether the site uses HTTPS
  3. Whether the report suite has a time zone
  4. Which analytics library version is installed

Explanation

Combining values into one dimension versus splitting into two affects reporting flexibility and cardinality. This is a design decision that should be agreed during planning. The other items do not address how campaign data is structured.

Question 16Implementation planning and requirements gathering

Which statement best describes the role of success criteria in an Analytics implementation plan?

  1. They define the technical stack for tagging
  2. They provide a measurable standard for judging whether the implementation meets its goals Correct answer.
  3. They list the names of all report suite users
  4. They specify the JavaScript framework to use

Explanation

Success criteria state how the implementation's effectiveness will be evaluated, such as data accuracy or report adoption. They give the project a measurable target. Technical stack and user lists are separate concerns.

Question 17Implementation planning and requirements gathering

A client wants a report on "content engagement" but has no defined metric. Which approach best translates this into an implementable requirement?

  1. Agree on specific behaviors such as video plays and scroll depth thresholds Correct answer.
  2. Record all mouse movements
  3. Track every scroll event on every page
  4. Capture the page's word count

Explanation

Engagement must be operationalized through agreed, observable behaviors. Selecting specific behaviors with thresholds yields a usable metric. Tracking everything creates noise and high data volume.

Question 18Implementation planning and requirements gathering

During planning, a stakeholder asks for real-time reporting on all dimensions. What is the most appropriate developer response?

  1. Explain the tradeoffs of real-time reporting and confirm which dimensions truly need it Correct answer.
  2. Disable reporting entirely until the request is withdrawn
  3. Agree to build it because real-time is always available
  4. Recommend abandoning Analytics for a data warehouse

Explanation

Real-time reporting has limitations in scope and latency, so requirements should be scoped to the dimensions that genuinely need immediacy. Explaining tradeoffs lets stakeholders make an informed decision. The other responses are unhelpful or extreme.

Question 19Implementation planning and requirements gathering

Which element of a solution design reference identifies the person accountable for each variable's definition and maintenance?

  1. The owner field Correct answer.
  2. The report suite mapping
  3. The variable description
  4. The expiration setting

Explanation

An owner field assigns accountability for a variable so definitions are maintained and changes are governed. Descriptions explain purpose, expiration governs persistence, and report suite mapping shows availability.

Question 20Implementation planning and requirements gathering

A client's site uses a single-page application. Which requirement detail most affects how page-view measurement must be designed?

  1. The brand's logo design
  2. The number of marketing emails sent monthly
  3. How virtual page views are triggered on route changes Correct answer.
  4. The preferred report color scheme

Explanation

In single-page applications, page views do not occur on full loads, so the trigger for virtual page views on route changes must be specified. This determines whether page-level reporting is accurate. The other items do not affect page-view measurement.

Question 21Implementation planning and requirements gathering

Which requirement is most likely to be missed if the developer gathers input only from the marketing team?

  1. Email click-through metrics
  2. Promotional landing page metrics
  3. Operational reporting needs of customer support Correct answer.
  4. Campaign tracking needs

Explanation

Different teams have distinct reporting needs, and support operations may require data the marketing team does not consider. Gathering input across teams prevents blind spots. The other items are typical marketing concerns.

Question 22Implementation planning and requirements gathering

What is the primary benefit of documenting assumptions and constraints in an Analytics implementation plan?

  1. They increase the number of server calls
  2. They make tradeoffs explicit so future changes can be evaluated against known limits Correct answer.
  3. They guarantee accurate data automatically
  4. They eliminate the need for testing

Explanation

Documented assumptions and constraints record the conditions under which the design was made, so later changes can be assessed against them. They support governance but do not replace testing or guarantee accuracy.

Question 23Implementation planning and requirements gathering

A stakeholder wants to compare revenue across regions and product categories in one report. Which planning consideration is most relevant?

  1. How many dimensions the report can break down by and at what granularity Correct answer.
  2. Whether the site uses a content delivery network
  3. The number of employees in each region
  4. The color of the checkout button

Explanation

Multi-dimension reporting depends on how many breakdowns are supported and the granularity of the data. This affects whether the requested comparison is feasible. CDN use, staffing, and styling do not affect report feasibility.

Question 24Implementation planning and requirements gathering

Which question best tests whether a proposed KPI is actionable?

  1. How many characters is the KPI name?
  2. How often is the JavaScript library updated?
  3. What action would the business take if this KPI moved significantly? Correct answer.
  4. Which server hosts the data?

Explanation

An actionable KPI is tied to a decision or behavior the business can change. Asking what action would follow reveals whether the metric has practical value. The other questions concern naming, hosting, and maintenance.

Question 25Tags, tag management, and data layer design

In Adobe Experience Platform Tags, what is the primary purpose of a data element?

  1. To host the JavaScript file that loads on the page
  2. To group rules into logical categories in the interface
  3. To schedule when the tag library is published to production
  4. To define a reusable pointer to a value that rules and extensions can reference Correct answer.

Explanation

Data elements are named variables that retrieve values from the data layer, cookies, query strings, or other sources. Rules and extensions reference them by name so the retrieval logic is defined once and reused.

Question 26Tags, tag management, and data layer design

Which object is the standard Adobe-recommended global namespace for a client-side data layer?

  1. window.analyticsLayer
  2. window.digitalData
  3. window.adobeDataLayer Correct answer.
  4. window.tagManagerData

Explanation

Adobe's recommended data layer is exposed as window.adobeDataLayer, an event-driven array that supports pushing events and state changes. Extensions subscribe to these events to trigger rules.

Question 27Tags, tag management, and data layer design

A developer wants a rule to fire only after a specific custom event has been pushed to the data layer. Which rule configuration accomplishes this?

  1. An event of type Library Loaded with a data element condition
  2. An event of type Data Element Changed targeting the event name
  3. An event of type Custom Event with a matching event name Correct answer.
  4. An event of type Direct Call with a matching string identifier

Explanation

The Custom Event rule type listens for events dispatched on the data layer (or document) and can filter by event name. This lets rules react to pushes such as a product view.

Question 28Tags, tag management, and data layer design

What does a tag property's Development environment typically point to?

  1. The library build used for testing before promotion Correct answer.
  2. The Adobe Experience Cloud shared asset library
  3. The production CDN URL served to all visitors
  4. A locked snapshot that cannot be modified

Explanation

Each property has environments (typically Development, Staging, Production). The Development environment hosts the working library used for building and testing changes before they are promoted.

Question 29Tags, tag management, and data layer design

Which extension is required to send beacon data to Adobe Analytics from a tag property?

  1. Experience Cloud ID Service
  2. Adobe Analytics Correct answer.
  3. Data Layer Manager
  4. Core

Explanation

The Adobe Analytics extension provides the AppMeasurement library and the action types used to set variables and send beacons. The ID Service is commonly used alongside it but does not send Analytics hits itself.

Question 30Tags, tag management, and data layer design

In the Adobe Analytics extension configuration, what does the 'Track by Adobe Experience Platform' setting control?

  1. Whether the property uses a first-party cookie domain
  2. Whether hits are sent through the Edge Network instead of AppMeasurement Correct answer.
  3. Whether data elements are available to rules
  4. Whether the library is minified during build

Explanation

Enabling the Experience Platform tracking option routes Analytics data through the Adobe Experience Platform Edge Network rather than legacy AppMeasurement collection. This affects how and where hits are transmitted.

Question 31Tags, tag management, and data layer design

Which data element type would a developer choose to read a value directly from the browser's URL query string?

  1. JavaScript Variable
  2. Cookie
  3. Query String Parameter Correct answer.
  4. DOM Attribute

Explanation

The Query String Parameter data element type parses the current URL and returns the value of a named parameter. It avoids custom scripting for common URL-based values.

Question 32Tags, tag management, and data layer design

Which rule event type fires when the user scrolls a specified percentage down the page?

  1. Click
  2. Entrance
  3. Element Visibility
  4. Scroll Depth Correct answer.

Explanation

The Scroll Depth event type triggers when the user scrolls past configured percentage or pixel thresholds. Element Visibility instead tracks whether a specific element is in the viewport.

Question 33Tags, tag management, and data layer design

A developer needs a rule action that sets multiple Analytics variables before sending a beacon. Which action sequence is correct?

  1. Set Variables only, which auto-sends
  2. Clear Variables, then Set Variables
  3. Set Variables, then Send Beacon Correct answer.
  4. Send Beacon, then Set Variables

Explanation

Analytics variables must be populated before the beacon is transmitted, so Set Variables precedes Send Beacon within the rule. Setting variables alone does not transmit data.

Question 34Tags, tag management, and data layer design

What is the effect of setting a rule's order value lower than another rule that shares the same event?

  1. The lower-order rule executes after the higher-order rule
  2. The rule is disabled until order is reset
  3. Order has no effect on execution sequence
  4. The lower-order rule executes before the higher-order rule Correct answer.

Explanation

Rules with the same event execute in ascending order value, so a lower number runs first. This lets developers sequence dependent logic deterministically.

Question 35Tags, tag management, and data layer design

Why does Adobe recommend building the data layer before the tag library loads?

  1. It disables the Experience Cloud ID Service
  2. It prevents the Analytics extension from firing
  3. It ensures data is available when rules evaluate at Library Loaded Correct answer.
  4. It reduces the size of the published library

Explanation

Rules that fire at Library Loaded or DOM Ready evaluate immediately, so the data layer must already contain the values they reference. Building the data layer above the embed code guarantees availability.

Question 36Tags, tag management, and data layer design

A developer wants to attach a custom script that runs only after the tag library has fully initialized. Which Core event type is appropriate?

  1. Library Loaded (Page Top) Correct answer.
  2. Direct Call
  3. DOM Ready
  4. Window Loaded

Explanation

Library Loaded (Page Top) fires as soon as the tag library initializes, making it suitable for setup logic that must run before other rules. DOM Ready and Window Loaded depend on page lifecycle events.

Question 37Tags, tag management, and data layer design

Which approach best avoids race conditions when multiple rules push to the same Analytics variable?

  1. Rely on alphabetical rule names to determine order
  2. Set the variable in each rule and let the last one win
  3. Increase the rule order value on every rule
  4. Consolidate the logic into a single rule with ordered actions Correct answer.

Explanation

Combining related variable-setting logic into one rule with ordered actions removes ambiguity about which value persists. Multiple independent rules writing the same variable create order-dependent results.

Question 38Tags, tag management, and data layer design

What does the _satellite.track() function do in a tag implementation?

  1. It sends an Analytics beacon directly
  2. It clears all data elements
  3. It triggers a Direct Call rule with the supplied identifier Correct answer.
  4. It reloads the tag library from the CDN

Explanation

_satellite.track(identifier) invokes any Direct Call rule whose string identifier matches, allowing code outside the tag library to trigger rules. It is not an Analytics-specific beacon method.

Question 39Tags, tag management, and data layer design

A developer needs to persist a value across pages using a first-party cookie set by the tag library. Which Core action accomplishes this?

  1. Write Variable
  2. Persist Data
  3. Store Value
  4. Set Cookie Correct answer.

Explanation

The Core extension provides a Set Cookie action that writes a named cookie with configurable domain, path, and expiration. This persists a value across pages.

Question 40Tags, tag management, and data layer design

Which data element type is most appropriate for reading a value from a global JavaScript object nested at window.myApp.user.id?

  1. JavaScript Variable Correct answer.
  2. Meta Tag
  3. Cookie
  4. Query String Parameter

Explanation

The JavaScript Variable data element type accepts a dot-notation path to a global object and returns its value. This reads nested application state directly.

Question 41Tags, tag management, and data layer design

Why is it problematic to reference a data element in a rule that fires before the element's source is populated?

  1. The data element returns undefined and the rule may send incorrect data Correct answer.
  2. The rule fails to publish
  3. The extension is automatically removed
  4. The library rebuilds with an error

Explanation

Data elements resolve at rule execution time; if the underlying source is empty, the value is undefined. Rules that depend on that value can then send incomplete or incorrect data.

Question 42Tags, tag management, and data layer design

Which statement best describes how the Experience Cloud ID Service extension interacts with Analytics in tags?

  1. It blocks Analytics hits until consent is given
  2. It generates the report suite ID
  3. It provides the visitor ID that Analytics uses in hits Correct answer.
  4. It replaces the Analytics extension entirely

Explanation

The ID Service extension sets the Experience Cloud visitor ID, which Analytics references in its hits for cross-solution identity. It works alongside, not instead of, the Analytics extension.

Question 43Tags, tag management, and data layer design

A developer wants a rule to fire only on the checkout page, identified by a data layer page type. Which condition type is most direct?

  1. A Custom Code condition that reloads the page
  2. A Randomization condition
  3. A Value Comparison condition on a data element Correct answer.
  4. A Time on Site condition

Explanation

A Value Comparison condition compares a data element or value against an expected string, such as pageType equals checkout. This scopes the rule to the intended page.

Question 44Tags, tag management, and data layer design

What is the correct order of the publishing flow in Adobe Experience Platform Tags?

  1. Build, Publish, Approve
  2. Publish, Build, Approve
  3. Approve, Build, Publish
  4. Build, Approve, Publish Correct answer.

Explanation

A library is built from the development environment, then approved (in environments requiring approval), and finally published to its target environment. Build precedes approval and publication.

Question 45Tags, tag management, and data layer design

A developer observes that an Analytics beacon sends before the data layer push that should populate eVar values. What is the most likely cause?

  1. The report suite is misconfigured
  2. The cookie domain is set incorrectly
  3. The Experience Cloud ID Service is disabled
  4. The rule fires on a page-top event rather than the data layer event Correct answer.

Explanation

If the rule triggers at Library Loaded or DOM Ready before the data layer push occurs, variables are empty at beacon time. Triggering on the relevant Custom Event ensures data is present.

Question 46Tags, tag management, and data layer design

Which design best supports an event-driven data layer where multiple rules react to the same push?

  1. Data is written to cookies and read on the next page
  2. Rules subscribe to a named event and read state from the event payload Correct answer.
  3. Each rule reads the same global object independently
  4. A single rule sets every variable for all tools

Explanation

An event-driven data layer dispatches named events with payloads so any number of rules can subscribe and read relevant state. This decouples producers from consumers and avoids duplicated reads.

Question 47Tags, tag management, and data layer design

A developer needs to validate that a data element returns a non-empty string before a rule sends a beacon. Which approach enforces this?

  1. An Entrance event with a page view type
  2. A Custom Code action that logs the value
  3. A Send Beacon action with a fallback value
  4. A Value Comparison condition requiring the value to be non-empty Correct answer.

Explanation

A Value Comparison condition can require the data element to match a non-empty pattern before actions execute. Conditions gate the rule so the beacon only sends with valid data.

Question 48Tags, tag management, and data layer design

When migrating from a legacy hardcoded AppMeasurement implementation to tags, which practice best preserves data continuity?

  1. Change report suite IDs to distinguish old and new data
  2. Remove all legacy code before validating the tag implementation
  3. Disable the Analytics extension until the migration completes
  4. Map existing variables to data elements and replicate the same variable assignments in rules Correct answer.

Explanation

Replicating existing variable assignments through data elements and rules keeps the payload consistent during migration. Validating parity before removing legacy code protects data continuity.

Question 49Tags, tag management, and data layer design

A developer wants a rule to fire for a custom 'productView' event but only when the product category is 'electronics'. Which combination achieves this?

  1. A Custom Event rule with a Value Comparison condition on the category data element Correct answer.
  2. A Click event with a Custom Code action
  3. A Library Loaded event with a Time on Site condition
  4. A Direct Call event with a randomization condition

Explanation

A Custom Event rule scoped by event name triggers on the push, and a Value Comparison condition filters on the category value. Together they target the exact scenario.

Question 50Tags, tag management, and data layer design

A developer wants a rule to fire on every page view but only after the data layer has been populated with page metadata. Which event type best matches this requirement?

  1. A Core Direct Call event triggered manually in the page head before the data layer loads
  2. A Core click event bound to the document body
  3. A Core event such as Library Loaded, because it guarantees the data layer is already populated
  4. A custom event dispatched by the site's data layer push, because it signals that the metadata is available Correct answer.

Explanation

A custom event tied to the data layer push fires at the moment the metadata becomes available, so the rule reads complete values. Library Loaded only indicates the tag library initialized, not that the page's data layer has been populated. Direct Call and click events do not inherently align with data layer readiness.