Braze Practitioner Level 1 Exam Ultimate Study Guide
Braze Practitioner Level 1 Exam — 60 Multiple-Choice Questions
Domain 1: Braze Platform Fundamentals & Architecture (Q1–Q8)
1. Which tab on the Braze dashboard serves as the primary hub for creating and
managing outbound messaging campaigns?
A) Users tab
B) Campaigns tab
C) Analytics tab
D) Segments tab
Rationale: The Campaigns tab on the Braze dashboard is the primary interface for creating,
managing, and monitoring all outbound messaging campaigns, including one-time, recurring,
triggered, and broadcast campaigns. From this tab, practitioners can create new campaigns,
view campaign status (draft, active, stopped, archived), access campaign analytics, duplicate
existing campaigns, and manage multi-channel message composition. The Users tab is for
individual user profile lookup and management, the Analytics tab provides aggregate reporting
and data visualization, and the Segments tab is for building and managing audience segments
used in campaigns and Canvases.
2. What is the primary purpose of separating Braze workspaces into Dev, Staging,
and Production environments?
A) To reduce platform subscription costs
B) To enable safe testing of campaigns and Canvas flows without impacting live
users, while ensuring data integrity across the development lifecycle
C) To increase the number of API endpoints available
D) To comply with GDPR data residency requirements
Rationale: Environment separation (Dev/Staging/Production) is a Braze governance best
practice that enables teams to build, test, and validate campaigns, Canvas flows, segments, and
Liquid logic in non-production workspaces without risking unintended messages reaching live
users. Dev environments are used for initial development and debugging, Staging for QA and
user acceptance testing with test user profiles, and Production for live messaging to real
customers. This separation prevents costly errors such as sending test messages to real
customers, ensures data integrity by keeping test events and attributes separate from
production data, and supports change management workflows including approval gates before
promotion to production.
3. Which of the following correctly describes the difference between an External
User ID and a Braze User ID?
A) They are identical and can be used interchangeably
B) The External User ID is assigned by the customer's system to identify a user
across integrations, while the Braze User ID (braze_id) is an internally
generated identifier assigned by the Braze platform
C) The Braze User ID is set by the customer, and the External User ID is generated by Braze
D) Only the Braze User ID can be used for segmentation
,Rationale: The External User ID (often called external_id) is a customer-defined identifier that
the integrating application sets via the Braze SDK or API to uniquely identify a user across the
customer's technology stack (e.g., a CRM customer ID, database primary key, or SSO
identifier). It enables data reconciliation between Braze and external systems. The Braze User
ID (braze_id) is a system-generated UUID assigned internally by Braze when a user profile is
first created. While both can be used to identify users within Braze, the external_id is the
preferred identifier for API calls, data integration, and cross-platform user matching because it
provides a stable, customer-controlled reference. Users without an external_id are considered
anonymous and are identified only by their braze_id.
4. Which data ingestion method is most appropriate for importing historical user
attribute data in bulk without requiring developer resources?
A) Braze REST API with programmatic scripting
B) CSV upload via the Braze dashboard
C) Braze SDK integration
D) Real-time event streaming via Kafka
Rationale: CSV upload via the Braze dashboard is the most appropriate method for importing
historical user attribute data in bulk without requiring developer resources. The CSV import
feature allows marketing operations practitioners to upload user data files (with columns
mapping to user attributes) directly through the dashboard interface, making it accessible to
non-technical team members. This method is ideal for one-time data migrations, backfilling
historical data, or updating user attributes from offline sources. The REST API (option A)
requires developer resources to write scripts. The SDK (option C) is designed for real-time event
and attribute tracking from applications, not bulk historical imports. Kafka streaming (option
D) is an advanced integration method requiring significant engineering infrastructure and is
suited for real-time event pipelines rather than bulk attribute imports.
5. Custom attributes in Braze are best described as:
A) Actions that users take within the application, such as clicking a button
B) Descriptive characteristics or properties attached to a user profile, such as
subscription_tier or loyalty_points
C) System-generated identifiers for API authentication
D) Message delivery status indicators
Rationale: Custom attributes in Braze are descriptive data fields attached to individual user
profiles that represent properties, characteristics, or state information about the user. Examples
include subscription_tier (e.g., 'premium', 'basic'), loyalty_points (numeric value),
preferred_language, or last_purchase_date. Custom attributes are used for audience
segmentation, message personalization via Liquid, and conditional logic in Canvas flows. They
differ from custom events (option A), which represent actions users take (e.g.,
'completed_purchase', 'viewed_product'). Attributes answer 'who is this user?' while events
answer 'what did this user do?' This distinction is fundamental to Braze data architecture and
directly impacts segmentation strategy, personalization capabilities, and reporting accuracy.
6. Which Braze dashboard tab is used to create and manage audience segments for
use in campaigns and Canvas flows?
A) Campaigns tab
B) Content tab
C) Segments tab
D) Settings tab
, Rationale: The Segments tab on the Braze dashboard is the dedicated interface for creating,
editing, and managing audience segments. From this tab, practitioners use the Segment Builder
to define audience criteria using filters based on user attributes, custom events, purchase events,
engagement history, and other data points. Segments can be previewed to estimate audience
size, tested for filter logic accuracy, and then referenced by campaigns and Canvas flows. The
Segments tab also displays segment details including estimated size, last updated timestamp,
and which campaigns/Canvases are currently using each segment. The Campaigns tab
manages messaging, the Content tab manages templates and content blocks, and the Settings
tab manages workspace configuration.
7. A practitioner needs to track when a user completes a specific in-app action
(e.g., 'added_to_wishlist'). Which data type should be logged?
A) Custom attribute
B) Custom event
C) Default attribute
D) Purchase event
Rationale: Custom events in Braze are designed to track specific actions or behaviors that users
perform within an application, such as 'added_to_wishlist', 'viewed_product',
'completed_tutorial', or 'shared_content'. Custom events capture the occurrence, timestamp,
and optional event properties (key-value pairs providing contextual detail about the action).
They are the correct data type for tracking user actions because they support event-based
segmentation (e.g., 'users who performed added_to_wishlist in the last 7 days'), triggered
campaign delivery (e.g., send a push notification when added_to_wishlist occurs), and
behavioral analytics. Custom attributes (option A) describe user state/properties, not actions.
Default attributes are system-defined fields like email or first_name. Purchase events are a
specialized event type specifically for revenue-generating transactions.
8. Which integration method allows non-developer team members to connect
Braze with other marketing tools using a visual, no-code interface?
A) Braze REST API with custom scripting
B) Braze SDK direct integration
C) Zapier integration with pre-built Braze triggers and actions
D) Custom webhook development from scratch
Rationale: Zapier integration provides a visual, no-code interface that allows non-developer
team members to connect Braze with thousands of other marketing tools using pre-built
triggers (e.g., 'New Custom Event in Braze') and actions (e.g., 'Create or Update User in Braze').
Zapier automates workflows between Braze and platforms like Google Sheets, Slack, Salesforce,
Shopify, and HubSpot without requiring custom code. This democratizes integration
capabilities and reduces reliance on engineering resources for common data flow scenarios. The
REST API (option A) requires developer scripting, the SDK (option B) requires engineering
implementation in the application codebase, and custom webhook development (option D)
requires programming expertise. While Zapier has limitations in throughput and complexity
compared to direct API integrations, it excels in accessibility and speed of deployment for
standard use cases.
Domain 2: Audience Segmentation & Targeting (Q9–Q17)
9. In the Braze Segment Builder, applying filters with AND logic means that a user
must:
A) Meet at least one of the specified filter conditions
Braze Practitioner Level 1 Exam — 60 Multiple-Choice Questions
Domain 1: Braze Platform Fundamentals & Architecture (Q1–Q8)
1. Which tab on the Braze dashboard serves as the primary hub for creating and
managing outbound messaging campaigns?
A) Users tab
B) Campaigns tab
C) Analytics tab
D) Segments tab
Rationale: The Campaigns tab on the Braze dashboard is the primary interface for creating,
managing, and monitoring all outbound messaging campaigns, including one-time, recurring,
triggered, and broadcast campaigns. From this tab, practitioners can create new campaigns,
view campaign status (draft, active, stopped, archived), access campaign analytics, duplicate
existing campaigns, and manage multi-channel message composition. The Users tab is for
individual user profile lookup and management, the Analytics tab provides aggregate reporting
and data visualization, and the Segments tab is for building and managing audience segments
used in campaigns and Canvases.
2. What is the primary purpose of separating Braze workspaces into Dev, Staging,
and Production environments?
A) To reduce platform subscription costs
B) To enable safe testing of campaigns and Canvas flows without impacting live
users, while ensuring data integrity across the development lifecycle
C) To increase the number of API endpoints available
D) To comply with GDPR data residency requirements
Rationale: Environment separation (Dev/Staging/Production) is a Braze governance best
practice that enables teams to build, test, and validate campaigns, Canvas flows, segments, and
Liquid logic in non-production workspaces without risking unintended messages reaching live
users. Dev environments are used for initial development and debugging, Staging for QA and
user acceptance testing with test user profiles, and Production for live messaging to real
customers. This separation prevents costly errors such as sending test messages to real
customers, ensures data integrity by keeping test events and attributes separate from
production data, and supports change management workflows including approval gates before
promotion to production.
3. Which of the following correctly describes the difference between an External
User ID and a Braze User ID?
A) They are identical and can be used interchangeably
B) The External User ID is assigned by the customer's system to identify a user
across integrations, while the Braze User ID (braze_id) is an internally
generated identifier assigned by the Braze platform
C) The Braze User ID is set by the customer, and the External User ID is generated by Braze
D) Only the Braze User ID can be used for segmentation
,Rationale: The External User ID (often called external_id) is a customer-defined identifier that
the integrating application sets via the Braze SDK or API to uniquely identify a user across the
customer's technology stack (e.g., a CRM customer ID, database primary key, or SSO
identifier). It enables data reconciliation between Braze and external systems. The Braze User
ID (braze_id) is a system-generated UUID assigned internally by Braze when a user profile is
first created. While both can be used to identify users within Braze, the external_id is the
preferred identifier for API calls, data integration, and cross-platform user matching because it
provides a stable, customer-controlled reference. Users without an external_id are considered
anonymous and are identified only by their braze_id.
4. Which data ingestion method is most appropriate for importing historical user
attribute data in bulk without requiring developer resources?
A) Braze REST API with programmatic scripting
B) CSV upload via the Braze dashboard
C) Braze SDK integration
D) Real-time event streaming via Kafka
Rationale: CSV upload via the Braze dashboard is the most appropriate method for importing
historical user attribute data in bulk without requiring developer resources. The CSV import
feature allows marketing operations practitioners to upload user data files (with columns
mapping to user attributes) directly through the dashboard interface, making it accessible to
non-technical team members. This method is ideal for one-time data migrations, backfilling
historical data, or updating user attributes from offline sources. The REST API (option A)
requires developer resources to write scripts. The SDK (option C) is designed for real-time event
and attribute tracking from applications, not bulk historical imports. Kafka streaming (option
D) is an advanced integration method requiring significant engineering infrastructure and is
suited for real-time event pipelines rather than bulk attribute imports.
5. Custom attributes in Braze are best described as:
A) Actions that users take within the application, such as clicking a button
B) Descriptive characteristics or properties attached to a user profile, such as
subscription_tier or loyalty_points
C) System-generated identifiers for API authentication
D) Message delivery status indicators
Rationale: Custom attributes in Braze are descriptive data fields attached to individual user
profiles that represent properties, characteristics, or state information about the user. Examples
include subscription_tier (e.g., 'premium', 'basic'), loyalty_points (numeric value),
preferred_language, or last_purchase_date. Custom attributes are used for audience
segmentation, message personalization via Liquid, and conditional logic in Canvas flows. They
differ from custom events (option A), which represent actions users take (e.g.,
'completed_purchase', 'viewed_product'). Attributes answer 'who is this user?' while events
answer 'what did this user do?' This distinction is fundamental to Braze data architecture and
directly impacts segmentation strategy, personalization capabilities, and reporting accuracy.
6. Which Braze dashboard tab is used to create and manage audience segments for
use in campaigns and Canvas flows?
A) Campaigns tab
B) Content tab
C) Segments tab
D) Settings tab
, Rationale: The Segments tab on the Braze dashboard is the dedicated interface for creating,
editing, and managing audience segments. From this tab, practitioners use the Segment Builder
to define audience criteria using filters based on user attributes, custom events, purchase events,
engagement history, and other data points. Segments can be previewed to estimate audience
size, tested for filter logic accuracy, and then referenced by campaigns and Canvas flows. The
Segments tab also displays segment details including estimated size, last updated timestamp,
and which campaigns/Canvases are currently using each segment. The Campaigns tab
manages messaging, the Content tab manages templates and content blocks, and the Settings
tab manages workspace configuration.
7. A practitioner needs to track when a user completes a specific in-app action
(e.g., 'added_to_wishlist'). Which data type should be logged?
A) Custom attribute
B) Custom event
C) Default attribute
D) Purchase event
Rationale: Custom events in Braze are designed to track specific actions or behaviors that users
perform within an application, such as 'added_to_wishlist', 'viewed_product',
'completed_tutorial', or 'shared_content'. Custom events capture the occurrence, timestamp,
and optional event properties (key-value pairs providing contextual detail about the action).
They are the correct data type for tracking user actions because they support event-based
segmentation (e.g., 'users who performed added_to_wishlist in the last 7 days'), triggered
campaign delivery (e.g., send a push notification when added_to_wishlist occurs), and
behavioral analytics. Custom attributes (option A) describe user state/properties, not actions.
Default attributes are system-defined fields like email or first_name. Purchase events are a
specialized event type specifically for revenue-generating transactions.
8. Which integration method allows non-developer team members to connect
Braze with other marketing tools using a visual, no-code interface?
A) Braze REST API with custom scripting
B) Braze SDK direct integration
C) Zapier integration with pre-built Braze triggers and actions
D) Custom webhook development from scratch
Rationale: Zapier integration provides a visual, no-code interface that allows non-developer
team members to connect Braze with thousands of other marketing tools using pre-built
triggers (e.g., 'New Custom Event in Braze') and actions (e.g., 'Create or Update User in Braze').
Zapier automates workflows between Braze and platforms like Google Sheets, Slack, Salesforce,
Shopify, and HubSpot without requiring custom code. This democratizes integration
capabilities and reduces reliance on engineering resources for common data flow scenarios. The
REST API (option A) requires developer scripting, the SDK (option B) requires engineering
implementation in the application codebase, and custom webhook development (option D)
requires programming expertise. While Zapier has limitations in throughput and complexity
compared to direct API integrations, it excels in accessibility and speed of deployment for
standard use cases.
Domain 2: Audience Segmentation & Targeting (Q9–Q17)
9. In the Braze Segment Builder, applying filters with AND logic means that a user
must:
A) Meet at least one of the specified filter conditions
