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 59

Question 580

An application needs managed certificate renewal for a supported custom domain. Which administrative action most directly meets the requirement?

  1. Enable HTTPS Only along with certificate and TLS binding requirements.
  2. Configure hostname binding and DNS ownership before expecting HTTPS to work.
  3. Bind the certificate to the App Service custom host and enable appropriate TLS settings.
  4. Evaluate App Service managed certificate eligibility and automate renewal monitoring.

Explanation

Correct Answer

D:

An App Service managed certificate must be supported for the app and verified hostname. Validate eligibility and hostname binding, then monitor certificate state and renewal behavior so the custom domain keeps a valid TLS binding; a generic minimum-TLS setting does not renew a certificate.

Incorrect Answers

A:

Enforcing HTTPS Only redirects HTTP requests once a valid HTTPS configuration exists. It does not determine whether an App Service managed certificate is supported for the custom domain or manage its renewal. Review managed-certificate eligibility and current binding/renewal conditions instead of using an HTTP redirect as a renewal mechanism.

B:

Custom hostname binding and DNS verification identify the host; they do not install a working certificate or enforce TLS policy by themselves.

C:

Binding a valid certificate to a custom hostname enables HTTPS traffic but is distinct from a managed certificate lifecycle. It does not by itself establish App Service managed certificate eligibility or verify that automated renewal will succeed for the requested hostname.

Question 581

An app's TLS certificate is valid but the domain isn't mapped to the web app. Which Azure configuration or procedure is the best fit?

  1. Enforce minimum TLS 1.2+ as supported and update incompatible clients.
  2. Configure hostname binding and DNS ownership before expecting HTTPS to work.
  3. Enable HTTPS Only along with certificate and TLS binding requirements.
  4. Evaluate App Service managed certificate eligibility and automate renewal monitoring.

Explanation

Correct Answer

B:

A valid certificate alone does not make App Service recognize or route traffic for an unbound custom hostname. Add and validate domain ownership and the hostname binding, then associate the certificate with that hostname so HTTPS requests resolve to the intended app.

Incorrect Answers

A:

Minimum TLS version restricts negotiated protocols; it doesn't create a valid domain, certificate binding or backup configuration.

C:

HTTPS Only redirects incoming HTTP requests to HTTPS once the app's HTTPS endpoint is properly configured. It doesn't map an unregistered hostname or prove domain ownership. A valid certificate alone is insufficient until the custom hostname is added to App Service with the correct DNS validation and hostname/TLS binding.

D:

Managed certificates have eligibility limits and renewal behavior; selecting one does not replace domain verification or make a missing hostname binding valid.

Question 582

A legacy browser uses an outdated TLS protocol no longer permitted. What should the administrator do to resolve this specific case?

  1. Configure hostname binding and DNS ownership before expecting HTTPS to work.
  2. Bind the certificate to the App Service custom host and enable appropriate TLS settings.
  3. Enable HTTPS Only along with certificate and TLS binding requirements.
  4. Enforce minimum TLS 1.2+ as supported and update incompatible clients.

Explanation

Correct Answer

D:

App Service's minimum incoming TLS setting rejects clients offering only protocols below the configured minimum. Keep a supported TLS minimum (at least TLS 1.2 where required) and update legacy clients rather than weakening the security baseline to accept their obsolete handshakes.

Incorrect Answers

A:

Custom hostname DNS ownership establishes where clients connect, but it cannot upgrade the TLS protocol supported by a legacy browser. The secure response is to retain an approved App Service minimum TLS version and update or replace the incompatible client.

B:

Binding a certificate to a custom App Service hostname establishes server identity for HTTPS, but it cannot make a client that only supports a disallowed TLS protocol negotiate successfully. Enforce the supported minimum TLS version and require affected browsers or client libraries to upgrade; do not weaken security merely to maintain obsolete clients.

C:

HTTPS Only redirects HTTP traffic to HTTPS; it cannot substitute for a valid hostname certificate or DNS mapping.

Question 583

An App Service website already has a valid HTTPS certificate and hostname binding. Security now requires any incoming HTTP request to be redirected to HTTPS automatically. Which built-in App Service setting addresses this?

  1. Add a new deployment slot without changing HTTP transport settings.
  2. Add a second certificate but leave the app HTTP endpoint accepting plaintext requests without redirect.
  3. Enable the App Service HTTPS Only option for the web app.
  4. Add an Azure Files share as content storage to force secure web requests.

