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 71

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.

Question 701

A contractor may connect to one approved VM through an existing Azure Bastion host but must not manage the entire subscription or modify Bastion configuration. What should be granted?

  1. Subscription Owner to avoid any Bastion connection restrictions.
  2. Public inbound RDP from the internet to bypass RBAC checks.
  3. A private DNS zone Contributor role to control VM guest rights.
  4. Appropriate narrowly scoped Reader/connection permissions for Bastion, target VM/NIC and valid guest credentials, without broad resource-management rights.

Explanation

Correct Answer

D:

Bastion access can be scoped to required Azure resources while guest authentication remains separate.

Incorrect Answers

A:

Subscription Owner is excessive for one authorized VM remote session.

B:

Direct public RDP bypasses the managed Bastion security objective.

C:

Private DNS administration is not equivalent to VM/Bastion connection authorization.

Question 702

An Azure Bastion session from the portal reaches the Bastion host, but SSH to a running private Linux VM times out. The VM SSH service listens on TCP 22 and Azure Bastion is healthy. Network diagnostics show the target VM subnet NSG denies inbound TCP 22 from the AzureBastionSubnet address range; the VM has no public IP. Which change restores the approved Bastion connection without exposing SSH publicly?

  1. Add an inbound NSG Allow for TCP 22 from Internet and assign a public IP to the target VM.
  2. Allow inbound TCP 22 from AzureBastionSubnet on the target VM effective NSG path, while retaining a functioning guest SSH listener.
  3. Change only AzureBastionSubnet inbound TCP 443 browser access because the portal cannot reach Bastion.
  4. Add an outbound TCP 3389 Allow from the Linux VM to the user browser to repair the Bastion SSH path.

Explanation

Correct Answer

B:

Bastion originates the target SSH connection from AzureBastionSubnet, so the destination subnet/NIC NSG must allow the required TCP 22 flow. With Bastion already reachable and SSH listening, this precisely removes the observed network deny.

Incorrect Answers

A:

Exposing SSH from the public Internet is unnecessary and violates the requirement for private-only administration. Bastion connects to the VM over its private address, not by assigning a public IP to the target.

C:

The portal can already reach the Bastion host, so its client-facing HTTPS port is not the failing hop. The diagnosed block is the separate Bastion-subnet-to-VM TCP 22 path, which the target NSG filters.

D:

RDP uses TCP 3389 and is not the SSH service on this Linux VM. An outbound rule from the target to a browser reverses the direction and addresses the wrong protocol for Bastion-initiated private SSH.

Question 703

An IT organization has Azure Bastion in HubNet and target VMs in a directly peered SpokeNet. Does every spoke need its own Bastion host?

  1. Yes, cross-VNet Bastion access is never supported.
  2. Yes, unless every spoke VM has a separate public IP.
  3. Only if the VM uses an availability set.
  4. No. A supported Bastion deployment can reach private VMs in peered VNets when routing, permissions and NSGs permit.

Explanation

Correct Answer

D:

Central Bastion with appropriate peering is a supported hub-and-spoke access design.

Incorrect Answers

A:

Azure Bastion supports connections to targets in properly configured peered networks.

B:

A public IP on the target VM is not required for Bastion private connectivity.

C:

Availability-set membership does not force one Bastion per VNet.

Question 704

An administrator must use Azure Bastion native client and custom RDP port capabilities, but the current Bastion SKU omits those features. What is the correct next step?

  1. Enable anonymous container registry pulls and keep the same Bastion SKU.
  2. Check the feature/SKU matrix and upgrade to a supported Bastion Standard-or-higher tier for custom ports and applicable native-client features.
  3. Increase VM guest RAM to enable Bastion advanced features.
  4. Rename AzureBastionSubnet to AppSubnet and try again.

Explanation

Correct Answer

B:

Bastion features are SKU-gated; selecting an eligible tier is required for unsupported advanced access modes.

Incorrect Answers

A:

Container registry access has no bearing on Bastion feature entitlements.

C:

VM memory cannot activate features missing from a Bastion host tier.

D:

Bastion dedicated subnet naming is a deployment requirement, not a tier-upgrade substitute.

Question 705

A team deploys dedicated Azure Bastion but places it in an ordinary application subnet with a /28 prefix. What subnet prerequisite must be corrected?

  1. Add a public DNS CNAME for the application subnet and retain /28.
  2. Create or use dedicated `AzureBastionSubnet` with a supported /26-or-larger address range and required NSG configuration.
  3. Remove all VM NSGs so Bastion can deploy into the arbitrary subnet.
  4. Move the Bastion host to a Storage Blob container instead of a subnet.

