New Year Sale 2026! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions
Mail Us support@pass4success.com
Location US
Mob_nav_barsMENU

CyberArk CPC-SEN Exam - Topic 1 Question 6 Discussion

Actual exam question for CyberArk's CPC-SEN exam
Question #: 6
Topic #: 1
[All CPC-SEN Questions]

Your customer recently merged with a smaller organization. The customer's connector has no network connectivity to the smaller organization's infrastructure. You need to map LDAP users from both your customer and the smaller organization. How is this achieved?

Show Suggested Answer Hide Answer
Suggested Answer: C

To map LDAP users from both your customer and the smaller organization they have merged with, especially when there is no network connectivity between the two infrastructures, the best approach is to:

Deploy Identity Connectors in the newly acquired infrastructure and create user mappings (Option C). This involves setting up additional Identity Connectors within the smaller organization's network. These connectors will facilitate the integration of user directories from both organizations into the customer's Privilege Cloud environment.


by Dalene at May 23, 2024, 01:47 PM

Limited Time Offer

25%

Off

Get Premium CPC-SEN Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

0/2000 characters
Submit Cancel
Karon
3 months ago
I thought SAML was just for single sign-on, not for this!
upvoted 0 times
...
Stefany
3 months ago
A is definitely not the way to go.
upvoted 0 times
...
Bambi
3 months ago
Wait, can you really only have one Identity Connector?
upvoted 0 times
...
Nathalie
4 months ago
I disagree, B could work too if set up right.
upvoted 0 times
...
Ceola
4 months ago
Option C seems like the best choice here.
upvoted 0 times
...
Cordie
4 months ago
I feel like deploying Identity Connectors in the new infrastructure makes sense, but I can't recall if there are any limitations we need to consider.
upvoted 0 times
...
Clement
4 months ago
I’m a bit confused about whether we can really only have one Identity Connector. I thought we could deploy more if needed.
upvoted 0 times
...
Clay
4 months ago
I think we practiced a similar question where we had to create mappings for multiple directories, so option B sounds familiar.
upvoted 0 times
...
Stephane
5 months ago
I remember we discussed the importance of having multiple Identity Connectors for different directories, but I'm not sure if that applies here.
upvoted 0 times
...
Aleta
5 months ago
This question is a bit tricky, but I think I've got a good handle on it. The key is that the customer's connector can't access the smaller organization's infrastructure, so we need to set up a new connector in the newly acquired environment. Option C is the way to go.
upvoted 0 times
...
Catalina
5 months ago
I'm pretty confident that the answer is C. Deploying Identity Connectors in the newly acquired infrastructure and creating user mappings seems like the most straightforward solution, given the network connectivity issue. The other options don't seem to address that constraint.
upvoted 0 times
...
Lonna
5 months ago
Okay, I've got it! Since the customer's connector can't access the smaller organization's infrastructure, we need to deploy a new Identity Connector in the newly acquired environment. That way, we can create user mappings for both directories independently. Option C is the way to go.
upvoted 0 times
...
Ailene
5 months ago
Hmm, this is a tricky one. I'm a bit confused about the limitations around having only one Identity Connector. Does that mean we can't use the original connector to map both directories? I'm not sure, I'll have to think this through carefully.
upvoted 0 times
...
Johnathon
5 months ago
I think the key here is that the customer's connector has no network connectivity to the smaller organization's infrastructure. That means we can't use the original connector to map both directories. I'm leaning towards option C - deploying Identity Connectors in the newly acquired infrastructure and creating user mappings.
upvoted 0 times
...
Deane
5 months ago
I'm pretty confident about this one. The question is asking about the ideal frequency for reviewing risks, not the actual practice. Option D, "Risks remain under constant review," seems like the most appropriate answer to ensure the countermeasures stay up-to-date.
upvoted 0 times
...
Frank
5 months ago
Alright, let's do this. I know the budget process well, so I think I can tackle this question efficiently. I'll carefully consider each option and select the best one.
upvoted 0 times
...
Regenia
5 months ago
I remember studying about Kinesis services, but I'm not entirely sure which one specifically stores data in Parquet format.
upvoted 0 times
...
Reena
2 years ago
Option C all the way! Deploy those Identity Connectors and get those user mappings set up. Easy peasy lemon squeezy.
upvoted 0 times
...
Daniel
2 years ago
A is definitely not the answer. How is creating users in one directory and configuring the connector to read that going to work when the infrastructures are separate?
upvoted 0 times
Lelia
2 years ago
A) Create the required users in one directory and configure the Identity Connector to read that directory, as there can only be one Identity Connector.
upvoted 0 times
...
Jamie
2 years ago
C) Deploy Identity Connectors in the newly acquired infrastructure and create user mappings.
upvoted 0 times
...
An
2 years ago
B) Create mappings for both directories from the original Identity Connector.
upvoted 0 times
...
...
Felicitas
2 years ago
B looks good. Mapping both directories from the original connector seems like a reasonable solution.
upvoted 0 times
...
Blondell
2 years ago
D? What? Switching to SAML just because there can only be one Identity Connector? That's crazy talk.
upvoted 0 times
Ceola
2 years ago
D? What? Switching to SAML just because there can only be one Identity Connector? That's crazy talk.
upvoted 0 times
...
Alysa
2 years ago
B) Create mappings for both directories from the original Identity Connector.
upvoted 0 times
...
Alecia
2 years ago
A) Create the required users in one directory and configure the Identity Connector to read that directory, as there can only be one Identity Connector.
upvoted 0 times
...
...
Curtis
2 years ago
I think option C is the way to go. Having separate Identity Connectors in the newly acquired infrastructure makes the most sense to me.
upvoted 0 times
Joye
2 years ago
Yeah, deploying Identity Connectors in the newly acquired infrastructure would ensure smooth user mappings.
upvoted 0 times
...
Dominic
2 years ago
C) Deploy Identity Connectors in the newly acquired infrastructure and create user mappings.
upvoted 0 times
...
Carmen
2 years ago
I agree, option C seems like the most logical choice in this scenario.
upvoted 0 times
...
Wai
2 years ago
A) Create the required users in one directory and configure the Identity Connector to read that directory, as there can only be one Identity Connector.
upvoted 0 times
...
...

Save Cancel