Which of the below is NOT a Synchronization Best Practice for mobile application?

• A. Only synchronize delta : Use control timestamps
  C Avoid long synchronization in a single transaction
• B. Sync only when strictly required
  E Don't sync on every screen or online event
• C. Do not use Entity Bulk Operation to ensure small lightweight updates
• D. Sync only when required. p At session start: sync summary data to local storage At process start: sync process detail to local storage At process/transaction end, sync back to server
• E. Only synchronize relevant data
• F. Ensure sync granularity: Prepare for constant retries without repeating work due to network loss. Sync in chunks, incremental by entity

Which of the below is NOT a suitable advice for designing a LIGHTWEIGHT mobile local storage?

• A. Group relevant information
• B. Store all records no matter if relevant or irrelevant
• C. Define only used attributes
• D. Denormalize the local storage

Of the options below, which one is a benefit of adopting the Architecture Canvas?

• A. It's a faster architecture design
• B. It's a systematic approach to architecture design
• C. It promotes the business users' collaboration and understanding
• D. It's an automatic way to find and fix architecture issues.

SSL Pinning is a security best practice for mobile application. Which of the below is FALSE about SSL Pinning?

• A. SSL Pinning does not mean hardcoding the public key into the code.
• B. SSL Pinning or HTTP Public Key Pinning (HPKP) helps reduce man-in-the-middle attacks
• C. Works on the client side and adds verification of the server certificate against hashes of public keys, which are pre-bundled with the mobile app
• D. All of the above are true

_BL module is for

• A. Logic to Synchronize data in CS's with an external system. Isolating this logic makes the CS completely system agnostic and it's easier to decouple or replace the external system.
• B. Isolated Business Logic (Actions), to manage complexity, composition or to have its own 'ifecycle.
• C. A BL becomes a Calculation Engine if it performs complex calculations, (e.g. an invoice calculation engine or an insurance simulator). Engines are usually subject to versions.
• D. Reusable Core Services with public entities, actions, and blocks.
• E. Technical wrapper to expose an API to External consumers, keeping core services system agnostic and supporting multiple versions of the API.