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

Microsoft Exam AZ-800 Topic 8 Question 38 Discussion

Actual exam question for Microsoft's AZ-800 exam
Question #: 38
Topic #: 8
[All AZ-800 Questions]

Task 1

You need to prevent domain users from saving executable files in a share named \\SRVl\Dat

a. The users must be able to save other files to the share.

Show Suggested Answer Hide Answer
Suggested Answer: A

One possible solution to prevent domain users from saving executable files in a share named SRVlData is to use file screening on the file server. File screening allows you to block certain files from being saved based on their file name extension. Here are the steps to configure file screening:

On the file server, openFile Server Resource Managerfrom theAdministrative Toolsmenu.

In the left pane, expandFile Screening Managementand click onFile Groups.

Right-click onFile Groupsand selectCreate File Group.

In theFile Group Propertiesdialog box, enter a name for the file group, such asExecutable Files.

In theFiles to includebox, enter the file name extensions that you want to block, such as.exe, .bat, .cmd, .com, .msi, .scr. You can use wildcards to specify multiple extensions, such as *.exe.

ClickOKto create the file group.

In the left pane, click onFile Screen Templates.

Right-click onFile Screen Templatesand selectCreate File Screen Template.

In theFile Screen Template Propertiesdialog box, enter a name for the template, such asBlock Executable Files.

On theSettingstab, select the optionActive screening: Do not allow users to save unauthorized files.

On theFile Groupstab, check the box next to the file group that you created, such asExecutable Files.

On theNotificationtab, you can configure how to notify users and administrators when a file screening event occurs, such as sending an email, logging an event, or running a command or script. You can also customize the message that users see when they try to save a blocked file.

ClickOKto create the file screen template.

In the left pane, click onFile Screens.

Right-click onFile Screensand selectCreate File Screen.

In theCreate File Screendialog box, enter the path of the folder that you want to apply the file screening to, such asSRVlData.

Select the optionDerive properties from this file screen template (recommended)and choose the template that you created, such asBlock Executable Files.

ClickCreateto create the file screen.

Now, domain users will not be able to save executable files in the share named SRVlData. They will be able to save other files to the share.


Contribute your Thoughts:

Lewis
8 months ago
What if we set up a separate share for approved executables and have users request access if they need to install something? That way we maintain control without shutting down the main share completely.
upvoted 0 times
Tish
8 months ago
Agreed, let's give it a shot and see how it goes.
upvoted 0 times
...
Georgene
8 months ago
It's definitely better than completely shutting down the main share for everyone.
upvoted 0 times
...
Genevive
8 months ago
I think it's worth trying out to see if it helps prevent any security risks.
upvoted 0 times
...
Latanya
8 months ago
It could be a bit of a hassle, but at least we would have more control over what is being saved on the main share.
upvoted 0 times
...
Edmond
8 months ago
But wouldn't it be a hassle for users to request access every time?
upvoted 0 times
...
Cruz
8 months ago
That sounds like a good idea.
upvoted 0 times
...
...
Art
8 months ago
Haha, I can already imagine the angry emails from users who can't save their 'totally-not-virus.exe' files anymore. But you're right, we need a solution that doesn't cripple their workflow.
upvoted 0 times
...
Chantell
8 months ago
I agree, we need to balance security and usability. Maybe we could use file type filtering or access control lists to allow certain types of files but block executables specifically.
upvoted 0 times
...
Cherri
8 months ago
This question seems straightforward, but I'm a little worried about the potential impact on user productivity if we can't let them save executable files. Maybe we could explore a more targeted solution instead of just blocking everything.
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