mcAfee Secure Website
23

Microsoft AZ-104 Bundle

Exam Code: AZ-104

Exam Name Microsoft Azure Administrator

Certification Provider: Microsoft

Corresponding Certification: Microsoft Certified: Azure Administrator Associate

AZ-104 Training Materials $44.99

Reliable & Actual Study Materials for AZ-104 Exam Success

The Latest AZ-104 Exam Questions as Experienced in the Actual Test!

  • 24
    Questions & Answers

    AZ-104 Questions & Answers

    606 Questions & Answers

    Includes questions types found on actual exam such as drag and drop, simulation, type in, and fill in the blank.

  • 25
    AZ-104 Video Course

    AZ-104 Training Course

    132 Video Lectures

    Based on Real Life Scenarios which you will encounter in exam and learn by working with real equipment.

  • exam =30
    Study Guide

    AZ-104 Study Guide

    458 PDF Pages

    Study Guide developed by industry experts who have written exams in the past. They are technology-specific IT certification researchers with at least a decade of experience at Fortune 500 companies.

exam =32

Microsoft Azure Administrator (AZ-104) Practice Tests

Guarantee

Satisfaction Guaranteed

Pass4sure has a remarkable Microsoft Candidate Success record. We're confident of our products and provide no hassle product exchange. That's how confident we are!

99.3% Pass Rate
Total Cost: $194.97
Bundle Price: $149.98

Purchase Individually

  • exam =34
    Questions & Answers

    Questions & Answers

    606 Questions

    $124.99
    exam =35
  • exam =37
    AZ-104 Video Course

    Training Course

    132 Video Lectures

    $39.99
  • exam =36
    Study Guide

    Study Guide

    458 PDF Pages

    $29.99

Microsoft AZ-104 Practice Test 70

Question 690

An Azure VM is reattached from subnet `admin` to subnet `isolated` with no guest OS, SSH daemon, source IP or credentials change. Subnet `isolated` has a different NSG from `admin`. The same management client can no longer establish SSH over TCP/22, and the administrator must diagnose the network-policy difference before changing rules. What is the most targeted first check?

  1. Inspect the old `admin` subnet NSG only; subnet-level NSGs remain inherited by a NIC even after it is attached to another subnet.
  2. Check only the NIC’s directly associated NSG and ignore subnet-level rules, because the NIC NSG always overrides an inherited subnet Deny.
  3. Add an inbound Allow on the NIC NSG immediately and assume it takes precedence over any blocking rule on `isolated`.
  4. Inspect the VM NIC’s effective inbound security rules, including the new subnet NSG and any NIC NSG, for TCP/22; check effective routing if those rules allow it.

Explanation

Correct Answer

D:

The effective security rules for the NIC aggregate the subnet- and NIC-associated inbound NSG rules. Checking the TCP/22 flow and its source/destination constraints isolates the policy introduced by the move; if permitted, verifying effective routes is the appropriate next diagnostic.

Incorrect Answers

A:

Moving a NIC to `isolated` changes which subnet-level NSG applies; Azure does not keep inheriting `admin` subnet rules after the move. Reviewing only the old association misses the likely new cause of the SSH failure.

B:

Azure evaluates both subnet and NIC network security groups where both apply. A NIC-level Allow cannot universally override a matching Deny at the subnet layer, so ignoring the new subnet is unsafe.

C:

Adding a NIC Allow without identifying the current denial may be ineffective if the new subnet has a restrictive inbound rule. The case explicitly requests diagnosis before altering production network policy.

Question 691

A firewall review finds a custom NSG rule with source Any, destination Any and all destination ports, but the requirement permits only database TCP 1433 from AppSubnet. What should be changed?

  1. Give the NSG resource a more restrictive display name.
  2. Replace the wildcard rule with source AppSubnet and database destination/port/protocol restrictions.
  3. Set the storage account minimum TLS version to 1.2 as the only fix.
  4. Remove all logging and keep the broad network allow.

Explanation

Correct Answer

B:

An explicit source range and TCP port/destination scope implements least privilege for the stated database flow.

Incorrect Answers

A:

Rule names do not change source/destination match behavior.

C:

Storage TLS policy does not restrict generic VM-to-database NSG traffic by prefix.

D:

Removing logs does not narrow the overly permissive rule.

Question 692

An NSG rule changed from Allow to Deny, but an existing established TCP session continues briefly. New connections are denied. Which explanation fits?

  1. An NSG must be a resource-group Owner to apply new deny rules.
  2. Changing DNS TTL can clear the stateful session record.
  3. NSGs are stateful; established flows can persist until their flow records close while new connections match the updated rules.
  4. Azure peering automatically overrides all NSG rule changes.

