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 60

Question 590

An administrator wants to recover an app from before an accidental release. Which administrative action most directly meets the requirement?

  1. Configure supported App Service backup schedule and eligible storage location.
  2. Renew the scoped SAS or eligible backup authentication and rerun backup validation.
  3. Configure the database's own backup integration/policy rather than assume all external data is included.
  4. Restore an appropriate available backup point into a safe target slot or app.

Explanation

Correct Answer

D:

An accidental release requires returning app content or settings to a known good recovery point. Select an existing supported App Service backup and restore to an appropriate safe app or slot first, validating the site and separately protected databases before any production cutover.

Incorrect Answers

A:

An App Service backup schedule stores eligible restore points; it doesn't fix an expired backup SAS or restore an old backup by itself.

B:

Renewing SAS credentials reauthorizes a backup destination but does not schedule backups or select a restore point.

C:

A database-specific backup is important if the web application relies on external data, but that does not restore application code and content from before an accidental release. Use an available compatible App Service recovery point and restore to a safe target for validation, then coordinate any separate database restoration if required.

Question 591

In October 2026, a company configures a NEW scheduled custom backup for its .NET Azure App Service website. The web app uses an independent Azure SQL Database, and the new App Service backup configuration does not offer the historical option to include that linked SQL database. The company needs recoverable database state to a point in time within its compliance retention, in addition to web app files. What is the correct protection plan?

  1. Restore yesterday’s App Service app-content backup and assume that the unrelated Azure SQL Database automatically rolls back to the same point in time.
  2. Upgrade the App Service plan to a higher tier so that the removed linked SQL database checkbox becomes available in all new custom-backup configurations.
  3. Use Azure SQL Database native automated backups with correctly configured PITR retention and test restoration, with LTR if required; protect App Service content separately instead of relying on the removed linked-database backup option.
  4. Rotate the App Service custom backup storage SAS and leave Azure SQL Database protection unspecified; a valid app-backup destination automatically copies all linked database data.

Explanation

Correct Answer

C:

Azure SQL Database automatically captures service-managed full, differential and transaction-log backups and supports point-in-time restore within the configured PITR retention. Check retention against the requested recovery horizon, configure native long-term retention separately if required, and perform a supported restore test. Microsoft removed new linked SQL database selection from App Service custom backups in April 2026; web app content and SQL data thus need separately verified recovery paths.

Incorrect Answers

A:

Restoring an App Service custom backup brings back supported app content and selected configuration, not the independent Azure SQL Database’s full transaction-log recovery chain. The database must have its own native PITR retention and tested recovery. Restoring web content alone does not satisfy the explicit database recovery objective.

B:

In April 2026 Microsoft began removing the ability to add Azure SQL/SQL Server linked databases to newly configured App Service custom backups, as part of their March 31, 2028 linked-database retirement. A higher hosting tier does not reverse that new-backup feature removal. Configure native Azure SQL Database protection and keep app-content backup separate.

D:

An App Service custom backup uses a supported storage destination, but fixing destination SAS permissions does not enroll the linked Azure SQL Database in native database backup or restore its transaction log. The missing database coverage is a workload-boundary issue, not a failed upload authorization issue.

Question 592

An App Service app on a supported paid tier has an existing scheduled CUSTOM backup that stores downloadable ZIP files in an Azure Storage container. Jobs succeeded last week but now fail with an authentication error because the configured destination SAS has expired. The storage account and app are healthy, and the company must keep using this built-in custom-backup feature. Which response corrects the documented authorization mechanism?

  1. Upgrade the App Service pricing tier or switch to a different runtime stack; the expired storage SAS will then automatically renew without updating the backup configuration.
  2. Renew or replace the time-limited, appropriately scoped storage SAS with permissions required for custom backup writes, update the App Service custom-backup destination configuration, and run a validation backup.
  3. Assign the App Service managed identity Storage Blob Data Contributor and delete the expired SAS; App Service CUSTOM backup uses that identity automatically instead of a SAS.
  4. Restore a prior app snapshot and change the App Service database connection string; neither operation renews destination storage authorization.

Explanation

Correct Answer

B:

Microsoft documents that App Service custom backups to the customer-selected Azure Storage account require SAS-based authorization; managed identity is not supported for this backup/restore destination. Renew a valid least-scope SAS with appropriate expiry and required container write/create capabilities, update the backup configuration and run a test backup to confirm access. The case is not a schedule or pricing-tier problem.

Incorrect Answers

A:

A supported App Service tier and working application stack do not regenerate an expired Azure Storage shared access signature. The previously successful custom backups establish feature eligibility; the identified failure is destination authorization. Renew the supported SAS rather than changing hosting capacity.

C:

