mcAfee Secure Website
23

Microsoft DP-300 Bundle

Exam Code: DP-300

Exam Name Administering Microsoft Azure SQL Solutions

Certification Provider: Microsoft

Corresponding Certification: Microsoft Certified: Azure Database Administrator Associate

DP-300 Training Materials $44.99

Reliable & Actual Study Materials for DP-300 Exam Success

The Latest DP-300 Exam Questions as Experienced in the Actual Test!

  • 24
    Questions & Answers

    DP-300 Questions & Answers

    470 Questions & Answers

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

  • 25
    DP-300 Video Course

    DP-300 Training Course

    130 Video Lectures

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

  • exam =30
    Study Guide

    DP-300 Study Guide

    672 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

Administering Microsoft Azure SQL Solutions (DP-300) 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

    470 Questions

    $124.99
    exam =35
  • exam =37
    DP-300 Video Course

    Training Course

    130 Video Lectures

    $39.99
  • exam =36
    Study Guide

    Study Guide

    672 PDF Pages

    $29.99

Microsoft DP-300 Practice Test 81

Question 800

An Azure SQL operations team investigates: A restored SQL Server VM database remains in restoring state after all planned logs because final recovery was not issued. Select TWO complementary answers: the targeted corrective action AND the evidence that verifies it.

  1. Plan native SQL Server full, differential and transaction log backup chains with frequency tied to recovery objectives on supported platforms.
  2. Configure active geo-replication for supported Azure SQL Database individual databases to create readable secondaries and initiate supported failover.
  3. Telemetry and a safe failover exercise demonstrate acceptable replication delay, data consistency and application routing.
  4. Apply SQL Server backup restoration in the correct full, optional differential and transaction-log order, using NORECOVERY until final recovery.
  5. A rehearsed restore applies the intended complete backup chain and opens the database only after final RECOVERY.

Explanation

Correct Answers

D:

The reported Azure SQL or SQL Server condition is: A restored SQL Server VM database remains in restoring state after all planned logs because final recovery was not issued. The specific supported administrative response is: Apply SQL Server backup restoration in the correct full, optional differential and transaction-log order, using NORECOVERY until final recovery. The technical risk is: Recovering the database too early or restoring an incompatible log backup can prevent remaining backup application. Confirm the correction with: A rehearsed restore applies the intended complete backup chain and opens the database only after final RECOVERY.

E:

The acceptance evidence for this incident (A restored SQL Server VM database remains in restoring state after all planned logs because final recovery was not issued.) is: A rehearsed restore applies the intended complete backup chain and opens the database only after final RECOVERY. It directly tests whether the remediation (Apply SQL Server backup restoration in the correct full, optional differential and transaction-log order, using NORECOVERY until final recovery.) solves the specified issue, instead of proving an unrelated database control works.

Incorrect Answers

A:

Native SQL server full differential and log backups (5.2) addresses another technical failure: An incomplete log chain or wrong recovery model can prevent recovery to the desired point after a failure. The case states: A restored SQL Server VM database remains in restoring state after all planned logs because final recovery was not issued. The most direct paired action and test is: Apply SQL Server backup restoration in the correct full, optional differential and transaction-log order, using NORECOVERY until final recovery.

B:

Azure SQL database active geo-replication (5.3) addresses another technical failure: An asynchronous geo-secondary may lag behind the primary and individual database failover does not automatically coordinate a multi-database application. This choice can be useful for that problem, but it does not establish the Native restore sequence with norecovery and recovery (5.2) control being assessed here.

C:

Monitoring replica health and lag across ha dr (5.3) would demonstrate or implement: Telemetry and a safe failover exercise demonstrate acceptable replication delay, data consistency and application routing. This case instead tests Native restore sequence with norecovery and recovery (5.2); the choice measures or changes another part of the system.

Question 801

An Azure database administrator observes: An on-premises SQL Server backs up directly to an approved Azure Blob container. Which action best addresses the specific technical requirement?

  1. Monitor SQL HA/DR replica synchronization, redo or log-send queues, failover readiness and user connection validation at the relevant platform layer.
  2. Plan native SQL Server full, differential and transaction log backup chains with frequency tied to recovery objectives on supported platforms.
  3. Use supported SQL Server BACKUP TO URL and RESTORE FROM URL workflows with correctly scoped storage access and verified backup artifacts.
  4. Select supported read replicas and routing according to whether reporting should offload reads or the business requires writable primary failover.