Explanation

Correct Answer

C:

Existing tracked flows and newly initiated flows can behave differently after an NSG rule update.

Incorrect Answers

A:

Azure RBAC authority is not the mechanism behind differences between old and new connections once a rule is applied.

B:

DNS cache settings cannot evict NSG per-flow state for an existing TCP connection.

D:

Peering routes connectivity but does not bypass stateful NSG evaluation.

Question 693

VM `app01` in subnet `sn-app` opens TCP/8443 toward VM `api01` in subnet `sn-api` of the same Azure VNet. The source NIC and sn-app outbound effective NSG rules ALLOW this destination and port; Network Watcher shows a valid VNet route. The destination sn-api subnet NSG has a higher-priority inbound DENY for TCP/8443 from sn-app, and no NIC rule can override that subnet deny. Security authorizes HTTPS-alt traffic only from sn-app to api01, not a broad all-source allow. What network-rule action resolves this specific flow without weakening unrelated access?

  1. Add another outbound allow on app01 with an even smaller priority number, leaving sn-api's matching inbound deny unchanged.
  2. Enable VNet peering gateway transit between sn-app and sn-api, even though both subnets are in the same VNet and routing already works.
  3. Remove the destination subnet route table without changing its NSG; routing changes automatically neutralize higher-priority inbound deny rules.
  4. Inspect both source outbound and destination inbound effective rules, then add an approved source/port-specific inbound allow at higher priority than the matching sn-api deny.

Explanation

Correct Answer

D:

Azure checks outbound NSG controls at the source and inbound NSG controls at the destination, including applicable NIC/subnet associations. An authorized narrow inbound allow with priority preceding the broad 8443 deny can permit exactly this approved source-to-API flow without exposing the port to all VNet clients.

Incorrect Answers

A:

The source outbound path is already permitted. A second source rule cannot override the destination subnet's independently enforced inbound DENY on the same 8443 flow, even if the source rule has higher precedence locally.

B:

Gateway transit is for peered virtual networks and their virtual network gateways, not private traffic between subnets inside one VNet. The identified blocker is the destination inbound NSG, not the route topology.

C:

An NSG deny is evaluated as a packet-filter rule; removing an unrelated route table neither deletes the rule nor creates a matching inbound allow. The VM already has a valid path, so routing is not the failing layer.

Question 694

NSG nsg-app already has an inbound allow rule at priority 250. A second inbound rule for an unrelated TCP destination is submitted using priority 250 and Azure rejects it as a duplicate. The administrator must retain both rules and preserve their ordering. What should be changed?

  1. Move the second rule to outbound direction but leave its source and destination fields unchanged.
  2. Assign the new inbound rule a distinct unused priority within the valid NSG custom-rule range, preserving the intended match order.
  3. Keep both inbound rules at 250 and change only their display names so the priority check is bypassed.
  4. Delete the default NSG deny rules before adding the second custom inbound rule at priority 250.

Explanation

Correct Answer

B:

Each security-rule priority must be unique within the applicable NSG rule collection, and lower numbers are evaluated before higher numbers. By choosing an unused valid value, the administrator retains both inbound rules while defining the intended order. The correct choice requires checking existing rules rather than blindly using the next integer, since another rule might already occupy that slot. The rule’s protocol, destination and allowed source should remain aligned with the original requirement.

Incorrect Answers

A:

Inbound and outbound rules are evaluated in different directions. Moving an inbound rule to outbound would stop it from matching the intended incoming TCP packets, even though the numeric priority might then be accepted. The requirement is to preserve two distinct inbound controls and their ordering.

C:

Azure does not use a security rule’s display name as a substitute for a unique priority. Two rules in the same NSG direction cannot reuse an occupied custom priority simply by having different names. The request would continue to fail its validation and would not establish deterministic processing.

D:

Default NSG rules have their own reserved priorities and remain part of the evaluation model. Deleting them is neither the supported way to make duplicate custom priorities legal nor a safe way to preserve intended traffic control. Resolve the conflict among custom inbound priority values instead.

Question 695

An Azure VM's subnet NSG contains a matching inbound Allow TCP/22 rule at priority 100. However, Azure Virtual Network Manager has already deployed a security admin rule with action Deny for that same inbound SSH flow to the VM's managed VNet, and no exemption applies. The VM remains unreachable. Which explanation and next administrative action are correct?

  1. The subnet NSG's priority-100 Allow wins because NSG priorities are always evaluated before centrally managed security rules.
  2. Adding a lower-numbered Allow TCP/22 rule to the NIC NSG overrides the deployed Azure Virtual Network Manager Deny rule.
  3. The centrally deployed security admin Deny is evaluated before NSGs and blocks the flow; an authorized central admin must change the security admin policy or scope if SSH is approved.
  4. Grant the VM operator subscription Owner so the RBAC assignment exempts their SSH packets from Azure Virtual Network Manager filtering.