Explanation

Correct Answer

C:

HTTPS Only instructs App Service to redirect requests to HTTPS for the already correctly bound web hostname.

Incorrect Answers

A:

Deployment slots control staged releases, not transport-level HTTP to HTTPS redirection.

B:

Certificate installation enables TLS but does not itself redirect clients arriving over unsecured HTTP.

D:

File share mounting does not alter inbound web request scheme enforcement.

Question 584

The DNS team manages example.com and requires a CNAME rather than an A record for the www subdomain. Its target is an existing App Service app app-news.azurewebsites.net, but www.example.com has not yet been bound or ownership-verified in the app. Which TWO actions complete the requested subdomain mapping? Select TWO answers.

  1. Create an A record for the apex example.com and assume it also maps www automatically.
  2. Validate control of www.example.com using the App Service domain-verification procedure and add its custom host-name binding.
  3. Point www.example.com to a public IP address in a CNAME record rather than to a DNS hostname.
  4. Create a www CNAME in the public DNS zone targeting app-news.azurewebsites.net.
  5. Enable minimum TLS 1.2 on the existing app without changing DNS or adding the custom hostname.

Explanation

Correct Answers

B:

App Service must know that the custom hostname belongs to the intended app. The operator should follow the portal’s domain ownership verification flow, typically using the supplied asuid TXT verification value, and then add the custom domain binding after DNS validation. Without a valid hostname binding, traffic reaching the App Service platform cannot be confidently routed to the target app for this host. This step is separate from the public CNAME that resolves the hostname.

D:

For a custom App Service subdomain, a CNAME whose target is the app’s default azurewebsites.net hostname establishes the public DNS mapping without hard-coding its frontend IP. With www.example.com pointing at app-news.azurewebsites.net, DNS clients resolve the application’s current platform endpoint. This is distinct from adding the corresponding custom host binding and ownership proof in App Service. Both the DNS record and binding are needed for the intended hostname to work reliably.

Incorrect Answers

A:

An apex A record applies to example.com itself, not automatically to www.example.com. The requirement is explicitly for the www host and the DNS team has chosen CNAME mapping for that subdomain. Creating an unrelated apex record would leave www unresolved or pointed elsewhere and would not establish ownership or an App Service hostname binding.

C:

A CNAME record aliases one DNS name to another DNS name; its target cannot be a raw IPv4 address. Attempting this would be invalid DNS configuration and would not follow the approved mapping design. The App Service default hostname is the supported CNAME target for the requested www subdomain, and domain ownership still needs to be verified in App Service.

E:

Enforcing a TLS version is an independent HTTPS security setting and does not tell public DNS where www.example.com should resolve. It also does not establish ownership or the custom hostname binding for that name. TLS configuration can be reviewed later, after the DNS-to-App-Service mapping exists; it cannot substitute for the two requested domain operations.

Question 585

An organization maps the DNS apex `example.org` (not `www.example.org`) to an Azure App Service custom domain. Its DNS provider prohibits CNAME at the zone apex. What record strategy fits the apex?

  1. Publish a supported apex A record to the app inbound IP, or provider-supported flattened ALIAS/ANAME, and complete App Service ownership validation.
  2. Put a literal CNAME at the apex even though the DNS provider and zone standard prohibit it.
  3. Create only a public MX mail record and assume browsers use it for web navigation.
  4. Link the public apex DNS zone to an Azure VNet as a private zone instead of creating public records.

Explanation

Correct Answer

A:

Apex hostnames normally use A records for Azure App Service, with some DNS providers supporting an ALIAS/ANAME-style equivalent plus validation.

Incorrect Answers

B:

An ordinary apex CNAME conflicts with the provider constraint and usual DNS zone apex records, so it cannot be the required answer.

C:

MX records route mail delivery and do not map an HTTPS web hostname to App Service.

D:

Azure private DNS VNet links are not substitutes for publicly delegated authoritative records for an internet-facing apex site.

Question 586

