HOTSPOT
Your network contains an Active Directory domain named corp.contoso.com. The domain contains
two member servers named Server1 and Edge1. Both servers run Windows Server 2012 R2. Your
company wants to implement a central location where the system events from all of the servers in
the domain will be collected.
From Server1, a network technician creates a collector-initiated subscription for Edge1. You discover
that
Server1 does not contain any events from Edge1. You view the runtime status of the subscription as
shown in the exhibit. (Click the Exhibit button.)
Exhibit:
Hot Area:
Answer: Pending
Explanation:
Select Events
Proposed solution is “Select Events…” because of too much Events coming in to the collector.
See: https://social.technet.microsoft.com/Forums/windowsserver/en-US/bb5246a6-98f2-49a4-b7ed-5c7aa03b85da/2008-r2-forwarded-events-data-area-passed-to-system-call-is-too-small?forum=winserverManagement
0
0
My thoughts:
Events, cause you already select a computer nothing wrong
Advancad…? why..to use another user, not a logical thing to do right
or it is to select how to deliver the events, normal, minimal BW or Min Latency
But I can’t see if there are any events selected, so I ‘d say “Events”….
0
0
This “question” is confusing as it doesn’t ask you to do anything nor specify any requirements. Are you supposed to select where you would view the events? If that is the case then “select events” would seem to be the logical choice.
0
0
Check the error message in image one:
‘The data area passed to a system call is too small’
Which seems to indicate that too many events are selected and need to be reduced.
https://social.technet.microsoft.com/Forums/windowsserver/en-US/bb5246a6-98f2-49a4-b7ed-5c7aa03b85da/2008-r2-forwarded-events-data-area-passed-to-system-call-is-too-small?forum=winserverManagement
0
0