Thursday, September 7, 2017

AZURE 70-534 Exam Notes and Cheat Sheet -Part 4 (Design Advance Azure Application )

Quick Summary 

Primary objective of this page is to summarize key data points of all the security option available to Azure Infrastructure as per AZURE 70-534 Exam Objective IV (Design Advance Azure Application). Use this page as quick refresher or Cheat Sheet but no way a replacement of actual exam study guide or course 

This Post is part of multi-part series and I will keep posting other part as it progress

High Performance Computing (HPC)

  1. HPC Option in Azure 
    1. HPC Pack (On Premise)
    2. HPC Pack Hybrid 
    3. HPC Pack IAAS 
    4. Azure Batch 
  2. Compute Intensive VM Series
    1. A9, A10, A11 are HPC compute VM 
      1.  Support Netwok Intensive application 
      2. Support Windows and Linux both
    2.  A8, A9 instances support RDMA
      1. allow Remote Direct Memory Access 
      2. VM are connected by low latency high throughput network 
      3. Very much suitable for Message Passing Application  
    3. Scaling in not possible in between Non Compute and Compute Optimized Instance and visa Versa
  3. Azure Batch
    1. It is fully managed HPC in cloud 
    2. Auto scale based on compute demand 
    3. Light Weight REST Interface 
    4. can be used by any cloud application to run schedule job 
    5. Azure media services are built on top of it 
    6. Support User management, Quota , Budget, Analytics, and Client Plug-In
    7. Provide Batch SDK that can be used to build Job Execution Pipeline 
    8. Key Concepts 
      1. Creates a separate batch account
      2. Create a Task Virtual Machine 
      3. Create Pool of TVMs 
        1. Pool Can be resized as required 
        2. Different pool can be based on different user profile 
      4. Work Item - How jobs run in TVM pool 
      5. Task - Steps to complete job
      6. File - Input Data for Task
        1. Uploaded to Azure Storage
        2. Azure Batch transfer to TVM for processing 
      7. Batch App- manage, run and monitor repetitive batch jobs 
      8. Batch Application - Name of repeatable batch job 
      9. Application Image - a Zip file containing application executable and support file 
      10. Cloud Assembally - Zip File that includes 
        1. Method to break jobs in  to task 
        2. Method to invoke application executable 

Create Long Running Application

  1. Web Jobs 
    1. Supported by Web App and Process on same machine good for short term asynchronous jobs 
  2. Worker Roles 
    1. It is managed execution environment for long running task that do not required direct input 
    2. Azure handles most of infrastructure and task runs in asynchronous mode
    3. Used an alternative of HCP for for compute intensive tasks
    4. Worker roles can be deployed either via console or visual studio 
    5. Run on PAAS VM (Rather IAAS VM)
    6. Scale as per demand.
    7. Limited RDP is supported diagnostics and trouble shooting 
    8. Worker Role Vs WebJobs 
      1. Worker Role is processed on separate VM
      2. Web jobs are processed on same machine where WebApps are deployed so not suitable for compute intensive jobs
      3. Worker role can scale independent of Web Roles

Designing Azure Storage Option for Advance Compute 

  1. Hybrid Data Connection Option
    1. Express Route 
    2. Service Bus relay 
    3. BizTalk Hybrid Connection Manager 
    4. VPN
  2. Consideration for Storage Selection 
    1. Storage Performance Option 
      1. TBD 
    2. Storage Concurrency
      1.  Last Write Wins 
      2. Optimistic
      3. Pessimistic 
  3. Queue Selection Consideration 
    1. Azure Queue 
      1. Simple REST Based interface 
      2. Reliable Persistent messaging 
      3. Use case 
        1. App needs to store 80 GB plus message with max 7 days lifespan 
        2. Need to track progress of message inside queue  
        3. Need server side logs of all transaction against queue 
    2. Service Bus Queue 
      1. it is like ESB 
      2. Support Queuing 
      3. Support Publish Subscribe 
      4. Web service Remoting 
      5. Support Integration Patterns 
      6. Use case 
        1. When you need pub/sub  mechanism 
        2. Ordered Delivery 
        3. Duplication detection 
        4. Message Stream Implementation 
        5. TTL more than 7 Days 
        6. Message > 64 KB to 256 KB
        7. role based model and access 
        8.  Queue size is less then 80 GB
        9. Want to use AMPQ message broker 
        10. Guaranteed non duplicate ordered delivery is required 
        11. required message batching 
        12. Need to Publish and consume message in batches 
        13. Need Full WCF stack Integration 
      7. Azure Service Bus Queue Vs Azure Queue 
        1. TBD
      8. Queue Design Patters 
        1. Competing Consumer 
        2. Priority Queue 
        3. Queue based Load Leveling 
        4. Ref https://docs.microsoft.com/en-us/azure/architecture/patterns/
    3. SQL Server Selection Consideations
      1. https://docs.microsoft.com/en-us/azure/sql-database/sql-database-paas-vs-sql-server-iaas

Integrating Azure Services

  1. Machine Learning (ML)
    1. Data is loaded to machine learning using multiple ways 
    2. Data can directly be published from application running in Azure 
    3. ML Studio is IDE to interact with data
    4. Result are exposed via API 
    5. it can run Script in R and Python 
    6. Provide rebuild algorithm to get started 
    7. Market place has several machine learning solution available 
  2. Big Data (HD Insights )
    1. provide two clustors 
      1. Hadoop
      2. Apache Spark 
      3. HDase 
      4. Apache Storm
  3. Azure Media Services 
    1. TBD
  4. Azure Search 
    1. Custom Tuning is supported 
    2. Search Keys are used to access services 
    3. Primary and Secondary admin key is support 
    4. Also support search query key for read only access 

No comments:

Post a Comment