Explanation

Correct Answer

C:

Security admin Deny blocks the matching flow before NSG evaluation, even if an NSG allows it. The centrally authorized network governance team must modify its deployed rule or authorized exception scope; merely editing a local NSG will not unblock the traffic.

Incorrect Answers

A:

Azure Virtual Network Manager security admin rules are evaluated before subnet/NIC NSGs. An NSG Allow rule is not examined once a matching security admin Deny terminates the packet evaluation.

B:

A NIC NSG rule is also evaluated after security admin rules. Its priority number cannot override a higher-precedence security admin Deny already enforced at the VNet level.

D:

Azure RBAC grants administrative control-plane permissions but does not exempt packets from deployed network security admin rules. A broader subscription role would not change the SSH flow's Deny decision.

Question 696

A security engineer needs Azure-portal browser-based RDP to a private-only Windows VM that has NO public IP. Which Azure access service can provide the managed connection?

  1. Allow anonymous HTTPS on a storage account in the VM resource group.
  2. Deploy a supported Azure Bastion host and use its portal-based VM connection with approved network/RBAC and guest credentials.
  3. Create a public IP on the VM and open RDP 3389 to Any.
  4. Turn on VM managed-disk encryption, which also creates a browser terminal.

Explanation

Correct Answer

B:

Azure Bastion can proxy portal RDP/SSH to private VMs without assigning an internet public IP to the VM.

Incorrect Answers

A:

Anonymous storage reads do not provide Windows RDP management access.

C:

The proposed direct public exposure contradicts the requirement to keep the VM private-only.

D:

Disk encryption secures data at rest and does not provide a remote desktop gateway.

Question 697

Azure Bastion Standard is already deployed and its browser session opens successfully. The Windows VM has no public IP, is running, and accepts RDP locally on TCP 3389. A diagnostic shows the target VM subnet's NSG denies inbound TCP 3389 from AzureBastionSubnet 10.40.0.0/26 at a higher priority than any allow rule. What narrowly scoped network change will restore Bastion-to-VM sessions?

  1. Add an effective VM-subnet inbound allow rule for TCP 3389 from 10.40.0.0/26, ahead of the matching deny.
  2. Allow inbound TCP 3389 from Internet to the VM subnet so browser clients can connect directly to the VM.
  3. Allow inbound RDP from Internet to AzureBastionSubnet because all Bastion browser clients connect on TCP 3389.
  4. Upgrade the Bastion SKU while leaving the target VM subnet's explicit deny rule in place.

Explanation

Correct Answer

A:

Azure Bastion establishes the private RDP connection to the VM from the AzureBastionSubnet address range. The browser-to-Bastion leg is already working, the VM listens on 3389, and the diagnostic identifies the VM subnet's explicit higher-priority block. Add the narrow TCP 3389 inbound allow from 10.40.0.0/26 to the target NSG with a priority that wins over the deny. Verify effective NSG rules afterward. This restores only the expected Bastion source path and does not expose the VM's management port to the public internet.

Incorrect Answers

B:

Opening RDP from the entire Internet expands the VM subnet's attack surface and violates the private-management design. Bastion clients use an HTTPS browser connection to the Bastion service; the service then talks privately to the VM. The identified problem is a deny on VM-side inbound traffic from AzureBastionSubnet, not lack of internet reachability to the VM. A public allow would be both excessive and potentially still shadowed by the earlier deny.

C:

Standard portal-based Azure Bastion connections use HTTPS on port 443 for the client-facing leg, rather than a public RDP listener on AzureBastionSubnet. The failing leg here is Bastion-to-VM over the private subnet and target NSG. Opening inbound 3389 from Internet to the Bastion subnet would target the wrong interface and create an unnecessary exposure without removing the VM subnet's deny.

D:

A different Bastion SKU does not override the target VM subnet's NSG evaluation. The Bastion service and browser connection already work; the only supplied blocked element is a higher-priority deny for traffic from the Bastion subnet to Windows RDP. Upgrading costs more and leaves that rule in place, so the same RDP connection would remain denied unless the effective VM-side NSG permissions changed.

Question 698

