Optimizely supports client‑side web experiments and server‑side feature experimentation with flags. This quiz checks your understanding of core capabilities and good practices.
In Optimizely’s feature experimentation, a ______ controls whether a capability is shown without redeploying code.
feature flag
DOM selector
browser cookie
CSS token
Optimizely’s Stats Engine is designed to manage multiple metrics and variations by controlling the ______ rate.
image sampling
false discovery
cache eviction
scroll
A common way to limit blast radius during a rollout is a targeted ______ such as 1%→5%→25% traffic.
staged ramp
one‑shot jump
random CSS cycle
pixel cascade
Server‑side experiments typically randomize at the ______ level to avoid cross‑session contamination.
pageview
IP octet
pixel
user
Mutual exclusivity between experiments helps prevent ______ when tests overlap on the same users.
font fallback
gzip inflation
interaction and contamination
CDN pinning
Audiences in Optimizely are used to ______.
purge caches
target variations to specific user segments
compile JavaScript
resize images
Event tracking in experiments should capture primary KPIs and ______ guardrails.
hex colors
image DPI
CSS z‑index
safety or performance
A holdout can be preserved to estimate long‑run impact by keeping a small share on ______.
control
preload
offline cache
iframes only
Warehouse‑native analytics or BigQuery pipelines are often used to run deeper analyses on ______ data.
raw experiment event
favicon
SVG path
sprite sheet
When many goals are tracked, it’s good practice to declare one primary and treat others as ______.
immutable
deprecated
render‑blocking
secondary (exploratory)
Starter
New to optimizely platform deep dive? Review fundamentals and practice with simple examples before scaling.
Solid
Good grasp of optimizely platform deep dive. Tighten design choices and deepen analysis to improve reliability.
Expert!
Excellent command of optimizely platform deep dive. You’re ready for complex rollouts and edge‑case diagnostics.