Storage Blob Data Contributor on a managed identity could authorize some other Blob clients, but Microsoft explicitly does NOT support managed-identity-based storage account authentication for App Service custom backup and restore operations. Leaving the expired SAS in place would not repair the configured backup destination.

D:

Restoring application code or adjusting a database connection string does not provide storage destination permission for the custom-backup job. The platform must be authorized by its supported SAS mechanism to write a new ZIP backup; use a renewed suitable SAS and verify by running a supported test job.

Question 593

A web app is hosted on the Free F1 App Service plan, and its owner requires the built-in scheduled custom backup feature. How should the hosting limitation be addressed?

  1. Renew a storage SAS and expect Free F1 to gain paid backup features.
  2. Enable scheduled custom backup in F1 without any plan change because all tiers expose the same backup capabilities.
  3. Upgrade to a supported Basic-or-higher tier or implement a separately approved backup method.
  4. Mark an application setting as deployment-slot sticky; that enables scheduled backups even on Free.

Explanation

Correct Answer

C:

Microsoft documents backup support beginning at eligible Basic and higher tiers; otherwise a separate supported protection architecture is required.

Incorrect Answers

A:

Changing an access token does not add a backup capability that the current hosting tier lacks.

B:

Built-in App Service backup features require a supported pricing tier; Free plans cannot provide the stated built-in feature.

D:

Deployment-slot setting stickiness does not change plan entitlements for scheduled custom backups.

Question 594

App Service app app-invoice is hosted on a compatible Premium plan and must initiate outbound TCP connections to an Azure SQL Database private endpoint in vnet-data. The endpoint is Approved, and app-invoice is not yet VNet-integrated. The SQL public endpoint is disabled. Which TWO configurations enable the supported private outbound path? Select TWO answers.

  1. Create a private endpoint for app-invoice itself and disable its public inbound endpoint; that controls how users reach the web app, not its outbound SQL traffic.
  2. Enable the Azure SQL public network endpoint temporarily because private SQL cannot be called from App Service.
  3. Make sql-invoice.database.windows.net resolve to the SQL private endpoint IP through the appropriate private DNS zone and client VNet DNS path.
  4. Place an Azure load balancer public frontend in front of the SQL private endpoint to translate its private address.
  5. Enable App Service regional VNet integration using a suitable delegated subnet that can reach the SQL private endpoint.

Explanation

Correct Answers

C:

The application should retain the standard SQL logical-server hostname, while the private DNS configuration resolves that name to the approved endpoint private IP for integrated clients. Link the appropriate privatelink.database.windows.net zone to the client VNet or provide a supported conditional resolver path. A public result when the service public endpoint is disabled would prevent the intended private connection even if regional VNet integration were enabled.

E:

Regional VNet integration assigns the App Service worker outbound access into the selected integration subnet so it can reach reachable private IP destinations, including SQL private endpoints in that or an appropriately connected VNet. Use a supported plan and delegated subnet, validate NSGs/routes and confirm SQL DNS resolves privately from the app. Integration is an outbound feature and does not itself create inbound private app access; the case does not require that feature.

Incorrect Answers

A:

An App Service private endpoint controls inbound client access to the web application. It does not put the app worker’s outbound connections into vnet-data or create DNS resolution for the SQL endpoint. The question specifically concerns app-initiated connections from the web app to SQL. Regional VNet integration, paired with the SQL endpoint DNS path, is the relevant outbound mechanism.

B:

Azure SQL Database can be reached through an approved private endpoint using appropriate VNet connectivity and name resolution. Reenabling public access would defeat the stated private-only design and does not configure the app worker’s virtual network path. Fix the outbound VNet integration and private SQL DNS mapping without reintroducing public database exposure.

D:

A public load balancer frontend would expose a new ingress target and does not substitute for DNS records pointing to the SQL Private Link address. Azure SQL private endpoints already present supported private connectivity. The missing pieces are the App Service outbound network integration and correct DNS, not a public load-balancing layer.

Question 595

A public App Service API must accept inbound requests only from its existing corporate reverse proxy with a stable public IPv4 range. Which administrative action most directly meets the requirement?

  1. Configure App Service access restrictions to allow the proxy addresses and deny other public clients, without requiring a private endpoint.
  2. Enable regional VNet integration for outbound traffic and configure routing/DNS.
  3. Inspect subnet, route, firewall and DNS resolution before granting role privileges.
  4. Disable the public App Service endpoint and require the corporate reverse proxy to use a private endpoint even though it has no private network connection.

Explanation

Correct Answer

A:

App Service access restrictions filter requests to the public endpoint by source IP, priority and unmatched action. Allow the corporate reverse proxy's stable public addresses, and explicitly deny unmatched clients where necessary. This keeps the API publicly addressed but limits which proxy sources may reach it; verify both the main app and separate SCM endpoint requirements.