Explanation

Correct Answer

C:

The reported Azure SQL or SQL Server condition is: An on-premises SQL Server backs up directly to an approved Azure Blob container. The specific supported administrative response is: Use supported SQL Server BACKUP TO URL and RESTORE FROM URL workflows with correctly scoped storage access and verified backup artifacts. The technical risk is: Unreachable Blob storage, expired credentials or unverified backup integrity can make a cloud backup unusable in a disaster. Confirm the correction with: A restore test retrieves the Blob backup and validates the resulting database without exposing storage credentials.

Incorrect Answers

A:

Monitoring replica health and lag across ha dr (5.3) addresses another technical failure: A replica shown as connected can still be too far behind or unhealthy to satisfy recovery objectives. The case states: An on-premises SQL Server backs up directly to an approved Azure Blob container. The most direct evidence is: Use supported SQL Server BACKUP TO URL and RESTORE FROM URL workflows with correctly scoped storage access and verified backup artifacts.

B:

Native SQL server full differential and log backups (5.2) addresses another technical failure: An incomplete log chain or wrong recovery model can prevent recovery to the desired point after a failure. This choice can be useful for that problem, but it does not establish the SQL server backup and restore to azure blob storage (5.2) control being assessed here.

D:

Read-scale replicas versus writable ha requirements (5.1) addresses another technical failure: A read-only secondary cannot simply accept all transactional writes after switchover without supported role promotion and client redirection. The required evidence concerns SQL server backup and restore to azure blob storage (5.2); a passing result for this alternative could leave that requirement unresolved.

Question 802

During post-change validation, the team reports: An on-premises SQL Server backs up directly to an approved Azure Blob container. Which observation best demonstrates that the appropriate correction worked?

  1. A restore chain replay reaches a chosen timestamp and DBCC or application integrity checks pass.
  2. A restore test retrieves the Blob backup and validates the resulting database without exposing storage credentials.
  3. Representative read and write tests confirm intended routing before and after a planned role change.
  4. Telemetry and a safe failover exercise demonstrate acceptable replication delay, data consistency and application routing.

Explanation

Correct Answer

B:

The acceptance evidence for this incident (An on-premises SQL Server backs up directly to an approved Azure Blob container.) is: A restore test retrieves the Blob backup and validates the resulting database without exposing storage credentials. It directly tests whether the remediation (Use supported SQL Server BACKUP TO URL and RESTORE FROM URL workflows with correctly scoped storage access and verified backup artifacts.) solves the specified issue, instead of proving an unrelated database control works.

Incorrect Answers

A:

Native SQL server full differential and log backups (5.2) would demonstrate or implement: A restore chain replay reaches a chosen timestamp and DBCC or application integrity checks pass. The case states: An on-premises SQL Server backs up directly to an approved Azure Blob container. The most direct evidence is: A restore test retrieves the Blob backup and validates the resulting database without exposing storage credentials.

C:

Read-scale replicas versus writable ha requirements (5.1) would demonstrate or implement: Representative read and write tests confirm intended routing before and after a planned role change. This case instead tests SQL server backup and restore to azure blob storage (5.2); the choice measures or changes another part of the system.

D:

Monitoring replica health and lag across ha dr (5.3) would demonstrate or implement: Telemetry and a safe failover exercise demonstrate acceptable replication delay, data consistency and application routing. The required evidence concerns SQL server backup and restore to azure blob storage (5.2); a passing result for this alternative could leave that requirement unresolved.

Question 803

An Azure database administrator observes: A DBA stores a SAS token in a public deployment script that runs BACKUP TO URL. Which action best addresses the specific technical requirement?

  1. Use supported SQL Server BACKUP TO URL and RESTORE FROM URL workflows with correctly scoped storage access and verified backup artifacts.
  2. Monitor SQL HA/DR replica synchronization, redo or log-send queues, failover readiness and user connection validation at the relevant platform layer.
  3. Select supported read replicas and routing according to whether reporting should offload reads or the business requires writable primary failover.
  4. Plan native SQL Server full, differential and transaction log backup chains with frequency tied to recovery objectives on supported platforms.