Explanation

Correct Answer

B:

Dedicated Bastion deployments require AzureBastionSubnet with sufficient addresses and compatible network policies.

Incorrect Answers

A:

A DNS alias cannot replace Bastion’s dedicated subnet capacity/name requirement.

C:

Deleting target VM NSGs does not make a /28 application subnet an eligible Bastion subnet.

D:

Blob containers store data, not Bastion managed gateway network resources.

Question 706

A regulated organization wants private VM administration through Bastion, with recorded remote sessions for audit and no direct public SSH/RDP exposure on target VMs. Which deployment feature is required?

  1. Use Azure Bastion Premium session recording with secure storage/auditing and appropriate VM/subnet NSG controls.
  2. Publish TCP 22 and 3389 on every VM public IP, then record only browser history.
  3. Use Bastion Developer SKU and assume it includes Premium session recording.
  4. Change the Recovery Services vault redundancy to enable RDP recording.

Explanation

Correct Answer

A:

Azure Bastion Premium offers session recording and managed private VM access; permissions and logs must be configured.

Incorrect Answers

B:

Exposing management ports publicly violates the private-VM requirement and browser history is not full session recording.

C:

Developer tier lacks Premium session recording capabilities.

D:

Backup vault storage redundancy has no relationship to Bastion session capture.

Question 707

An existing Azure Bastion Standard deployment has Shareable Link enabled for approved VM users. An administrator tries to create a shareable link for a VM in a VNet that is peered to the Bastion VNet, but the two VNets belong to different Microsoft Entra tenants. Ordinary cross-tenant VNet peering is authorized. What documented Bastion feature limitation explains why the proposed shareable link path is unsupported?

  1. All Azure VNet peering across different Entra tenants is impossible, so the VNet peering itself must be deleted.
  2. Bastion Shareable Link does not support peered virtual networks across tenants, even when ordinary authorized VNet peering is established.
  3. Bastion Shareable Link contains the guest OS password inside the URL, and tenant boundaries prevent Azure from decrypting that embedded password.
  4. Shareable Link is only available for Azure Files shares; it has no support for Azure VMs or VM scale sets in any tenant.

Explanation

Correct Answer

B:

Microsoft documents that Bastion Shareable Links are not supported for peered VNets across tenants. Use a supported VM placement/connectivity design or a separate authorized connection method; do not assume working cross-tenant peering makes this link feature supported.

Incorrect Answers

A:

Microsoft allows VNet peering between subscriptions in different Microsoft Entra tenants when authorized; the presence of cross-tenant peering does not itself invalidate ordinary private networking. The limitation here is specific to Bastion Shareable Link.

C:

Shareable Links do not contain login credentials. A user opening a link must authenticate to the target VM or scale set with the permitted guest credentials or key. The limitation is topology/tenant support, not encrypted passwords inside the link.

D:

Shareable Links provide Bastion browser access to supported Azure VMs and VM scale sets without requiring Azure portal sign-in. They are not an Azure Files-only capability.

Question 708

Virtual machines in subnet `app-subnet` already access an approved Azure Resource Manager-based Blob storage account through a Microsoft.Storage service endpoint. The storage firewall allows that subnet, and security requires preventing these VMs from accessing any other storage account through Storage service endpoints. No classic storage account is involved, and the design must keep the public service-endpoint model instead of Private Link. Which TWO changes create the intended outbound destination restriction? Select TWO answers.

  1. Use an outbound NSG rule with the Storage service tag and assume the tag matches only the one approved storage account.
  2. Add the subnet to the allowed storage account firewall a second time and assume that inbound destination rule blocks requests to all other Storage accounts.
  3. Create a Microsoft.Storage service endpoint policy definition that lists the approved ARM storage account resource ID as an allowed destination.
  4. Associate the service endpoint policy with app-subnet while keeping the Microsoft.Storage service endpoint enabled.
  5. Add an Azure Policy Deny definition for creating storage accounts, assuming it filters subsequent packets to already-existing Storage accounts.

Explanation

Correct Answers

C:

A Storage service endpoint policy definition supports Azure Resource Manager storage account IDs as allowlisted destinations. This is one required component of egress filtering; Microsoft documents that classic storage accounts cannot be allowed by these policies, so the case explicitly uses ARM-based storage.

D:

The policy definition must be associated with the source subnet to apply to its service-endpoint traffic. Because the endpoint is already enabled, binding the policy with the approved destination list completes the subnet-side restriction while ordinary storage firewall and authorization checks still apply.

Incorrect Answers

A:

