Your network contains a Network Policy Server (NPS) server named Server1. The network
contains a server named SQL1 that has Microsoft SQL Server 2008 R2 installed. All servers
run Windows Server 2012 R2.
You configure NPS on Server1 to log accounting data to a database on SQL1.
You need to ensure that the accounting data is captured if SQL1 fails. The solution must
minimize cost.
What should you do?
A.
Implement Failover Clustering.
B.
Implement database mirroring.
C.
Run the Accounting Configuration Wizard.
D.
Modify the SQL Server Logging properties.
Explanation:
In Windows Server 2008 R2, an accounting configuration wizard is added to the Accounting
node in the NPS console. By using the Accounting Configuration wizard, you can configure
the following four accounting settings:
• SQL logging only. By using this setting, you can configure a data link to a SQL
Server that allows NPS to connect to and send accounting data to the SQL server. In
addition, the wizard can configure the database on the SQL Server to ensure that the
database is compatible with NPS SQL server logging.
• Text logging only. By using this setting, you can configure NPS to log accounting
data to a text file.• Parallel logging. By using this setting, you can configure the SQL Server data link
and database. You can also configure text file logging so that NPS logs simultaneously to
the text file and the SQL Server database.
• SQL logging with backup. By using this setting, you can configure the SQL Server
data link and database. In addition, you can configure text file logging that NPS uses if SQL
Server logging fails.
Can anyone confirm the answer to this? Lots of answers online indicate C, but why would you re-run accounting config wizard when you can just alter properties of SQL Server Logging?
0
0
to minimize cost jst re-run the accounting config on ur nps server…. at least nps server also can accept accounting data
0
0
But why would you run the wizard instead of just Modifying SQL Server Properties?
0
0
Because it doesn’t make sense as many of the questions in this test.
Modify the SQL Server Logging properties is the answer that requires less administrative effort = less time = less cost!
0
0
Modify the SQL Server Logging properties would mean you are getting another SQL server, which does not minimize cost…
0
0
why getting another SQL server?
just check to option for “enable text file logging for failover” and you’re done, or am I missing something around here?
0
0
And to do that you need to run Configure Accounting Wizard.
0
0
I thinkl its because they want us to change logging from “SQL logging only” to “SQL logging with backup” so that in case SQL fails we still have accounting data logged.
0
0
In my humble opinion, It is the accounting data that matters, not the SQL server logging.
Well, there might be a small benefit on having English not as native tongue
0
0
f—- you
0
0
love thy neighbor
0
0
By using the accounting configuration wizard we can change the logging from SQL to both (SQL and text)
• Parallel logging. By using this setting, you can configure the SQL Server data link
and database. You can also configure text file logging so that NPS logs simultaneously to
the text file and the SQL Server database.
So, correct answer is C
0
0
but “You need to ensure that the accounting data is captured if SQL1 fails” and minimize cost: if data gets logged simultaneously then you have higher cost than if you just configure it for failover
0
0
I think I figured it out:
we have to assume that we have a default setup with just SQL logging configured. So when you just modify the SQL log settings and activate text file logging for failover then you get nothing because default state is not configured to log to any text file! I just tested this in lab…
But when you use the wizard then you are asked about the directory were to place the text logs!
So provided answer is correct
0
0
D is the answer
****
To configure SQL Server logging in NPS
Open the NPS console or the NPS Microsoft Management Console (MMC) snap-in.
In the console tree, click Accounting.
In the details pane, in SQL Server Logging Properties, click Change SQL Server Logging Properties. The SQL Server Logging Properties dialog box opens.
In Log the following information, select the information that you want to log:
To log all accounting requests, click Accounting requests.
To log authentication requests, click Authentication requests.
To log periodic accounting status, click Periodic accounting status.
To log periodic status, such as interim accounting requests, click Periodic status.
To configure the number of concurrent sessions allowed between the server running NPS and the SQL Server, type a number in Maximum number of concurrent sessions.
To configure the SQL Server data source, in SQL Server Logging, click Configure. The Data Link Properties dialog box opens. On the Connection tab, specify the following:
To specify the name of the server on which the database is stored, type or select a name in Select or enter a server name.
To specify the authentication method with which to log on to the server, click Use Windows NT integrated security. Or, click Use a specific user name and password, and then type credentials in User name and Password.
To allow a blank password, click Blank password.
To store the password, click Allow saving password.
To specify which database to connect to on the computer running SQL Server, click Select the database on the server, and then select a database name from the list.
To test the connection between NPS and SQL Server, click Test Connection. Click OK to close Data Link Properties.
——————————————————————————————–
In Logging failure action, select Enable text file logging for failover if you want NPS to continue with text file logging if SQL Server logging fails.
——————————————————————————————–
In Logging failure action, select If logging fails, discard connection requests if you want NPS to stop processing Access-Request messages when log files are full or unavailable for some reason. If you want NPS to continue processing connection requests if logging fails, do not select this check box.
https://technet.microsoft.com/fr-fr/library/ee663942(v=ws.10).aspx
0
0
In the console tree, click Accounting.
It’s C
0
0