Planning data management (17 percent)

  • Plan data caching and persistence strategy. It may include but is not limited to:
    • retrieve data from disparate data sources (XML data, flat files, and relational databases, manage class-generated data, LINQ),
    • manage bulk imports and exports (ETL, data transformation),
    • choose appropriate data access layer,
    • manage data purity (re-validate data across trust boundaries),
    • manage data asynchronously,
    • leverage synchronization services,
    • connection management
  • Select a data storage mechanism. It may include but is not limited to:
    • managing data cache,
    • managing data persistence (storing disconnected scenarios, managing offline data),
    • mapping database to local cache (loading all customers locally),
    • managing data state
  • Plan application data sharing. It may include but is not limited to:
    • security,
    • target data engine,
    • target environment (workstation capabilities, OS, bandwidth, domain vs. workgroup, connectivity, reliability)
  • Design a schema evolution management strategy. It may include but is not limited to:
    • managing data shared between forms and processes,
    • managing data synchronization (ADO.NET synchronization services),
    • drag and drop files or objects from outside sources
  • Design a concurrency management strategy. It may include but is not limited to:
    • synchronizing an application with a schema
  • Plan data access strategy. It may include but is not limited to:
    • database segmentation,
    • planning for concurrency and collision avoidance,
    • optimistic vs. pessimistic
Share
Tagged with:
 

2 Responses to “Microsoft’s 70-563: Pro: Windows Applications Using .NET 3.5 Objectives List Part 2”

  1. I’ve been checking your blog for a while now, seems like everyday I learn something new :-) Thanks

Leave a Reply