An NSG service tag covers Azure service IP address prefixes, not the resource identity of a single storage account. It cannot enforce a one-account egress allowlist over Storage service endpoints, even when the destination subnet is restricted.

B:

The approved account’s firewall decides which sources may reach that destination; it cannot prevent the same VM from accessing other storage accounts. Repeating an already-present inbound network rule does not constrain the client subnet’s outbound set of destinations.

E:

Azure Policy can prevent or audit resource management operations, but does not serve as an egress firewall for data requests to existing accounts. The service endpoint policy, rather than a resource-creation policy, evaluates the destination account for this traffic.

Question 709

A storage account permits only selected virtual networks. Subnet subnet-api already has the Microsoft.Storage service endpoint enabled, and the VM can resolve the storage public endpoint. Storage access still returns a network-level 403 because subnet-api does not appear in the storage account's virtual network firewall rules. Which specific setting must be added?

  1. Assign Storage Blob Data Contributor to the VM identity but leave the storage firewall unchanged.
  2. Disable and reenable the already working Microsoft.Storage service endpoint without editing storage account rules.
  3. Add subnet-api as an allowed virtual network/subnet rule in the storage account's Networking settings.
  4. Generate a new SAS token because SAS authorization always overrides selected-network firewall restrictions.

Explanation

Correct Answer

C:

For a storage account with public network access restricted to selected virtual networks, Azure Storage needs an account-side virtual network rule authorizing the origin subnet. The Microsoft.Storage service endpoint already identifies subnet-api traffic on the source side, but it does not automatically grant access through a destination firewall. Add subnet-api to the storage account's virtual network allowlist, then retest while retaining normal identity or SAS authorization. This repairs the precise denied-network condition without opening the entire storage account publicly or changing unrelated RBAC grants.

Incorrect Answers

A:

Blob data RBAC roles authorize what an authenticated principal can do after the storage account's network gate admits the request. The failure in this case is explicitly traced to a missing subnet rule in a selected-network firewall. Additional blob permissions cannot create a virtual-network allowlist entry or force Azure Storage to accept traffic from a disallowed subnet.

B:

The service endpoint is already present on subnet-api and DNS resolves the intended public service endpoint. Cycling that endpoint cannot add the corresponding storage account firewall allow rule. Microsoft describes the subnet-side endpoint and resource-side virtual network rules as separate settings, both required for this selected-network model. The omitted storage network rule must be added at the destination account.

D:

A shared access signature controls access scope and lifetime for certain storage data requests; it is not an exemption from storage account network access rules. If the request comes from a network the selected-network firewall denies, replacing an otherwise valid SAS will not make the source subnet allowed. This case specifically provides a network 403 and an absent virtual network rule, so fix that network rule first.

Question 710

An engineer enabled the Microsoft.Storage service endpoint on subnet app-subnet and added that subnet to a storage firewall allowlist. The storage endpoint still resolves to an Azure public service IP. Security now requires clients to connect through a private IP address allocated inside the VNet. Which design change meets that stricter network requirement?

  1. Create an appropriate Storage private endpoint and private DNS mapping; service endpoints alone do not assign a private IP to the PaaS endpoint.
  2. Keep only the existing service endpoint and update a subnet NSG with the Storage service tag, which forces public DNS to return a private address.
  3. Assign a public IPv4 address to the VNet subnet so the storage account endpoint will automatically become a private-IP listener.
  4. Change storage redundancy to geo-zone-redundant storage and assume the storage FQDN then resolves to the VNet gateway address.

Explanation

Correct Answer

A:

Azure service endpoints extend VNet identity to supported Azure PaaS services while the service endpoint retains public service IP addressing. A private endpoint is the mechanism that presents an approved service subresource at a private IP on a NIC in the selected VNet. The administrator should create that connection, configure relevant private DNS resolution, and validate the allowed route before closing unwanted public access paths. Service endpoint firewall rules alone do not satisfy the new private-address requirement.

Incorrect Answers

B:

NSGs and service tags can influence allowed traffic, but they cannot transform a storage service public endpoint into a VNet private IP. The service endpoint remains a supported network identity/routing approach using service public addresses. Private Link and private DNS are required for a private endpoint design.

C:

Allocating a public IP address to another resource does not cause an Azure Storage service FQDN to resolve to a private IP. Storage is a platform service with its own endpoint. A private endpoint must be created and approved for the relevant Storage service subresource.

D:

Storage redundancy protects data across infrastructure locations; it does not determine whether clients address a private endpoint or a public Storage service IP. GZRS can be appropriate for availability, but it cannot reconfigure a VNet DNS response into a private network interface.