If you de-provision a user that has been synced to G Suite or O365 from within Jumpcloud, what
happens to the G Suite or O365 account(s)? Select the correct answer.
Suggested Answer: C
Get Premium JumpCloud-Core Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
14 comments · newest first
SU
Susana
12 months ago
Yeah, B makes sense. Syncing means full control.
HU
Huey
12 months ago
Wait, are you sure? I thought it was A.
RO
Rory
12 months ago
Definitely B, I've seen it happen before.
ER
Ernie
1 year ago
I thought it just suspended access, not deleted!
EM
Emilio
1 year ago
B is the correct answer, user gets deleted.
AN
Annamae
1 year ago
I feel like the answer is B, but I could also see it being C since suspending access seems like a safer option.
BU
Buffy
1 year ago
I’m a bit confused about this one. I thought de-provisioning just meant they lose access, but does it actually delete the account?
GE
Georgiana
1 year ago
I think if you de-provision a user, it might delete their account in G Suite or O365, but I'm not entirely sure.
RH
Rhea
1 year ago
I remember practicing a question like this, and I think the user gets suspended rather than deleted.
SH
Sharmaine
1 year ago
I think the answer is C. The firewall-cmd --query-service http command seems like the most straightforward way to check if the HTTP service is allowed through the firewall.
SC
Scarlet
1 year ago
Hmm, I'm a little unsure about this one. I'll need to think through the different options carefully to make sure I understand the implications of each setting.
CL
Clemencia
1 year ago
Hmm, I'm not sure about this one. I know arguments are passed to console apps, but I thought they were in a string array, not a Hashtable. Let me think this through carefully.
LA
Lashaun
1 year ago
Ah, I remember this from the training materials! After the UniversalInstaller, the next step is the AvayaAura Contact Center Configuration Wizard, so I'm going to go with option A.
LA
Lang
1 year ago
This seems straightforward. Since we need to control who can send email to the team channels, the external collaboration settings in the Azure Active Directory admin center is likely the right place to make the necessary changes.