Pessoal, segue uma pequena lista de coisas que estudei e foram super úteis na hora de fazer a prova de certificação 70-532 de Azure.

1 – The Service Management API provides programmatic access to much of the functionality available through the Management Portal.

2 – The Resource Manager A resource group is a container that holds related resources for an application. 
 
3 – XML Storage https://msdn.microsoft.com/en-us/library/azure/ee758708.aspx
 
 
 
4 – ASP NET Stateless -> Arr-Disable-Session-Affinity = True permitirá que cada request de um cliente caia em uma máquina qualquer. Se estiver TRUE, todos os requests de um mesmo cliente caem sempre na mesma máquina. 
 
5 – Always-on -> O site é carregado na memória a primeira vez, e nunca mais é descarregado. O padrão é OFF. 
 

6 – To move a role instance to another subnet edit the CSCFG file.

 
7 – Push Notification (TOAST -> VISUAL -> BINDING -> TEMPLATE -> TEXT) var payload = ‘<?xml version=”1.0″ encoding=”utf-8”?>
<toast>
<visual>
<binding template=”ToastText01”>
 <text id=”1″>’ + item.text + ‘</text>
</binding>
</visual>
 </toast>
8 – Azure Redis Cache
Classe: ConnectionMultiplexer – ConnectionMultiplexer connection = ConnectionMultiplexer.Connect(“contoso5.redis.cache.windows.net,ssl=true,password=…”);
Limite de conexões por cache: 10.000 clientes conectados
IDatabase cache = Connection.GetDatabase();  //referência para o banco de dados do Redis Cache chamando o método ConnectionMultiplexer.GetDatabase
Inserindo dados: cache.StringSet(“key1”, “value”);
Recuperando dados: string key1 = cache.StringGet(“key1”);
9 – Blob Storage: http://justazure.com/azure-blob-storage-part-three-using-the-storage-client-library/
  • CloudStorageAccount – this is a reference to the storage account, created using the account name and key.
  • CloudBlobClient – this is a reference to the object used to perform operations on the blob storage account. This is created using the CloudStorageAccount object.
  • CloudBlobContainer – this is a reference to the container that your blobs reside in. This is used in most blob operations, and is created using the CloudBlobClient.
  • CloudBlockBlob – this is a reference to the actual blob. This is created using the CloudBlobContainer object and the name of the blob.  (If using page blobs, this would be CloudPageBlob).
  • CloudBlockBlob – Optimized for efficient upload of large blobs. They are consist of a set of blocks, each identified by a block ID. Block blobs are limited to 200 GB in size.
  • CloudPageBlob – Optimized for random read and write operations. Page blobs consist of a set of 512-byte pages and are limited to 1 TB in size.
10 – Você usa as APIs padrão de acesso a Blob e Tables quando precisa configurar o storage analytics e acessar os dados armazenados neste storage analytics

11 – Windows Azure Storage provides following options for redundancy for Blobs, Tables and Queues:

1. Locally Redundant Storage (LRS): All data in the storage account is made durable by replicating transactions synchronously to three different storage nodes within the same region. The below section will cover more details on LRS including on how to select LRS.

2. Geo Redundant Storage (GRS): This is the default option for redundancy when a storage account is created. Like LRS, transactions are replicated synchronously to three storage nodes within the primary region chosen for creating the storage account. However, the transaction is also queued for asynchronous replication to another secondary region (hundreds of miles away from the primary) where data is again made durable by replicating it to three more storage nodes there. The below section will cover in depth the asynchronous replication process, information on region pairings and the failover process.

3. Read Access – Geo Redundant Storage (RA-GRS): For a GRS storage account, we now have introduced in limited preview the ability to turn on read only access to a storage account’s data in the secondary region. Since replication to the secondary region is done asynchronously, this provides an eventual consistent version of the data to read from. The below section will cover more details on RA-GRS, how to enable this in preview mode and details on storage analytics.

12 – All startup tasks are executed according to their taskType attribute.

 

  • The simple tasks are executed synchronously, one at a time.
  • The background and foreground tasks are started asynchronously, parallel to the startup task.

Abs,

@daibert

 

 

Anúncios