A developer must access exactly one Azure test VM in a region where Azure Bastion Developer SKU is available. The environment does not require concurrent sessions, virtual-network peering, native clients, production-grade availability, or a dedicated Bastion deployment. Which Azure Bastion SKU fits this limited development requirement?

  1. Azure Bastion Developer SKU, recognizing its single-VM-at-a-time and no-VNet-peering limitations.
  2. Azure Bastion Premium private-only SKU is required for every test VM even when no private-only deployment was requested.
  3. Azure Bastion Basic, because Developer SKU always requires a public IP on the target VM and cannot connect to a private test VM.
  4. Any SKU with VNet peering enabled, because Developer SKU supports peered virtual networks and unlimited concurrent sessions.

Explanation

Correct Answer

A:

Microsoft positions Bastion Developer for supported dev/test environments at no SKU charge, with a one-VM-at-a-time limitation and no VNet-peering support. Those constraints match this single test VM and its limited connectivity needs.

Incorrect Answers

B:

Premium supports additional features including private-only Bastion and session recording, but none is required by the specified one-VM dev/test scenario. Requiring Premium would solve a more demanding case at unnecessary complexity.

C:

Bastion is designed to connect to VMs using private addresses without requiring the target VM to expose public RDP/SSH. The Developer tier is a shared development option in supported regions, not inherently prohibited for the stated target.

D:

Developer SKU does not support VNet peering or multiple concurrent VM connections. Choosing it on the assumption of those capabilities would fail the explicitly unsupported cases, which the question excludes.

Question 699

A user can view an Azure Bastion host but cannot open an RDP session to a Windows VM. What two authorization boundaries must be verified?

  1. Only the VM public DNS label and storage account SAS.
  2. Only the Azure resource-group tag named Administrator.
  3. Only the Azure private DNS zone link with no guest sign-in.
  4. Appropriate Azure Bastion/VM permissions and network reachability, plus valid guest Windows sign-in credentials or supported Entra sign-in.

Explanation

Correct Answer

D:

Bastion authorization and reachability are separate from authenticating to the VM operating system.

Incorrect Answers

A:

DNS labels and SAS tokens cannot grant Bastion portal access or Windows logon rights.

B:

Azure tags are not a replacement for Bastion access rights.

C:

Private DNS alone cannot authorize the administrative session at either the Azure or guest identity layer.

Question 700

An operations team administers VM payroll01 by RDP and VM api01 by SSH directly over their existing public NIC IPs. Company policy now prohibits Internet-exposed management ports but requires administrators to retain browser-based management from the Azure portal through a supported Bastion deployment. Which TWO changes satisfy the requirement? Select TWO answers.

  1. Remove the unneeded VM public management IPs and Internet RDP/SSH allow rules, validating that no required unrelated service depends on them.
  2. Provision an approved Azure Bastion host in its correctly sized dedicated subnet and use Bastion connections to the VMs over private IPs.
  3. Install a second public SSH listener on api01 and use an obscured TCP port rather than stopping Internet access.
  4. Enable an Azure Policy exemption for all VMs, which makes existing public RDP/SSH traffic private.
  5. Publish the VM private IPs as public DNS A records and leave their inbound management NSG rules unchanged.

Explanation

Correct Answers

A:

Removing direct public management exposure closes the forbidden Internet RDP/SSH path. Confirm that each public NIC address serves no unrelated approved function before removal and restrict any network security group rules that otherwise still allow those management ports from the Internet. This change is separate from providing an alternative management path; Azure Bastion allows administrators to connect through private VM addresses after the public exposure is removed.

B:

Azure Bastion provides supported RDP and SSH connectivity to Azure VMs without requiring the VMs themselves to have public management IPs. Deploy it with the required dedicated AzureBastionSubnet and supported configuration, confirm routing and access authorization, and connect from the portal to the VMs’ private IPs. Bastion is the replacement administration path; merely removing public access without it could strand operators, so both selected changes are needed to satisfy the complete requirement.

Incorrect Answers

C:

Changing SSH to a nonstandard public port does not remove Internet-facing remote administration. Public attackers can still reach a listening SSH service, and the organization explicitly prohibits Internet-exposed management access. The supported replacement uses a private VM path through Bastion and closes the original exposed endpoints rather than relying on port obscurity.

D:

An Azure Policy exemption affects how a policy assignment evaluates designated resources; it does not change public IP assignments or network security group packet filtering. Exempting the VMs would neither close their existing management ports nor create an alternative secure admin path. The policy objective remains unmet.

E:

Publishing private-address hostnames in public DNS does not make RDP or SSH private. The VM still has its public NIC endpoint and permissive network policy unless those are removed or restricted. Public DNS is a naming mechanism, not a Bastion tunnel or management-port firewall. Use the private Bastion path and explicitly eliminate unwanted public exposure.