Incorrect Answers

B:

Regional VNet integration provides an App Service app a path for outbound calls into a virtual network or routed destinations. It does not, by itself, restrict which external public source addresses may send inbound requests to the app's default endpoint.

C:

Checking subnet routes, firewalls and DNS is appropriate for an outbound VNet connection failure. The stated issue is limiting inbound public API access to a known proxy IP range, so this diagnostic activity will not add the required public-endpoint access policy.

D:

Private endpoints introduce a separate private ingress path and its own DNS and network controls. They are not required when the corporate reverse proxy already has stable public IPs and the API can remain on its public endpoint with correctly scoped App Service access restrictions.

Question 596

An App Service administrator enables VNet integration and claims this AUTOMATICALLY makes the public web app inaccessible from the internet. Which explanation is accurate?

  1. VNet integration is an inbound-only private endpoint and always disables public traffic.
  2. VNet integration primarily enables outbound connectivity; inbound private endpoints and access restrictions are configured separately.
  3. VNet integration automatically migrates the app into a private Azure VM subnet and disables all public DNS records.
  4. Every storage service endpoint automatically denies the App Service public frontend.

Explanation

Correct Answer

B:

App Service distinguishes outbound VNet integration from inbound Private Link and IP/access restrictions.

Incorrect Answers

A:

VNet integration is not an inbound-only endpoint; it provides application outbound network reachability.

C:

App Service remains a managed service; integration does not relocate its public frontend into a customer subnet.

D:

Service endpoints do not automatically disable the App Service app’s internet-facing endpoint.

Question 597

An App Service app must receive HTTPS requests only through private IPs from connected VNets, using Azure Private Link. Which component is required?

  1. Enable App Service VNet integration alone, leaving inbound traffic public.
  2. Create an App Service private endpoint with private DNS resolution and restrict public network ingress as required.
  3. Configure a storage account private endpoint instead of the web app’s endpoint.
  4. Change only the web app managed identity assignment.

Explanation

Correct Answer

B:

An App Service private endpoint provides a VNet private IP for inbound requests, with DNS and public ingress policy completed separately.

Incorrect Answers

A:

VNet integration solves outbound app-to-network access and does not create an inbound private web app interface.

C:

A private endpoint on storage protects storage traffic, not the App Service hostname.

D:

Managed identity governs authorization to resources and does not create a network ingress endpoint.

Question 598

After enabling App Service regional VNet integration, an app resolves an internal backend hostname to an unexpected public address and cannot connect. What should be investigated?

  1. Create a private endpoint for the web app’s INBOUND clients and ignore the backend DNS resolution.
  2. Scale up the App Service plan without checking the network path.
  3. Review outbound VNet integration routes, the configured DNS resolver/private zone, NSGs and backend firewall.
  4. Grant the app the Subscription Owner role so all network firewalls are bypassed.

Explanation

Correct Answer

C:

Outbound private connectivity depends on correct integrated subnet, private DNS resolution, effective routes and security rules.

Incorrect Answers

A:

An inbound App Service private endpoint does not by itself fix an outbound backend name-resolution error.

B:

Additional CPU/memory cannot repair incorrect private hostname resolution or blocked routing.

D:

Azure management RBAC cannot bypass DNS or network controls on a TCP connection.

Question 599

A production App Service web app needs a separately testable, pre-warmed build before promotion with minimal client disruption. What deployment workflow should be used?

  1. Overwrite the production site directly before running any tests.
  2. Create a duplicate resource group name without deploying an app.
  3. Change only the custom domain CNAME to an empty endpoint.
  4. Deploy to an eligible staging deployment slot, validate its health, then swap to production.

Explanation

Correct Answer

D:

Deployment slots permit a staging app to warm/validate before the swap moves the vetted version into the production slot.

Incorrect Answers

A:

Direct overwrite exposes untested content to production visitors immediately.

B:

Resource groups do not themselves host or prewarm an application.

C:

DNS pointing to no healthy app breaks clients rather than safely releasing a build.

Question 600

A connection string in a production App Service slot must retain its production value when staging code is swapped into production. What setting prevents the value moving with code?

  1. Put the connection string into a public source-control README.
  2. Clear the connection string from both slots before the swap.
  3. Mark the connection string as a Deployment slot setting (sticky) on the applicable slots.
  4. Increase the staging slot worker count only.

Explanation

Correct Answer

C:

Deployment slot settings stay with the specified slot rather than swapping with the application content.

Incorrect Answers

A:

Publishing a secret in a README exposes it and does not control App Service slot swapping.

B:

Deleting secrets prevents the application from authenticating after rollout.

D:

Worker instance count affects capacity and is not the application-setting stickiness control.