Explanation

Correct Answer

A:

The reported Azure SQL or SQL Server condition is: A DBA stores a SAS token in a public deployment script that runs BACKUP TO URL. The specific supported administrative response is: Use supported SQL Server BACKUP TO URL and RESTORE FROM URL workflows with correctly scoped storage access and verified backup artifacts. The technical risk is: Unreachable Blob storage, expired credentials or unverified backup integrity can make a cloud backup unusable in a disaster. Confirm the correction with: A restore test retrieves the Blob backup and validates the resulting database without exposing storage credentials.

Incorrect Answers

B:

Monitoring replica health and lag across ha dr (5.3) addresses another technical failure: A replica shown as connected can still be too far behind or unhealthy to satisfy recovery objectives. This choice can be useful for that problem, but it does not establish the SQL server backup and restore to azure blob storage (5.2) control being assessed here.

C:

Read-scale replicas versus writable ha requirements (5.1) addresses another technical failure: A read-only secondary cannot simply accept all transactional writes after switchover without supported role promotion and client redirection. This case instead tests SQL server backup and restore to azure blob storage (5.2); the choice measures or changes another part of the system.

D:

Native SQL server full differential and log backups (5.2) addresses another technical failure: An incomplete log chain or wrong recovery model can prevent recovery to the desired point after a failure. The required corrective action concerns SQL server backup and restore to azure blob storage (5.2); a passing result for this alternative could leave that requirement unresolved.

Question 804

In a database operations review, a team encounters: A DBA stores a SAS token in a public deployment script that runs BACKUP TO URL. Which failure or exposure is most directly relevant?

  1. Unreachable Blob storage, expired credentials or unverified backup integrity can make a cloud backup unusable in a disaster.
  2. A replica shown as connected can still be too far behind or unhealthy to satisfy recovery objectives.
  3. An incomplete log chain or wrong recovery model can prevent recovery to the desired point after a failure.
  4. A read-only secondary cannot simply accept all transactional writes after switchover without supported role promotion and client redirection.

Explanation

Correct Answer

A:

The incident (A DBA stores a SAS token in a public deployment script that runs BACKUP TO URL.) most directly exposes: Unreachable Blob storage, expired credentials or unverified backup integrity can make a cloud backup unusable in a disaster. The resulting safe technical response is: Use supported SQL Server BACKUP TO URL and RESTORE FROM URL workflows with correctly scoped storage access and verified backup artifacts. Its verification is: A restore test retrieves the Blob backup and validates the resulting database without exposing storage credentials.

Incorrect Answers

B:

Monitoring replica health and lag across ha dr (5.3) would demonstrate or implement: A replica shown as connected can still be too far behind or unhealthy to satisfy recovery objectives. This choice can be useful for that problem, but it does not establish the SQL server backup and restore to azure blob storage (5.2) control being assessed here.

C:

Native SQL server full differential and log backups (5.2) would demonstrate or implement: An incomplete log chain or wrong recovery model can prevent recovery to the desired point after a failure. This case instead tests SQL server backup and restore to azure blob storage (5.2); the choice measures or changes another part of the system.

D:

Read-scale replicas versus writable ha requirements (5.1) would demonstrate or implement: A read-only secondary cannot simply accept all transactional writes after switchover without supported role promotion and client redirection. The required risk concerns SQL server backup and restore to azure blob storage (5.2); a passing result for this alternative could leave that requirement unresolved.

Question 805

An Azure database administrator observes: A SQL Server on Azure VM cannot read its Blob backup after a storage credential expires. Which action best addresses the specific technical requirement?

  1. Monitor SQL HA/DR replica synchronization, redo or log-send queues, failover readiness and user connection validation at the relevant platform layer.
  2. Plan native SQL Server full, differential and transaction log backup chains with frequency tied to recovery objectives on supported platforms.
  3. Select supported read replicas and routing according to whether reporting should offload reads or the business requires writable primary failover.
  4. Use supported SQL Server BACKUP TO URL and RESTORE FROM URL workflows with correctly scoped storage access and verified backup artifacts.

