70-534 Practice Test Questions Answers

1
Architecting Azure Solutions Microsoft
2
Azure Storage Overview70-534

• Architecting Microsoft Azure Solutions

3
Two Part Presentation
4
Introducing Azure Storage
5
Cloud Application Requirements

• Durable and highly available
• Scalable and performant
• Multiple concurrent users
• Secure
• Manageable
• Time to market

https//www.pass4sureexam.com/70-534.html
6
Introducing Microsoft Azure Storage

• Cloud Storage - Anywhere and anytime access
• Blobs, Disks, Tables, Queues and Files
• Highly Durable, Available and Massively Scalable
• Easily build Internet scale applications
• More than 35 trillion stored objects
• 3.5 Million requests/sec on average
• Pay only for what you use
• Exposed via easy and open REST APIs
• Rich Client Libraries and Tools

https//www.pass4sureexam.com/70-534.html
7
17 Regions Worldwide in 2015
8
Abstractions Blobs

• Blobs Massively scalable object store in the
  cloud
• Simple REST interface (Put, Get, Delete)
• Data sharing share documents, pictures, video,
  music, etc.
• Big Data store raw data/logs and compute/map
  reduce over data
• Backups data and device backups

9
Abstractions Disks

• Persistent disks for VMs in Azure 
• Disks are VHDs stored in Azure Page Blobs
• Page blobs are optimized for random I/O
• VM see the VHD/Blob as a disk
• Reads translated to GETs, writes to PUTs
• Blob protected by write-lease
• Reads from the blob (and snapshots) still allowed

10
Breaking News Premium Storage

• Consistent low latency SSD based with predictable
  IO throughput
• Suitable for high-performance IO-intensive
  database workloads
• Single digit milliseconds latencies
• Supports up to 1 TB blob/disk size
• Stripe up to 32 disks for a total of
• 32TB and more than 50,000 IOPS
• Premium Storage Disks work in
• conjunction with a new VM series

11
Abstractions Tables

• Tables Massively scalable NoSQL cloud store
• Key/Attribute(s) store at scale
• Store user, device or any type of metadata for
  your service
• Auto load balances partitions to meet traffic
  needs
• OData protocol (AtomPub or JSON)

12
Abstractions Queues

• Queues Reliable messaging system
• Reliable, low latency, high throughput messaging
  system
• Decouple components/roles
• Web role to worker role communication
• Allows roles to scale independently
• Implement scheduling of asynchronous tasks
• Building process/work flows

13
Abstractions Files

• Move on-premises applications to cloud
• VMs can net use an SMB share using standard file
  APIs and semantics
• SMB 2.1 protocol
• VM and storage account within same region
• Supports REST and SMB protocol access to same
  file share

Microsoft Azure
Share data stored in Azure Files among Azure VMs
via SMB
14
Additional Services, Tools and Libraries

• Azure Import/Export
• Move TBs of data into and out of Azure Blobs by
  shipping disk
• Submit and monitor jobs via REST and Portal
• All disks encrypted with BitLocker
• Client Libraries
• Simplify interaction with REST services
• Convenience capabilities retry logic,
  parallelization, SAS tokens,
• .NET (Desktop, Phone, Windows), Java, C,
  Android, Node.JS, Python, PHP, Ruby, IOS (Coming
  Soon)
• Tools
• PowerShell commands
• CLI tools
• AzCopy 3.0 Copy blobs and disks (Tables and
  Files in Preview Release)

15
Azure Storage Architecture
Client Libraries (.NET, Java, c, Android,
Node.JS)
Import / Export
SMB Client
SMB 2.1
REST
REST
REST
REST
File Share Endpoint
Front End Layer
Massive Scale Out Auto Load Balancing Index
Layer
Partition Layer
Distributed Replication Layer
Stream Layer
Windows Azure Storage A Highly Available Cloud
Storage Service with Strong Consistency, ACM
Symposium on Operating System Principals (SOSP),
Oct. 2011
16
Platform Capabilities
17
Durability Options

