Comprehensive and Detailed Explanation:
OIC's unsaved changes feature safeguards design-time work against disruptions. Let's explore each option in detail:
Option A: A user with the ServiceAdministrator role can recover the unsaved changes.
True:The ServiceAdministrator role has elevated privileges, including recovering unsaved changes from a crashed session. For example, if a developer's browser crashes mid-flow, an admin can log in, access the integration, and restore the draft. This ensures continuity in team workflows.
Option B: A user with the ServiceAdministrator role can unlock an integration that has unsaved changes.
True:If an integration is locked due to a crash (e.g., user session terminates unexpectedly), a ServiceAdministrator can unlock it, allowing recovery or further editing. This is critical in scenarios where a developer leaves an integration in a locked state.
Option C: Changes made while editing a Connections page cannot be recovered.
True:OIC's recovery mechanism doesn't extend to the Connections page. Connection edits (e.g., updating credentials) are separate from integration flows and lack the same autosave granularity. If a crash occurs here, changes are lost, requiring re-entry.
Option D: Changes made while working inside a data mapper cannot be recovered.
False (Not True):Mapper changes (e.g., mapping fields between source and target)arerecoverable. OIC autosaves mapper edits as part of the integration draft. Forinstance, if you map "OrderID" to "PurchaseID" and the browser crashes, logging back in restores this work. This makes D the incorrect statement and the answer.
Option E: A backup copy is created after each complete task, therefore there is no time limit to logging back in and recovering the changes.
True:OIC creates backups after significant actions (e.g., adding an action, saving a map). There's no strict time limit for recovery, as drafts persist until overwritten or discarded, offering flexibility post-crash.
Why D is the answer:Mapper changes are integral to integration design and covered by OIC's autosave, unlike Connection edits (C). D's claim contradicts this capability.
Use Case Example:A developer mapping a complex payload in an ERP-to-CRM sync recovers their work after a network drop, proving mapper recovery works.

Comprehensive and Detailed Explanation:
REST trigger config:
A:True-standard (e.g., Content-Type) and custom headers are supported for request/response.
B:False-attachments are possible in responses too.
C:False-response format isn't mandatory for PUT/POST.

Comprehensive and Detailed Explanation:
Scheduled Parameters:
C:True-override at runtime is simplest.

Creating two separate configuration plans for each environment is the best practice. This keeps environment-specific details separate from the SOA archive and promotes reusability and maintainability. Other methods are error-prone or inefficient.

A: IoT integrates various technologies like mobile, cloud, and big data to connect devices.
B: Cloud platforms provide scalable and cost-effective infrastructure for IoT.
C: IoT applications extend beyond hospitality, making this statement less universally true.
D: IoT is valuable in asset tracking due to the availability of low-cost sensors.