Explanation

Correct Answer

D:

The reported Azure SQL or SQL Server condition is: A SQL Server on Azure VM cannot read its Blob backup after a storage credential expires. The specific supported administrative response is: Use supported SQL Server BACKUP TO URL and RESTORE FROM URL workflows with correctly scoped storage access and verified backup artifacts. The technical risk is: Unreachable Blob storage, expired credentials or unverified backup integrity can make a cloud backup unusable in a disaster. Confirm the correction with: A restore test retrieves the Blob backup and validates the resulting database without exposing storage credentials.

Incorrect Answers

A:

Monitoring replica health and lag across ha dr (5.3) addresses another technical failure: A replica shown as connected can still be too far behind or unhealthy to satisfy recovery objectives. The case states: A SQL Server on Azure VM cannot read its Blob backup after a storage credential expires. The most direct corrective action is: Use supported SQL Server BACKUP TO URL and RESTORE FROM URL workflows with correctly scoped storage access and verified backup artifacts.

B:

Native SQL server full differential and log backups (5.2) addresses another technical failure: An incomplete log chain or wrong recovery model can prevent recovery to the desired point after a failure. This choice can be useful for that problem, but it does not establish the SQL server backup and restore to azure blob storage (5.2) control being assessed here.

C:

Read-scale replicas versus writable ha requirements (5.1) addresses another technical failure: A read-only secondary cannot simply accept all transactional writes after switchover without supported role promotion and client redirection. This case instead tests SQL server backup and restore to azure blob storage (5.2); the choice measures or changes another part of the system.

Question 806

During post-change validation, the team reports: A SQL Server on Azure VM cannot read its Blob backup after a storage credential expires. Which observation best demonstrates that the appropriate correction worked?

  1. Representative read and write tests confirm intended routing before and after a planned role change.
  2. A restore chain replay reaches a chosen timestamp and DBCC or application integrity checks pass.
  3. Telemetry and a safe failover exercise demonstrate acceptable replication delay, data consistency and application routing.
  4. A restore test retrieves the Blob backup and validates the resulting database without exposing storage credentials.

Explanation

Correct Answer

D:

The acceptance evidence for this incident (A SQL Server on Azure VM cannot read its Blob backup after a storage credential expires.) is: A restore test retrieves the Blob backup and validates the resulting database without exposing storage credentials. It directly tests whether the remediation (Use supported SQL Server BACKUP TO URL and RESTORE FROM URL workflows with correctly scoped storage access and verified backup artifacts.) solves the specified issue, instead of proving an unrelated database control works.

Incorrect Answers

A:

Read-scale replicas versus writable ha requirements (5.1) would demonstrate or implement: Representative read and write tests confirm intended routing before and after a planned role change. The case states: A SQL Server on Azure VM cannot read its Blob backup after a storage credential expires. The most direct evidence is: A restore test retrieves the Blob backup and validates the resulting database without exposing storage credentials.

B:

Native SQL server full differential and log backups (5.2) would demonstrate or implement: A restore chain replay reaches a chosen timestamp and DBCC or application integrity checks pass. This choice can be useful for that problem, but it does not establish the SQL server backup and restore to azure blob storage (5.2) control being assessed here.

C:

Monitoring replica health and lag across ha dr (5.3) would demonstrate or implement: Telemetry and a safe failover exercise demonstrate acceptable replication delay, data consistency and application routing. This case instead tests SQL server backup and restore to azure blob storage (5.2); the choice measures or changes another part of the system.

Question 807

An Azure database administrator observes: An enterprise wants off-host copies of native SQL Server backups for disaster recovery. Which action best addresses the specific technical requirement?

  1. Monitor SQL HA/DR replica synchronization, redo or log-send queues, failover readiness and user connection validation at the relevant platform layer.
  2. Use supported SQL Server BACKUP TO URL and RESTORE FROM URL workflows with correctly scoped storage access and verified backup artifacts.
  3. Plan native SQL Server full, differential and transaction log backup chains with frequency tied to recovery objectives on supported platforms.
  4. Select supported read replicas and routing according to whether reporting should offload reads or the business requires writable primary failover.

Explanation

Correct Answer

B:

