MENU
An investigator his successfully installed the ExchangeOnlineManagement module on their investigation system and is attempting to search a client's Microsoft 365 Unified Audit Log using PowerShell. PowerShell returns a "command not found" error each time they try to execute the Search-UnifiedAuditLog cmdlet. How should the investigator troubleshoot this issue?
Suggested Answer: C
Get Premium GCFR Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
32 comments · newest first
RO
Rozella
10 months ago
I thought .NET version 4.b was required for all cmdlets, is that not true?
CA
Cassi
11 months ago
Make sure you're using PowerShell Core, that's a common mistake!
ST
Stephaine
11 months ago
Wait, why would MFA need to be disabled? That seems risky.
BE
Bea
11 months ago
Definitely, permissions are key for accessing the audit log!
TY
Ty
11 months ago
You need to check the permissions of the account used in Microsoft 365.
MA
Madonna
11 months ago
I believe permissions are crucial for accessing the audit log, so maybe checking the account's permissions in Microsoft 365 could be a good first step.
SA
Samira
12 months ago
I practiced a question similar to this, and I feel like checking the PowerShell version is important, but I can't recall if it specifically needs to be PowerShell Core.
HU
Hubert
12 months ago
I think I read that MFA can sometimes cause issues with certain commands, but I'm not entirely clear on how it affects the Search-UnifiedAuditLog cmdlet.
KI
King
12 months ago
I remember something about needing the right version of .NET for certain cmdlets, but I'm not sure if it's 4.b or something else.
AL
Alison
12 months ago
I've encountered this problem before. I think the key is to make sure the account has the necessary permissions to access the Unified Audit Log. I'll carefully review the account settings.
ER
Erasmo
12 months ago
I'm a bit confused by this error. I wonder if there's some kind of compatibility issue with the ExchangeOnlineManagement module. I'll need to do some research to figure this out.
DO
Domitila
12 months ago
Okay, let's think this through step-by-step. First, I'll verify the PowerShell version and ensure I'm using the right one. Then I'll double-check the account permissions in M365.
WI
Willis
1 year ago
Hmm, this is a tricky one. I'll need to carefully check the system requirements and permissions to make sure I'm not missing anything obvious.
BE
Bev
1 year ago
D is definitely the way to go here. Permissions are everything when it comes to accessing that Unified Audit Log. Though I have to say, the idea of disabling MFA just to get this working is about as smart as using Internet Explorer for a cybersecurity investigation.
JI
Jill
1 year ago
D) Check the permissions of the account used in Microsoft 365
HA
Hassie
1 year ago
B) Ensure that MFA has been disabled for The account used
AM
Amira
1 year ago
A) Ensure their system has .NFT version 4.b or later Installed
YU
Yuriko
1 year ago
Ah, the joys of troubleshooting tech issues. I bet they're wishing they had a magic 8-ball to solve this one. Maybe they should try throwing some glitter at the problem - that's how I fix all my computer troubles!
CA
Candida
1 year ago
C) Check that they are using PowerShell Core
VE
Vernice
1 year ago
B) Ensure that MFA has been disabled for The account used
KA
Karl
1 year ago
A) Ensure their system has .NFT version 4.b or later Installed
MA
Marylou
1 year ago
Hmm, PowerShell Core, eh? Sounds like they're trying to be a trendy investigator. But hey, if it works, it works. Though I gotta say, turning off MFA is a bold move - not sure I'd recommend that one.
SE
Serina
1 year ago
Maybe they should also ensure their system has .NET version 4.0 or later installed.
NO
Noe
1 year ago
D is the way to go here. Permissions are key when it comes to accessing the Unified Audit Log. I bet they forgot to give the account the necessary admin rights.
GE
Geoffrey
1 year ago
User2: Absolutely, without the right permissions, you can't access the Unified Audit Log.
BO
Boris
1 year ago
User1: D is definitely important. Permissions can cause a lot of issues.
MA
Marti
1 year ago
I agree with Paola. It's important to make sure the account has the necessary permissions.
CL
Clarence
2 years ago
Ah, the classic 'command not found' error. Looks like they need to check their PowerShell version and permissions. Let's hope they don't try to solve this by turning off MFA - that would be a security nightmare!
SV
Svetlana
1 year ago
D) Check the permissions of the account used in Microsoft 365
BU
Bulah
1 year ago
C) Check that they are using PowerShell Core
DA
Danilo
1 year ago
A) Ensure their system has .NFT version 4.b or later Installed
PA
Paola
2 years ago
I think the investigator should check the permissions of the account used in Microsoft 365.