• Locally Redundant Storage (LRS)
• Stores 3 replicas of the data within a single
  zone (facility) in a single region
• Provides data durability for disk, node and rack
  failures
• Geo Redundant Storage (GRS)
• Stores 6 replicas of the data across two regions
  (3 in each region)
• Provides additional durability to protect data
  against major regional natural disasters (e.g.,
  tornado, hurricane, fire, etc, destroying a
  whole region)
• Updates across regions are performed
  asynchronously
• Zone Redundant Storage (ZRS)
• Stores 3 replicas of the data across multiple
  zones (facilities) within a single region or
  across regions
• Provides additional durability to protect data
  against zone failures (e.g., fire burning down a
  facility)

https//www.pass4sureexam.com/70-534.html
18
Secondary Read-Only Access

• Customers using Geo Redundant Storage can opt to
  have read-only access to the eventually
  consistent copy of the data on Secondary tenant
• Applications control which location they read
  data from
• Primary endpoint
• accountname.ltservicegt.core.windows.net
• Secondary endpoint
• accountname-secondary.ltservicegt.core.windows.net
• Consistency
• All Writes go to the Primary
• Reads to Primary are Strongly Consistent
• Reads to Secondary are Eventually Consistent
• Our client library SDK provides features for
  reading from the secondary
• Retry options PrimaryOnly, SecondaryOnly,
  PrimaryThenSecondary, etc.

https//www.pass4sureexam.com/70-534.html
19
Access Control

• Symmetric Shared Key AuthN
• Trusted service that owns the storage accounts
• Shared Access Signature (SAS) Delegated AuthZ
• 3rd party services
• Mobile device applications
• Restricted access for services
• Allow client applications to directly communicate
  with Storage rather than scaling a proxy web
  service
• Public (Blob service only)
• CDN access
• Browser based access

https//www.pass4sureexam.com/70-534.html
20
Concurrency

• Optimistic Concurrency
• Blobs and Tables support optimistic concurrency
• Based on HTTP protocol (Etag and if-match
  conditions)
• Pessimistic Concurrency
• Blocks provide exclusive access via leases
• Enable synchronization strategies
• Exclusive write / shared read
• Exclusive write / exclusive read
• Shared write / exclusive read
• Last Writer Wins

https//www.pass4sureexam.com/70-534.html
21
Scalability Targets

• Storage Account
• Capacity Up to 500TB
• Objects per second 20,000 1KB messages
• Scans/Listing considered as the number of objects
  read by the system and not the number of objects
  returned
• Bandwidth
• GRS Up to 10 Gbps Ingress/20 Gbps Egress
• LRS Up to 20 Gbps Ingress/30 Gbps Egress
• Partition
• Table- Up to 2,000 1KB entities/sec
• Queue - Up to 2,000 1KB messages/sec
• Blob - Up to 60 MB/s, IOPS 500
• File - Up to 60 MB/s, IOPS 1000
• Check Azure Storage Scalability and Perf Targets

22
Storage Analytics

• Storage platform incorporates rich analytics
• Metrics - Monitor service health, capacity,
  availability and performance
• Logs Detailed logs of every operation to
  support troubleshooting
• Analytics is not enabled by default we
  recommend enabling
• During testing to establish baseline metrics
• In production to assist with troubleshooting
• Client libraries also enable access to metrics
  data via strongly typed objects
• Client libraries also have client side logging

23
Designing a Cloud Scale Application
24
Scale Design Principles

• Uniformly distributed traffic across the entire
  user partition namespace
• Range based partitioning does not cater to
  append/prepend pattern
• Avoid spikes
• Additional accounts to get more scale than a
  single account
• Design application to dynamically add accounts
• Throughput
• Use more simultaneous outstanding IO
• Single blob Parallel page writes or block writes
• Multiple blobs Upload blobs in parallel

https//www.pass4sureexam.com/70-534.html
25
Resilience Design Principles