The reported Azure SQL or SQL Server condition is: An enterprise wants off-host copies of native SQL Server backups for disaster recovery. The specific supported administrative response is: Use supported SQL Server BACKUP TO URL and RESTORE FROM URL workflows with correctly scoped storage access and verified backup artifacts. The technical risk is: Unreachable Blob storage, expired credentials or unverified backup integrity can make a cloud backup unusable in a disaster. Confirm the correction with: A restore test retrieves the Blob backup and validates the resulting database without exposing storage credentials.

Incorrect Answers

A:

Monitoring replica health and lag across ha dr (5.3) addresses another technical failure: A replica shown as connected can still be too far behind or unhealthy to satisfy recovery objectives. The case states: An enterprise wants off-host copies of native SQL Server backups for disaster recovery. The most direct corrective action is: Use supported SQL Server BACKUP TO URL and RESTORE FROM URL workflows with correctly scoped storage access and verified backup artifacts.

C:

Native SQL server full differential and log backups (5.2) addresses another technical failure: An incomplete log chain or wrong recovery model can prevent recovery to the desired point after a failure. This case instead tests SQL server backup and restore to azure blob storage (5.2); the choice measures or changes another part of the system.

D:

Read-scale replicas versus writable ha requirements (5.1) addresses another technical failure: A read-only secondary cannot simply accept all transactional writes after switchover without supported role promotion and client redirection. The required corrective action concerns SQL server backup and restore to azure blob storage (5.2); a passing result for this alternative could leave that requirement unresolved.

Question 808

In a database operations review, a team encounters: An enterprise wants off-host copies of native SQL Server backups for disaster recovery. Which failure or exposure is most directly relevant?

  1. An incomplete log chain or wrong recovery model can prevent recovery to the desired point after a failure.
  2. A replica shown as connected can still be too far behind or unhealthy to satisfy recovery objectives.
  3. A read-only secondary cannot simply accept all transactional writes after switchover without supported role promotion and client redirection.
  4. Unreachable Blob storage, expired credentials or unverified backup integrity can make a cloud backup unusable in a disaster.

Explanation

Correct Answer

D:

The incident (An enterprise wants off-host copies of native SQL Server backups for disaster recovery.) most directly exposes: Unreachable Blob storage, expired credentials or unverified backup integrity can make a cloud backup unusable in a disaster. The resulting safe technical response is: Use supported SQL Server BACKUP TO URL and RESTORE FROM URL workflows with correctly scoped storage access and verified backup artifacts. Its verification is: A restore test retrieves the Blob backup and validates the resulting database without exposing storage credentials.

Incorrect Answers

A:

Native SQL server full differential and log backups (5.2) would demonstrate or implement: An incomplete log chain or wrong recovery model can prevent recovery to the desired point after a failure. The case states: An enterprise wants off-host copies of native SQL Server backups for disaster recovery. The most direct risk is: Unreachable Blob storage, expired credentials or unverified backup integrity can make a cloud backup unusable in a disaster.

B:

Monitoring replica health and lag across ha dr (5.3) would demonstrate or implement: A replica shown as connected can still be too far behind or unhealthy to satisfy recovery objectives. This choice can be useful for that problem, but it does not establish the SQL server backup and restore to azure blob storage (5.2) control being assessed here.

C:

Read-scale replicas versus writable ha requirements (5.1) would demonstrate or implement: A read-only secondary cannot simply accept all transactional writes after switchover without supported role promotion and client redirection. This case instead tests SQL server backup and restore to azure blob storage (5.2); the choice measures or changes another part of the system.

Question 809

An Azure database administrator observes: A backup job reports success but the recovery team has never tested restoring from the cloud storage URL. Which action best addresses the specific technical requirement?

  1. Use supported SQL Server BACKUP TO URL and RESTORE FROM URL workflows with correctly scoped storage access and verified backup artifacts.
  2. Monitor SQL HA/DR replica synchronization, redo or log-send queues, failover readiness and user connection validation at the relevant platform layer.
  3. Plan native SQL Server full, differential and transaction log backup chains with frequency tied to recovery objectives on supported platforms.
  4. Select supported read replicas and routing according to whether reporting should offload reads or the business requires writable primary failover.

Explanation

