Question: 1
Note: This question is part of a series of questions that present the same scenario. Each question in the series contains a unique solution that might meet goals. Some question sets might have more than one correct solution, while others might not have a correct solution.
After you answer a question in this section, you will NOT be able to return to it As a result these
questions will not appear in the review screen.
You have a database named DB1 that is 640 GB and is updated frequently.
You enabled log shipping for DB1 and configure backup and restore to occur every 30 minutes.
You discover that the disks on the data server are almost full.
You need to reduce the amount of disk space used by the log shipping process.
Solution: You configure log shipping to backup and restore by using shared folder.
Does this meet the goal?
A. Yes
B. No
Answer: B
Question: 2
Note: This question is part of a series of questions that present the same scenario. Each question in the
series contains a unique solution that might meet goals. Some question sets might have more than one
correct solution, while others might not have a correct solution.
After you answer a question in this section, you will NOT be able to return to it As a result these
questions will not appear in the review screen.
You have a database named DB1 that is 640 GB and is updated frequently.
You enabled log shipping for DB1 and configure backup and restore to occur every 30 minutes.
You discover that the disks on the data server are almost full.
You need to reduce the amount of disk space used by the log shipping process.
Solution: You enable compression for the transaction log backups:
Does this meet the goal?
A. Yes
B. No
Answer: A
Explanation:
SQL Server 2017 supports backup compression. When creating a log shipping configuration, you can
control the backup compression behavior of log backups by choosing one of the following options: Use
the default server setting, Compress backup, or Do not compress backup
Note: SQL Server 2008 Enterprise and later versions support backup compression.
References:
https://docs.microsoft.com/en-us/sql/database-engine/log-shipping/configure-log-shipping-sqlserver?view=sql-server-2017
Question: 3
Note: This question is part of a series of questions that present the same scenario. Each question in the
series contains a unique solution that might meet goals. Some question sets might have more than one
correct solution, while others might not have a correct solution.
After you answer a question in this section, you will NOT be able to return to it As a result these
questions will not appear in the review screen.
You have a database named DB1 that is 640 GB and is updated frequently.
You enabled log shipping for DB1 and configure backup and restore to occur every 30 minutes.
You discover that the disks on the data server are almost full.
You need to reduce the amount of disk space used by the log shipping process.
Solution: You increase the frequency of the transaction log backups to every 10 minutes.
Does this meet the goal?
A. Yes
B. No
Answer: B
Question: 4
Note: This question is part of a series of questions that present the same scenario. Each question in the
series contains a unique solution that might meet the stated goals. Some question sets might have more
than one correct solution, while others might not have a correct solution.
After you answer a question in this section, you will NOT be able to return to it. As a result, these
questions will not appear in the review screen.
You need to configure a Microsoft SQL Server instance to ensure that a user named Mail1 can send mail
by using Database Mail.
Solution: You add the DatabaseMailUserRole to Mail1 in the tempdb database.
Does the solution meet the goal?
A. Yes
B. No
Answer: B
Explanation:
Database Mail is guarded by the database role DatabaseMailUserRole in the msdb database, not the
tempdb database, in order to prevent anyone from sending arbitrary emails. Database users or roles
must be created in the msdb database and must also be a member of DatabaseMailUserRole in order to
send emails with the exception of sysadmin who has all privileges.
Note: Database Mail was first introduced as a new feature in SQLServer 2005 and replaces the SQL Mail
feature found in previous versions.
References:
http://www.idevelopment.info/data/SQLServer/DBA_tips/Database_Administration/DBA_20.shtml
Question: 5
Note: This question is part of a series of questions that present the same scenario. Each question in the
series contains a unique solution that might meet the stated goals. Some question sets might have more
than one correct solution, while others might not have a correct solution.
After you answer a question in this section, you will NOT be able to return to it. As a result, these
questions will not appear in the review screen.
You need to configure a Microsoft SQL Server instance to ensure that a user named Mail1 can send mail
by using Database Mail.
Solution: You add the DatabaseMailUserRole to Mail1 in the msdb database.
Does the solution meet the goal?
A. Yes
B. No
Answer: A
Explanation:
Database Mail is guarded by the database role DatabaseMailUserRole in the msdb database in order to
prevent anyone from sending arbitrary emails. Database users or roles must be created in the msdb
database and must also be a member of DatabaseMailUserRole in order to send emails with the
exception of sysadmin who has all privileges.
Note: Database Mail was first introduced as a new feature in SQL Server 2005 and replaces the SQL Mail
feature found in previous versions.
References:
http://www.idevelopment.info/data/SQLServer/DBA_tips/Database_Administration/DBA_20.shtml
Pass Your Microsoft 70-764 Actual Test And Get Certified | Practice Question Answers
No comments:
Post a Comment