Knowledge check PhotoRobot Viewer Layouts & Embedding
12 questions in pool · live exam draws 5
B21
Q1 multiple-choice · layout-types PhotoRobot Viewer offers two canonical layout types. Which are they?
Source: B21 textbook §2 (Buttons vs. Thumbnails).
Explanation: PhotoRobot Viewer’s two canonical layouts are Buttons (icon row at bottom for folder navigation) and Thumbnails (image strip alongside the main viewer, gallery-style). Configured under CAPP Cloud → Settings → Viewer layouts.
Q2 scenario · layout-choice · weight 2 Your customer is a fashion e-commerce site with rich product pages — multiple hero images, color variants, lifestyle shots, detail shots. Their existing product page shows a vertical thumbnail strip on the left and a large main image on the right.
Source: B21 textbook §2 (When to use Thumbnails).
Explanation: The customer’s existing product page establishes the visual pattern shoppers expect . Mixing a Buttons-layout viewer into a Thumbnails-layout page reads as inconsistency. Match the customer’s pattern. Fashion / e-commerce sites with rich visual content + variant gallery patterns = Thumbnails. Compact icon-led sites = Buttons.
Q3 multiple-choice · hot-spot-sweet-spot What’s the recommended number of hot spots per item in a PhotoRobot Viewer spin?
Source: B21 textbook §4 (Hot spot best practices).
Explanation: 2–4 hot spots per item is the sweet spot . Fewer = under-leveraging the feature. More = visual noise that overwhelms the spin. The job of a hot spot is to inform the shopper at the moment of curiosity , not display the entire spec sheet. Spec items go in the product description; hot spots highlight differentiated features.
Q4 scenario · hot-spot-inflation · weight 2 Your customer asks you to add 15 hot spots to each product spin — one for every feature in their marketing materials.
Source: B21 textbook §4 (Anti-pattern: hot spot inflation).
Explanation: Resist hot spot inflation. 15 hot spots on a single spin overwhelms the visual; shoppers stop reading any of them. Counter-propose the 4–6 most differentiating features as hot spots, with the remaining specs in product description text. Customers usually accept the counter-proposal once they see the cluttered alternative mocked up.
Q5 multiple-choice · idle-default-direction What’s the recommended default direction for idle auto-rotation, and why?
Source: B21 textbook §5 (Recommended baseline).
Explanation: Counter-clockwise is the recommended default in Western markets. The eye scans left-to-right; counter-clockwise rotation reveals the right side of the product first, which feels like natural picking-up motion. Subtle but tested across multiple PhotoRobot studios. Markets with right-to-left reading conventions (Arabic, Hebrew) may flip the default.
Q6 multiple-choice · image-format-default What’s the recommended default image format for the PhotoRobot Viewer spin folder, and at what quality?
Source: B21 textbook §6 (Image settings).
Explanation: WebP at quality 65–75 is the recommended default for the spin folder in the Viewer. WebP files are dramatically smaller than JPEG at equivalent visual quality, and the CDN serves dozens of frames per spin — bandwidth matters. Above 80 there’s diminishing visual return; below 60 quality damage becomes visible. PNG / TIFF reserved for special cases.
Q7 scenario · embed-choice · weight 2 Your customer is on Shopify and has no in-house developer. They want a PhotoRobot Viewer on every product page.
Source: B21 textbook §10 (Iframe vs. JS SDK).
Explanation: Iframe is the right starting point for non-developer customers on platforms like Shopify / WooCommerce. It’s isolated (no CSS conflict), trivial to embed (anyone who can paste HTML can use it), and PhotoRobot can update viewer behavior server-side. Upgrade to JS SDK only when the customer’s developer specifically needs variant-driven dynamic behavior (e.g., color selector switches viewer content).
Q8 multiple-choice · lazy-loading PhotoRobot Viewer lazy-loads spin frames by default. What does that mean?
Source: B21 textbook §11 (Lazy loading).
Explanation: Lazy loading = first frame loads with the page, additional frames load progressively as the user interacts. Most users rotate only ~30–60° before deciding “yes / no” — only a fraction of frames are actually loaded. This is what makes spin viewers tolerable on shopper bandwidth. Disabling lazy loading is the most common over-engineering mistake.
Q9 scenario · viewer-cascade · weight 2 Your studio manager finds themselves manually tweaking viewer settings on every individual item — hours per week. Every new item starts from scratch.
Source: B21 textbook §9 (Configuring per item, project, or organization).
Explanation: PhotoRobot Viewer settings cascade: Item > Project > Organization . The discipline: set organization-level defaults right (covers 80 % of items), use project-level for campaign-specific tweaks, reserve item-level for documented exceptions. If you’re doing >10 % item-level overrides, your organization-level defaults are wrong — fix the defaults, not each item.
Q10 multiple-choice · aspect-ratio PhotoRobot Viewer’s main viewer area supports which aspect ratios?
Source: B21 textbook §3 (Step 4 — Aspect ratio).
Explanation: PhotoRobot Viewer supports 1:1 (square) or 4:3 (slightly wider). 1:1 fits cleanly into grid-based e-commerce layouts (Shopify default, Amazon-style). 4:3 better for landscape-oriented products (furniture, carpets, large hardware). Pick the one matching the customer’s image grid — mixing aspects across a product page reads as inconsistency.
Q11 true-false · hot-spot-preservation Re-exporting an item from CAPP automatically deletes its viewer hot spots.
Source: B21 textbook §13 (Common failure modes — hot spots disappeared).
Explanation: False — re-exporting an item does NOT delete hot spots. Hot spots are stored per-item in the Cloud, separate from the captured image data. The only time hot spots vanish is when an item is re-imported / re-created in CAPP (treated as a new item, with no historical hot spot configuration). Re-export by itself preserves hot spots.
Q12 multiple-choice · preconnect-hint A customer in a region far from PhotoRobot’s CDN edge complains the viewer is slow on first load. What’s the simplest tuning step?
Source: B21 textbook §11 (CDN quirks).
Explanation: A preconnect hint in the page <head> tells the browser to establish DNS + TLS handshake to viewer.photorobot.com early, before the viewer starts requesting frames. This shaves hundreds of milliseconds off first-load latency for shoppers far from a CDN edge. Cheap to add, no negative side effects. Disabling lazy loading would actually make it slower; switching to JPEG would marginally help on file size but not the latency root cause.
Ready to commit? You can review and change your answers before submitting. Once submitted, this attempt is final and we'll show you your score, correct answers, and explanations.
Submit final answers
