Software Testing

 In previous article we learnt about Azure Monitoring and Azure Health Service. In this article, we will be covering few fundamentals such as Economies of Scale, Capital Expenditure vs Operational Expenditure. This might be the last article in the series of Azure Tutorials Series for the preparation of Az-900, we might cover few practice papers as well which will give you exposure to the real time scenarios where Azure fundamentals comes in handy. Economies of Scale As the company grows in size, they can decrease price per unit for their customers.  Concept of buying in more quantities at lower cost, power of volume. Core principle being when the customer buys the service, he/she has to pay more than what Azure does it to them, the same service can be bought in good rate. Capital Expenditure(CapEx) vs Operational Expenditure(OpEx) Capital Expenditure requires upfront cost on infrastructure. It is an investment in on-premises. The value of infrastructure is such that it degrades with t

 In previous article we learnt about Azure Policies and Blueprints, In this article we will learn about Monitoring concepts in Azure, services like Azure Service Health and Azure Monitor. Monitoring in Azure Continuous monitoring of your applications and resources and keeping a log. Centralised repository to correlate events from multiple resources. One stop solution for collecting, analysing and tracking the progress and performance. Enhances availability, performance and security of the resources Provides visual graphics of the statistics. Can be integrated with other tools such as Power BI. Performs  Analysis Visualisation Insights Response Azure Monitor is a central dashboard where you can run queries, view graphs and create alerts for certain events. Azure Service Health  Is like a doctor which assesses your body first after which it provides you a medical subscription. Azure Service Health does the same, it provides you the health status of Azure Automatic pop-ups appears and war

 In previous article we learnt about Azure Encryption, Key Value, Azure Storage Encryption and lot of other related terms. In this article we will learn about Azure Policy, Difference between Azure Policy and RBAC, How to create a policy, Azure Blueprints, Azure Blueprints vs Azure Resource Manager Templates and lastly Azure Blueprints versus Azure Policy.  Azure Policy & Azure Blueprints Ensure whether the standards are maintained and followed. Azure Policy Enforces rules or policies for specified or all resources Makes sure all existing resources follows it and all the new deployment shall also follow it Such that infrastructure remains compliant, for an example, all the virtual machines in your organization has 8 GB RAM at least, or even allows to select the location of the resources. Can immediately deny the creation of a new resource if it is non-compliant with the policy. Can stop the update of old resource if it is against the policy. Azure Policy can add restrictions on Sto

 In Previous article, we covered Azure Identity Management, different user roles, Azure AD tenant and lot of other topics. In this article, we will be covering concepts of Encryption in Azure. Encryption in Azure Encryption of data such that no unauthorised person can read it. Data has to be decrypted to understand Encryption Types Symmetric Encryption - Requires the same key to encrypt and decrypt the data Asymmetric Encryption - uses a pair of public and private key such that one key can perform a single task at a given time. Encryption Ways Encryption at Rest - Data stored in server disk, database or storage account. Encryption in Transit - Data actively moving from one location to another Encryption on Azure We have below encryption for different services For raw storages - Azure Storage Service Encryption For Virtual machine disks - Azure Disk Encryption For Databases - Transparent Data Encryption(TDE) For Secrets- Azure Key vault We will learn about these 4 services and its e

 In previous article we learnt about Azure securities, Let's learn about Azure Identity and access in this article. We will cover authentication, authorisation, Azure active directory(AD) and RBAC. Identity and Access Management in Azure Ability to allow roles or permissions to access limited pool of resources Azure Active Directory helps enables authorisation and authentication for the privileges. Authentication vs authorisation Authentication(AuthN)  - Verifies the identity of a person Authorization(AuthZ)  - Verifies what all priviliges user has Azure Active Directory   Called Azure AD Cloud based identity service No SLA for free tier, Standard and Premium get 99.9% Can be used stand alone or can be synced with existing on-prem active directory Services includes - Multi Factor Authentication Single sign on Application Management Business to Business(B2B) identity services Business to customer(B2C) identity services Device Management Roles in Azure Roles in Azure are categorised

In previous article, we shared the concepts of networking and learnt about Azure load balancing, Azure Traffic Manager, DNS and other concepts. In this article, we will learn about security threats to Azure and how it deals to tackle it. Azure Security Attackers always have a good eye on the data breach Azure provides layer by layer protection to protect the security Confidentiality, Integrity and availability are the fundamental pillars of security Allows endpoint encryption for virtual machines Using networking to allow limited authorised traffic Anti DDoS attack configuration. Uses firewalls to identify and alert malicious attack on your network Provides IAM roles, RBAC for identity verification and access controls Uses Single-Sign-on and multi factor authentication Some of the way to increase the security of traditional systems are longer and more complex passwords Allow employees to log in with company registered devices Use MFA which requires to verify the identity Change passwor

In previous article, we have gone through Azure Networking and terminologies used while deciding a network. In this article, we will learn about load balancing, Azure application gateway, Content Delivery network, DNS, Azure traffic manager, network latency and difference between Azure traffic manager and load balancer. Azure Load Balancing Provides high availability with an SLA of 99.999% Highly resilient - An ability to stay operational during catastrophic times such as natural disasters, DDoS attacks. The function of load balancer is to equally distribute the traffic, as if high traffic comes in, it distributes among other peers. Azure Load Balancer Provides low latency - Ability of a computer network to process a very high volume of data messages with minimal latency(delay) Supports TCP and UDP applications Allows port forwarding  Let's suppose, one VM is unresponsive, Azure Load Balancer will route the traffic to the pool of other VMs. Azure Application Gateway Recommended to

I started this blog on 28th June 2019 when everything was normal. People were busy catching up their routines or job meetings, when masks were not seen at all, only people wore it to avoid polluted streets. In one year of accomplishment I have written about 93 articles. I still lag with the content quality and that is to be improved but it keeps me going and reading more stuff and sharing it here. It has become more of a journal to me. To be honest I didn't even know how 1 year went by so quickly, I feel like I am yet to learn more and share more content here. But when I look back it gives me a relief and smile that I started doing and following something. I started with IELTS, learning about working on the vocabulary and grammar structure. Then I shifted writing about Agile methodologies and principles. Later I shifted to Java, Selenium concepts - The tutorials series started and keep going till date. Java and Azure series has been really good and I have covered lot of topics from

In this article, we will learn about Azure networking concepts such as architecture, microservices, virtual networks, VPNs, subnet, VPN gateways and most importantly Network Security Group(NSG). All these terms are to be understood if you appearing for AZ900 Microsoft Azure Fundamentals exam. Azure Networking In previous articles we have learnt about Micro- services and how they work, these are alos loosely coupled architecture. Some of the features includes Independent components interact with each other with the help of queues Can be updated and deployed independently Highly scalable Supports Asynchronous messaging N-tier Architecture Supports loosely coupled architecture Application divided into multiple tiers such that higher tier can access lower tier but not vice versa Tiers are re-usable and can be updated or replaced easily without any hassle. Three-tier in general Web Tier(front end) Application tier(back end) Data tier(Storage) Virtual Network Isolated network shared by few g