When a business process does not require immediate confirmation from a target system, the architecture can move from a synchronous Request-Reply pattern to an asynchronous Fire-and-Forget pattern. In this transition, the most critical "non-functional" requirement for the Integration Architect is to define acceptable latency.

Latency determines the technical stack. If the fulfillment system must receive the order within seconds (Near Real-Time), the architect might choose Salesforce Outbound Messaging or a Flow-triggered Platform Event. If the order only needs to arrive within 4-12 hours, a Batch ETL process is more efficient as it conserves API limits and can handle much higher volumes more reliably.

While address validation (Option B) is a functional requirement, it does not define the architectural framework. Option C is a specific solution implementation question rather than a fundamental design constraint. By asking about latency, the architect identifies the time boundary between "Data Entry" in Salesforce and "Processing" in the fulfillment system. This answer directly informs the choice of pattern, the retry logic required, and the error-handling strategy needed to ensure the "Order-to-Cash" cycle is completed successfully without blocking the sales rep's productivity.

When an integration callout initiated from a Lightning Web Component (LWC) fails, the architect must distinguish between client-side and server-side security layers. Unlike Apex callouts, which are governed by Remote Site Settings at the server level, LWC requests originate directly from the user's browser. Consequently, they are subject to the browser's Content Security Policy (CSP).

CSP is a security layer that helps detect and mitigate certain types of attacks, including Cross-Site Scripting (XSS) and data injection attacks. It prevents a website from loading content from a third party unless that domain is explicitly safe-listed. If an LWC attempts to connect to an external API endpoint that is not listed in the CSP Trusted Sites in Salesforce Setup, the browser will block the request before it is even sent, often returning a "Refused to connect because it violates the document's Content Security Policy" error. While Cross-Origin Resource Sharing (CORS) is also a browser-level security mechanism, it must be configured on the external server to allow the browser to access its resources; however, the first validation step within the Salesforce environment for a failing LWC callout is ensuring the domain is allowed by the org's CSP.

When recommending Platform Events, an architect must account for the metadata lifecycle and the permanence of administrative actions. Unlike standard or custom objects, which can often be recovered from the Recycle Bin for a limited time, Platform Event definitions are handled with stricter permanence. Once a Platform Event definition is deleted, it is permanently removed from the organization's metadata, and it cannot be restored. This deletion also immediately invalidates any associated triggers, subscriptions, and stored events in the bus.

Beyond metadata management, the architect must consider the Event Retention window. High-volume platform events are stored for 72 hours, allowing subscribers to use a Replay ID to recover missed messages. However, this durability is predicated on the definition existing; if the definition is deleted, the historical data in the bus becomes inaccessible. Option A refers to Real-Time Event Monitoring, which is a separate product feature used for security auditing rather than general integration. Option B describes a specific system event (AssetTokenEvent) used for IoT device authentication, which is a niche use case and not a general consideration for platform event architecture. Therefore, understanding the permanent nature of metadata deletion is a fundamental "Maintenance" and "Governance" consideration that the architect must highlight to ensure the stability of the enterprise's event-driven landscape.