An admin is setting up domain verification for 'acme.com'. They have added the domain in the admin console and received the TXT record. They add the record to DNS, but then realize they added it to the wrong domain (e.g., 'acme.org'). What should the admin do?

Verify acme.org instead and then change the domain in Atlassian.

Add the same record to acme.com without removing the one on acme.org.

Contact Atlassian support to manually verify acme.com.

Remove the record from acme.org and add it to acme.com, then retry verification.

An organization wants to use Atlassian Access to enforce SAML SSO for all users with email addresses on the domain 'mycompany.com'. The admin has already added the domain in the admin console. What is the primary reason the domain must be verified before SAML SSO can be enforced?

To enable the domain to be used as a custom URL for the Atlassian site.

To prove the organization owns the domain, which is required to manage users and apply security policies.

To allow Atlassian to send billing invoices to the domain's email addresses.

To ensure the domain's email server is configured to receive Atlassian notifications.

An admin is verifying 'example.com' and has added the TXT record. Verification fails. The admin uses a DNS lookup tool and sees the TXT record, but the value is correct. They also notice that the domain has DNSSEC enabled. What could be the issue?

The TXT record must be signed with DNSSEC to be valid.

The admin must add a DS record to the DNS settings.

DNSSEC must be disabled for verification to work.

DNSSEC is not the issue; the record may be cached or the name may be incorrect.

A company with 500 employees wants to use Atlassian Access to enforce SAML SSO and automated user provisioning for their existing Atlassian Cloud org. They have a custom domain, 'example.com', used for employee email addresses. The admin has already created the organization and added the domain in the admin console. What must the admin do next to complete the setup?

Add the DNS TXT record provided by Atlassian to the DNS settings for example.com, then click 'Verify' in the admin console.

Upload a CSV file of all employee email addresses to the admin console to trigger verification.

Contact Atlassian support to manually verify the domain since it is a large organization.

Create a new site in the organization and assign the domain to that site before verification.

An admin is verifying 'example.com' and has added the TXT record. Verification fails, and the admin suspects DNS propagation delay. They have already waited 48 hours. They use a DNS checker and see the record, but the TTL is set to 86400. What is the best action?

Use a VPN to access the admin console and retry.

Wait another 48 hours before retrying.

Delete the TXT record and add it again with a different value.

Retry verification; if it still fails, check the record for exactness and consider lowering the TTL.

AtlassianCloud Organization Admin

Domain 1Objective 2

Verify Domains ACP-520 Practice Questions (Page 4)

Part of the Organization Settings domain, which makes up ~27% of our current practice bank. Atlassian does not publish an official question count, but from its 90-minute exam (~35–60 total, ~9–16 in this domain), expect 5–8 from this objective — we provide 26 practice questions to prepare you well beyond it. (estimate)

26questions here

6free pages

5concepts

Questions 16–20

16application · medium
An admin is setting up domain verification for 'acme.com'. They have added the domain in the admin console and received the TXT record. They add the record to DNS, but then realize they added it to the wrong domain (e.g., 'acme.org'). What should the admin do?
Select an answer first
17application · medium
An organization wants to use Atlassian Access to enforce SAML SSO for all users with email addresses on the domain 'mycompany.com'. The admin has already added the domain in the admin console. What is the primary reason the domain must be verified before SAML SSO can be enforced?
Select an answer first
18expert · hard
An admin is verifying 'example.com' and has added the TXT record. Verification fails. The admin uses a DNS lookup tool and sees the TXT record, but the value is correct. They also notice that the domain has DNSSEC enabled. What could be the issue?
Select an answer first
19application · medium
A company with 500 employees wants to use Atlassian Access to enforce SAML SSO and automated user provisioning for their existing Atlassian Cloud org. They have a custom domain, 'example.com', used for employee email addresses. The admin has already created the organization and added the domain in the admin console. What must the admin do next to complete the setup?
Select an answer first
20expert · hard
An admin is verifying 'example.com' and has added the TXT record. Verification fails, and the admin suspects DNS propagation delay. They have already waited 48 hours. They use a DNS checker and see the record, but the TTL is set to 86400. What is the best action?
Select an answer first

Finished these 5 questions?

Review the revealed explanations, or continue through the curriculum.

Next 5 questions →Back to ACP-520

Free Basic Practice is a study aid with revealable answers — not a scored exam. Examers.io is independent and not affiliated with or endorsed by Atlassian. “ACP-520” is a trademark of its owner, used for identification only.