When configuring an application to use the App Gateway, you do not have to change any configurations in the application directly. You enable the application for App Gateway access in the Admin…

Question

Options

• AExisting links and bookmarks do not work outside of the corporate network.
• BUsers must use different URLs depending on whether they access the application internally or externally.
• CMore configuration is needed because you must upload the URL certificate and private key, and edit DNS settings.
• DUsers must use the same URLs regardless of whether they access the application internally or externally.

• A
  86% (25)
• B
  3% (1)
• C
  3% (1)
• D
  7% (2)

Explanation

Option A is correct because internal URLs (e.g., http://app.company.local) are only resolvable within the corporate network. When remote users try to access the application using the same internal URL outside the network, DNS cannot resolve it, meaning any existing bookmarks or hardcoded links simply fail to connect.

Option B is wrong because it actually describes the scenario you'd want to avoid - needing different URLs is a problem, not a characteristic of internal URLs. The issue with internal URLs is that they don't work externally at all, not that they require a different URL externally.

Option C is wrong because the question explicitly states no application-side configuration changes are required for App Gateway setup; uploading certificates and editing DNS are not cited disadvantages of the internal URL option specifically.

Option D is wrong because using the same URL regardless of location is actually a goal, not a disadvantage - and the external URL option is what CyberArk provides to achieve this seamlessly.

Memory tip: Think "internal stays internal." An internal URL lives inside the network perimeter - drag it outside, and it goes dark. Any bookmark pointing to it becomes useless the moment a user goes remote.

No community discussion yet for this question.