You have two NSG rules: Rule A with priority 100 allowing inbound HTTP (port 80), and Rule B with priority 200 denying all inbound traffic. What happens to inbound HTTP traffic?
Remember, NSG rules are processed in order of priority from lowest number to highest.
NSG rules are evaluated by priority number, lowest first. Rule A with priority 100 allows HTTP traffic before Rule B with priority 200 denies all inbound traffic, so HTTP traffic is allowed.
You have a web tier, app tier, and database tier in separate subnets. Which NSG application strategy best limits unwanted traffic?
Think about controlling traffic flow between each tier and from outside.
Applying NSGs on all subnets allows filtering inbound and outbound traffic between tiers and from the internet, providing layered security.
Given this NSG rule JSON snippet, what is the effect on inbound traffic?
{
"name": "Deny-SSH",
"properties": {
"priority": 300,
"direction": "Inbound",
"access": "Deny",
"protocol": "Tcp",
"sourcePortRange": "*",
"destinationPortRange": "22",
"sourceAddressPrefix": "*",
"destinationAddressPrefix": "*"
}
}Check the direction, port, and access fields carefully.
The rule denies inbound TCP traffic on port 22 from any source to any destination, effectively blocking all inbound SSH connections.
You create two NSG rules with priority 100: one allows inbound HTTP, the other denies inbound HTTP. What is the outcome?
Check Azure NSG rules priority requirements.
Azure NSG requires unique priority numbers for rules. Duplicate priorities cause deployment errors.
Which statement best describes the role of NSG flow logs in Azure?
Think about what logs usually record about network traffic.
NSG flow logs record metadata about allowed and denied traffic flows, useful for troubleshooting and auditing network security.