Cyber Monday 2024! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Citrix Exam 1Y0-204 Topic 14 Question 81 Discussion

Actual exam question for Citrix's 1Y0-204 exam
Question #: 81
Topic #: 14
[All 1Y0-204 Questions]

Scenario: A Citrix Administrator will use PowerShell to configure a new restart schedule for the Windows 2016 Server OS group named ''Win2016-ServerOS'' within a Citrix Virtual Desktops infrastructure.

The administrator needs the machines in the Server OS group to restart at a time when no users will be accessing them: beginning at 23:00h (11:00 PM) each day, with 30-minute intervals between each machine restart.

Which PowerShell command should the administrator use?

Show Suggested Answer Hide Answer

Contribute your Thoughts:

Stephaine
2 months ago
This is a piece of cake! Just use Option B and your servers will be good as new, ready to face the day. Or night, in this case.
upvoted 0 times
Christa
1 months ago
Thanks for the tip! I'll go ahead and implement Option B for the server restart schedule.
upvoted 0 times
...
Christa
1 months ago
Great choice! Option B is the correct PowerShell command to use for the restart schedule.
upvoted 0 times
...
Christa
1 months ago
Option B) New-BrokerRebootScheduleV2 -Name XYZ-ServerOS-DailyReboot -DesktopGroupName Win2016-ServerOS -Frequency Daily -StartTime ''23:00'' -Enabled $true - RebootDuration 30
upvoted 0 times
...
...
Kimberely
2 months ago
Option A seems to have the right idea, but the start time is off. Why not just use 23:00 instead of 11:00? Gotta love that 24-hour time, am I right?
upvoted 0 times
Keshia
1 months ago
User 3: I agree, using 23:00 makes more sense for a late-night restart schedule.
upvoted 0 times
...
Dana
1 months ago
User 2: Yeah, 24-hour time is definitely the way to go for scheduling tasks like this.
upvoted 0 times
...
Tien
1 months ago
Option A is close, but the start time should be 23:00 instead of 11:00.
upvoted 0 times
...
...
Carey
2 months ago
I'm not sure why anyone would want to reboot their servers at 11:00 PM. That's my bedtime! Option B is the way to go.
upvoted 0 times
Maira
1 months ago
User 3: It's important to schedule reboots at a time when users won't be impacted.
upvoted 0 times
...
Kattie
1 months ago
User 2: Option B is definitely the best choice for the restart schedule.
upvoted 0 times
...
Yan
2 months ago
I agree, 11:00 PM is too late for server reboots.
upvoted 0 times
...
...
Tasia
2 months ago
I'd go with Option D. The 'Set-BrokerRebootSchedule' cmdlet seems more appropriate for configuring an existing reboot schedule.
upvoted 0 times
Margo
1 months ago
Let's use Set-BrokerRebootSchedule for configuring the restart schedule.
upvoted 0 times
...
Aretha
1 months ago
Setting the reboot schedule with Set-BrokerRebootSchedule is the best option.
upvoted 0 times
...
Lettie
2 months ago
I agree, Set-BrokerRebootSchedule seems like the right choice.
upvoted 0 times
...
Roslyn
2 months ago
Option D is the way to go.
upvoted 0 times
...
...
Haydee
2 months ago
I'm not sure, but I think C) Set-BrokerRebootScheduleV2 could also be a valid option.
upvoted 0 times
...
Alline
3 months ago
Option B looks good to me. It starts the reboot schedule at 11:00 PM, which is when no users will be accessing the servers.
upvoted 0 times
Christiane
2 months ago
That's perfect timing when no users will be accessing the servers.
upvoted 0 times
...
Arleen
2 months ago
Yeah, Option B starts the reboot schedule at 11:00 PM.
upvoted 0 times
...
Leigha
2 months ago
I think Option B is the correct one.
upvoted 0 times
...
...
James
3 months ago
I agree with Francisca, because the command specifies the correct start time of 23:00h.
upvoted 0 times
...
Francisca
3 months ago
I think the answer is B) New-BrokerRebootScheduleV2.
upvoted 0 times
...

Save Cancel
az-700  pass4success  az-104  200-301  200-201  cissp  350-401  350-201  350-501  350-601  350-801  350-901  az-720  az-305  pl-300  

Warning: Cannot modify header information - headers already sent by (output started at /pass.php:70) in /pass.php on line 77