Correct Answer

A:

The reported Azure SQL or SQL Server condition is: A backup job reports success but the recovery team has never tested restoring from the cloud storage URL. The specific supported administrative response is: Use supported SQL Server BACKUP TO URL and RESTORE FROM URL workflows with correctly scoped storage access and verified backup artifacts. The technical risk is: Unreachable Blob storage, expired credentials or unverified backup integrity can make a cloud backup unusable in a disaster. Confirm the correction with: A restore test retrieves the Blob backup and validates the resulting database without exposing storage credentials.

Incorrect Answers

B:

Monitoring replica health and lag across ha dr (5.3) addresses another technical failure: A replica shown as connected can still be too far behind or unhealthy to satisfy recovery objectives. This choice can be useful for that problem, but it does not establish the SQL server backup and restore to azure blob storage (5.2) control being assessed here.

C:

Native SQL server full differential and log backups (5.2) addresses another technical failure: An incomplete log chain or wrong recovery model can prevent recovery to the desired point after a failure. This case instead tests SQL server backup and restore to azure blob storage (5.2); the choice measures or changes another part of the system.

D:

Read-scale replicas versus writable ha requirements (5.1) addresses another technical failure: A read-only secondary cannot simply accept all transactional writes after switchover without supported role promotion and client redirection. The required corrective action concerns SQL server backup and restore to azure blob storage (5.2); a passing result for this alternative could leave that requirement unresolved.

Question 810

An Azure SQL operations team investigates: A backup job reports success but the recovery team has never tested restoring from the cloud storage URL. Select TWO complementary answers: the targeted corrective action AND the evidence that verifies it.

  1. Plan native SQL Server full, differential and transaction log backup chains with frequency tied to recovery objectives on supported platforms.
  2. Select supported read replicas and routing according to whether reporting should offload reads or the business requires writable primary failover.
  3. Use supported SQL Server BACKUP TO URL and RESTORE FROM URL workflows with correctly scoped storage access and verified backup artifacts.
  4. Telemetry and a safe failover exercise demonstrate acceptable replication delay, data consistency and application routing.
  5. A restore test retrieves the Blob backup and validates the resulting database without exposing storage credentials.

Explanation

Correct Answers

C:

The reported Azure SQL or SQL Server condition is: A backup job reports success but the recovery team has never tested restoring from the cloud storage URL. The specific supported administrative response is: Use supported SQL Server BACKUP TO URL and RESTORE FROM URL workflows with correctly scoped storage access and verified backup artifacts. The technical risk is: Unreachable Blob storage, expired credentials or unverified backup integrity can make a cloud backup unusable in a disaster. Confirm the correction with: A restore test retrieves the Blob backup and validates the resulting database without exposing storage credentials.

E:

The acceptance evidence for this incident (A backup job reports success but the recovery team has never tested restoring from the cloud storage URL.) is: A restore test retrieves the Blob backup and validates the resulting database without exposing storage credentials. It directly tests whether the remediation (Use supported SQL Server BACKUP TO URL and RESTORE FROM URL workflows with correctly scoped storage access and verified backup artifacts.) solves the specified issue, instead of proving an unrelated database control works.

Incorrect Answers

A:

Native SQL server full differential and log backups (5.2) addresses another technical failure: An incomplete log chain or wrong recovery model can prevent recovery to the desired point after a failure. The case states: A backup job reports success but the recovery team has never tested restoring from the cloud storage URL. The most direct paired action and test is: Use supported SQL Server BACKUP TO URL and RESTORE FROM URL workflows with correctly scoped storage access and verified backup artifacts.

B:

Read-scale replicas versus writable ha requirements (5.1) addresses another technical failure: A read-only secondary cannot simply accept all transactional writes after switchover without supported role promotion and client redirection. This choice can be useful for that problem, but it does not establish the SQL server backup and restore to azure blob storage (5.2) control being assessed here.

D:

Monitoring replica health and lag across ha dr (5.3) would demonstrate or implement: Telemetry and a safe failover exercise demonstrate acceptable replication delay, data consistency and application routing. The required paired action and test concerns SQL server backup and restore to azure blob storage (5.2); a passing result for this alternative could leave that requirement unresolved.