| Author |
NetChild's Wed 70-216 QOD
|
|
| NetChild1985 2003-04-02, 12:41 am |
| Your network is connected to the company network via a Windows 2000 Routing and Remote Access two-way demand-dial connection over ISDN. The ISDN link must only be used once each day to transfer sales information to or from the main office during non-business hours. Several times a day, an ISDN link is initiated between the networks. You analyze the traffic and discover that it is composed of router announcement broadcasts. What should you do to prevent the link from being used during business hours? (Choose two)
A. Schedule the demand-dial interface to dial only during business hours
B. Set the Remote Access Policy to only allow connections after business hours
C. Create a demand-dial filter on the interface
D. Set a TCP/IP filter on the interface to prevent broadcast messages from passing
Good luck! We'll see you tomorrow with the correct answers!  | |
| dogzpaw 2003-04-02, 5:07 am |
| hmmmmm. I'd go with C and...A(?)
IF the DD interface had been configured to dial out during NON-business hours? | |
|
| There are not two answers provided that would accomplish the objective. Specifically, no answer places a constraint on the demand dial interface to only dial during NON-business hours.
"C" - configure a demand dial filter on the interface is one for sure.
"A" would work if it stated "NON-business hours"
"B" - RAS policies apply to inbound connections, not outbound.
"D" - a TCP/IP filter really wouldn't apply in this scenario.
The only answer provided, which is only part of the solution is "C". But I think we really want "C" and "A"  | |
| NetChild1985 2003-04-02, 9:52 am |
| quote:
Originally posted by Spid
There are not two answers provided that would accomplish the objective. Specifically, no answer places a constraint on the demand dial interface to only dial during NON-business hours.
"C" - configure a demand dial filter on the interface is one for sure.
"A" would work if it stated "NON-business hours"
"B" - RAS policies apply to inbound connections, not outbound.
"D" - a TCP/IP filter really wouldn't apply in this scenario.
The only answer provided, which is only part of the solution is "C". But I think we really want "C" and "A"
Good thinking... | |
| dogzpaw 2003-04-02, 10:47 am |
| Have tried a similar set-up on my lab, thats what made me think of C (yeh! For sure) and A (if configured correctly)  | |
| cramersaunders 2003-04-02, 12:06 pm |
| CA | |
| bbraunstein 2003-04-02, 12:23 pm |
| I'll go with "C" and "A" as well.
BB | |
| NetChild1985 2003-04-02, 11:05 pm |
| quote:
Originally posted by NetChild1985
Your network is connected to the company network via a Windows 2000 Routing and Remote Access two-way demand-dial connection over ISDN. The ISDN link must only be used once each day to transfer sales information to or from the main office during non-business hours. Several times a day, an ISDN link is initiated between the networks. You analyze the traffic and discover that it is composed of router announcement broadcasts. What should you do to prevent the link from being used during business hours? (Choose two)
A. Schedule the demand-dial interface to dial only during business hours
B. Set the Remote Access Policy to only allow connections after business hours
C. Create a demand-dial filter on the interface
D. Set a TCP/IP filter on the interface to prevent broadcast messages from passing
Good luck! We'll see you tomorrow with the correct answers!
And the correct answers are: A and C
To prevent the calling router from making unnecessary on-demand dial-up connections, which may result in excessive phone charges, we can use demand-dial filtering to configure either the types of IP traffic that do not cause a connection to be made or the types of IP traffic that cause a connection to be made and/or we can use dial-out hours to configure the hours that a calling router is either permitted or denied to make a demand-dial connection. |
|
|
|