Constructus Temporary Buildings

Study Note

This page brings together public scenario links and AI-assisted research notes for study use. Start with the scenario brief, make your own attempt, and open the spoiler section only when you are ready to compare.

Scenario Snapshot

Field	Detail
Start here	Current scenario brief hub
Scenario source	Community scenario (Andrew Hart / CTA202)
Current status	Live (AH)
First public date	2021-01
Primary source	Open primary source
Coverage available	Scenario brief + Video or presentation + Public Q&A + Discussion or analysis

Only Open If You Have Attempted the Scenario

The section below contains public follow-up links, board-call material, and AI-assisted notes compiled from those public sources.

Open follow-up links, Q&A, and analysis

Follow-Up Links

Board Insights & Common Pitfalls

Generalized Judge Questions

Asset Availability: “How do you handle the ‘nearest depot’ requirement? Why did you choose a custom LWC over standard Salesforce functionality?”
Maintenance Strategy: “How are you storing maintenance schedules? If at the Product level, how do you handle exceptions for specific high-wear assets?”
FSL vs. Custom: “The scenario involves maintenance and skill-based assignments. Why did you (or didn’t you) recommend Field Service (FSL)? If you didn’t, how are you handling ‘shortest distance’ or ‘optimization’?”
Object Selection: “Why use Work Orders for installation instead of repurposing the Order object? What are the trade-offs for reporting and visibility?”
Procurement Flow: “When an asset isn’t available, you trigger procurement. Is this a separate Opportunity, a specific Order record type, or an external ERP integration?”

Common Mistakes

Over-Engineering Maintenance: Defaulting to Field Service (FSL) without justification. A Batch Apex or Scheduled Flow is often more cost-effective for these specific requirements.
Ignoring Geolocation: Not using Geolocation fields and the DISTANCE() formula in SOQL for the proximity-based depot logic.
Weak Asset Lifecycle: No clear status transitions (e.g., Available -> Booked -> Installed -> Maintenance -> Retired).
Missing “Daily Rate” Logic: Not explaining how assembly fees (one-time) and daily rates (recurring) are calculated on the Quote or Order.

Strong Patterns

LWC-Driven Availability: Using a custom LWC on the Opportunity/Quote to query Assets based on Depot__c and Status__c, sorted by proximity using the DISTANCE formula.
External Image Offloading: Storing high-resolution site inspection photos in S3 or Azure (via AppExchange tools like X-File Pro) to manage the massive image data volume.
Record Type-Driven Orders: Using distinct Order record types for “Installation/Assembly” vs. “Procurement” to separate business processes.

Strategic Insights

The “Fit for Purpose” Test: Constructus probes an architect’s ability to choose between a heavyweight solution (FSL) and a simpler custom implementation.
Multi-National Rollout: Operating in the UK, Switzerland, and the EU requires a CoE model that addresses local compliance, multi-currency (with Advanced Currency Management), and GDPR.

Date Notes

CTAGOF lists this scenario as Jan 2021.
CTA202’s current public page is dated 2024-12-26.
The strongest public mock-board post was published 2021-02-21.

Additional Notes

This is a good example of a scenario with both an original release signal and a later republication signal.

Always verify against official Salesforce documentation

This content is study material for CTA exam preparation. Content compiled and presented with AI assistance. Not affiliated with Salesforce.

Personal study notes for the Salesforce CTA exam. Content compiled from VJ's study notes, official Salesforce documentation, community sources, and online publicly available content, then organized and presented with AI assistance. Not affiliated with Salesforce. © 2025–2026 VJ Srivastava.