A marketing web app runs on a paid Azure App Service tier. New regional subdomains such as eu.example.com and apac.example.com should all resolve to the app without creating an individual DNS record for each region. The public example.com DNS zone is under the company’s control. Which supported DNS and App Service configuration meets this requirement?

  1. Add an apex CNAME at example.com and assume that all unknown subdomains automatically inherit it.
  2. Create a wildcard CNAME record named *.example.com that targets the app’s default azurewebsites.net hostname, then validate ownership and add the matching wildcard custom hostname to App Service.
  3. Create a linked Azure Private DNS zone for example.com and expect arbitrary public Internet clients to resolve it without public DNS records.
  4. Upload a wildcard TLS certificate but configure neither a wildcard DNS record nor an App Service custom-hostname binding.

Explanation

Correct Answer

B:

Microsoft documents wildcard public subdomains for App Service with a wildcard CNAME pointing to the default app hostname. The application must also validate domain control and accept a matching wildcard custom-hostname binding; DNS alone does not configure hostname admission.

Incorrect Answers

A:

An apex alias would not automatically map every subdomain. In addition, the zone apex cannot use a normal CNAME alongside the zone’s required SOA and NS records.

C:

Azure Private DNS is for private-network resolution, not general public recursive DNS queries. It does not publish the wildcard mapping required for Internet clients of the public App Service app.

D:

A certificate allows TLS authentication for hostnames covered by it, but it does not publish DNS or register a custom hostname with App Service. Those are separate prerequisites.

Question 587

A domain moves to a new app and users intermittently hit the old host. What should the administrator do to resolve this specific case?

  1. Add custom domain binding and validate domain ownership in App Service.
  2. Clean unused DNS mappings and validate TXT ownership records before migration.
  3. Update DNS/bindings and account for resolver TTL propagation.
  4. Use supported A/ALIAS/ANAME solution and ownership verification depending on DNS provider.

Explanation

Correct Answer

C:

Resolvers can cache the old DNS target until the record's TTL expires, while the new App Service must also have the custom hostname bound. Update and verify both configurations and account for cache propagation instead of attributing every transient old-host response to application code.

Incorrect Answers

A:

Adding a domain binding proves ownership and makes the host reachable; it does not handle TLS enforcement or DNS provider limitations alone.

B:

Removing stale DNS aliases addresses domain migration hygiene; it does not add the new supported apex mapping or enforce certificate settings.

D:

A/ALIAS/ANAME DNS record choice points a host to the app; it doesn't automatically establish App Service hostname ownership or HTTPS.

Question 588

An Azure App Service website was deleted, but a public DNS CNAME still points `old.example.com` to its abandoned default Azure Websites hostname. Security wants to eliminate a potential dangling-domain takeover. What should be done?

  1. Grant subscription Owner to every web visitor so the host can be reclaimed.
  2. Remove or update the dangling DNS CNAME and verify remaining TXT/domain ownership records and valid App Service hostname bindings.
  3. Enable anonymous Blob access for the retired hostname.
  4. Change the App Service plan SKU of an unrelated live site; dangling DNS cannot be abused when another plan exists.

Explanation

Correct Answer

B:

Removing stale DNS mappings eliminates references to unclaimed provider hostnames; validating ownership records and active bindings guards against reattachment.

Incorrect Answers

A:

Azure RBAC for web visitors cannot protect an abandoned domain record and would expose administrative authority.

C:

Blob anonymous access has no role in protecting abandoned App Service custom domain records.

D:

Changing an unrelated plan does not correct a stale authoritative CNAME to a deleted app.

Question 589

An App Service app runs in a tier that supports scheduled custom backups. Operations require an explicit weekly downloadable backup stored in an approved Azure Storage account. What should the administrator configure?

  1. Rely on an unconfigured automatic backup because it always permits exporting a file to the designated storage account.
  2. Create a supported App Service custom backup schedule and point it to the approved storage target with valid access.
  3. Enable Azure VM Backup on the app’s underlying platform-managed worker machines.
  4. Configure a DNS TXT ownership record to trigger scheduled App Service content backups.

Explanation

Correct Answer

B:

Custom backups can be scheduled on supported tiers and written to an authorized storage location for download and restore.

Incorrect Answers

A:

Automatic App Service backups are different from configured downloadable custom backups and do not use a user-selected blob storage destination.

C:

The worker infrastructure is platform-managed; Azure VM Backup of those workers is not the supported App Service application backup control.

D:

DNS ownership verification affects custom domains, not scheduling data-protection jobs.

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.