• Failures can occur
• Retry on Network/Connection failures
• Exponential back-off on timeout and throttling
  failures
• Regional failures can occur
• Design for regional redundancy
• RA-GRS Allows apps to continue with read only
  access to eventual consistent data
• Network latencies can occur
• Latency sensitive apps could use cache.

https//www.pass4sureexam.com/70-534.html
26
Scenario and Requirements

• Designing a SaaS solution to deliver Incident
  Management capabilities at hyper scale
• Significant Use Cases
• CRUD operations on Incidents
• Get Incidents assigned to a User
• Architecture Requirements
• High availability (99.99 for reads)
• Scalability beyond storage account limits
• Provide direct access to storage to minimize
  complexity and cost

https//www.pass4sureexam.com/70-534.html
27
Storage Design Practices

• Use the right abstraction
• Key Lookups at scale for structured data Tables
• Scans/retrieve large amount of raw data like for
  analytics/metrics etc. Blobs
• Process workflows, decoupling applications
  Queues

https//www.pass4sureexam.com/70-534.html
28
Table Design Principles

• Design for querying
• Specify both PartitionKey and RowKey in your
  queries
• Consider storing duplicate copies of entities
  (with different keys)
• Consider denormalizing your data
• Dont create a separate table for each type of
  entity
• Use compound key values
• Avoid creating hot partitions

https//www.pass4sureexam.com/70-534.html
29
CRUD Operations

• Table storage to store incident data
• PK as Incident ID, RK as empty
• Incident ID breakdown (OrgId, bucket ID, GUID)
• Table Property backed by blob

Partition Key (Incident ID) Row Key Title (string)   AssignedTo (string)   Status (string)   Description (string)
contoso _01_8743428c-ef91-4d05-9e7c-4a2e856e813a   Support Retrieval workflow user5 Active http//storageaccount1.blob.core.windows.net/backingcontainer/01_8743428c-ef91-4d05-9e7c-4a2e856e813a
30
Get Incidents Assigned to User

• Querying Incidents data as is - Table scan not
  optimal
• Make assignedto part of the pk or rk
• Denormalize common properties to avoid hops
  Title and Status
• Use Queues to get eventual consistency
• Key Pattern Write to queue first with timeout ,
  than update primary entity
• Worker role then updates the secondary index
• DEMO

Partition Key (PropertyName_Value) Row Key (Incident ID) Title (string)   Status (string)  
AssignedTo_user5 contoso _01_8743428c-ef91-4d05-9e7c-4a2e856e813a Support Retrieval workflow Active
31
High Read Availability

• Design the solution to be resilient to local and
  geographical failures
• Solution
• Replicate data between two regions using GRS
• Read from secondary region in the event of
  failure in first region
• Client SDKs retry policy automates this with a
  configuration setting
• Enable application to run in read only mode until
  recovery/failover

https//www.pass4sureexam.com/70-534.html
32
Provide Direct Access to Storage

• Enable clients to interact directly with storage
  to remove the need for a storage proxy
  decreasing latency and reducing complexity
• Solution
• Issue SAS tokens to Clients for delegated
  authorization
• Additional benefits
• SAS tokens can restrict access to tenant specific
  data

https//www.pass4sureexam.com/70-534.html
33
Pattern Scale beyond single storage account

• Solution needs to scale beyond storage account
  limits
• Solution
• Create only as many storage accounts as needed
  today
• Keep a map of OrgId bucket id to a storage
  account name
• When a bucket id fills up or storage account
  reaches limits (capacity/throughput), create a
  new bucket id and pick a storage account from
  pool for storing data
• Helps with write availability for new incidents
  in DR scenario

Partition Key (OrgID) Row Key (bucket id/sharding Index) Storage Account (string)   IsActive (bool)
contoso 00 demo1 false
contoso 01 demo2 true
elmaramsey 00 Demo1 true
34
Architectural Sketch
P1. Register New Customer
P2.2 Lookup Shard
P2.1 Get SAS Token
P2.3 CRUD CRUD Incidents
P3. Update Indices
35
Recap

• Designing a SaaS solution to deliver Incident
  Management capabilities at hyper scale
• Design Requirements and Solutions
• Multi-tenant SAS tokens for AuthZ
• Scale across storage accounts Shard data across
  storage accounts
• Optimize resources SAS tokens enable direct
  interaction with storage
• High availability in the face of intermittent and
  regional failures
• Read access to secondary region
• Ability to create new incidents in different
  storage accounts
• Customizable incidents Tables storage
• Support different search strategies Secondary
  indexes
• Coordinate updates to tables blobs Queue
  based coordination

36
Session Objectives And Takeaways

• Session Objective(s)
• Provide an overview of the Storage platform
  abstractions and platform capabilities
• Review principles and patterns in the context of
  a real world scenario
• What differentiates us
• Strong consistency Easier for applications to
  consume
• GRS Data replicated to DC 100s of miles apart
• RA-GRS Eventual consistent access to your data
• Disks Azure Files Enables lift shift of
  applications
• Strong Development tools and libraries
• AzCopy, PowerShell, CLI, Client libraries in
  various languages

37
Resources
38
Azure Storage Resources

• Documentation
• Azure Storage Blog
• Azure Storage Documentation (Azure.com / Docs /
  Storage)
• REST and API Documentation (MSDN)
• Client Libraries
• Azure Storage Nuget
• Azure Storage Client Library Source Code
• SDKs
• Architectural Guidance (Azure.Com / Docs /
  Storage)
• Azure Storage Performance and Scalability
  Checklist
• Monitor, Diagnose and Troubleshooting
• Managing Concurrency in Azure Storage
  Applications
• Azure Table Storage Design Guide (Coming Soon)

39
Thank you

• Continue the discussion
• Storage Team Round Table
• 5pm - 630pm in room 8.11

https//www.pass4sureexam.com/70-534.html
40
For more information
Come visit us in the Microsoft Solutions
Experience (MSE)! Look for the Cloud and
Datacenter Platform area TechExpo Hall 7
41
Azure
Implementing Microsoft Azure Infrastructure
Solutions
Exams
Developing Microsoft Azure Solutions
(Coming soon) Architecting Microsoft Azure
Solutions
EXAM 532
EXAM 533
EXAM 534
http//bit.ly/Azure-Cert

Classroom training
(Coming soon) Microsoft Azure Fundamentals
MOC 10979
Implementing Microsoft Azure Infrastructure
Solutions
Developing Microsoft Azure Solutions
MOC 20532
MOC 20533
2
5
5
http//bit.ly/Azure-Train
Online training
(Coming soon) Architecting Microsoft Azure
Solutions
(Coming soon) Microsoft Azure Fundamentals
MVA
MVA
http//bit.ly/Azure-MVA
Get certified for 1/2 the price at TechEd Europe
2014!
http//bit.ly/TechEd-CertDeal
42
Resources
43
Please Complete An Evaluation FormYour input is
important!
TechEd Mobile app Phone or Tablet
QR code
TechEd Schedule Builder CommNet station or PC
44
Evaluate this session
45
https//www.pass4sureexam.com/70-534.html
2014 Microsoft Corporation. All rights
reserved. Microsoft, Windows, and other product
names are or may be registered trademarks and/or
trademarks in the U.S. and/or other
countries. The information herein is for
informational purposes only and represents the
current view of Microsoft Corporation as of the
date of this presentation. Because Microsoft
must respond to changing market conditions, it
should not be interpreted to be a commitment on
the part of Microsoft, and Microsoft cannot
guarantee the accuracy of any information
provided after the date of this presentation.
MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED
OR STATUTORY, AS TO THE INFORMATION IN THIS
PRESENTATION.
46
(No Transcript)
47
(No Transcript)
48
(No Transcript)