An admin is troubleshooting domain verification for 'example.org'. They have added the TXT record, but verification fails. They use 'dig' and see the record, but the TTL is very high (e.g., 86400). What is the likely impact?

The high TTL may cause delays in Atlassian seeing the updated record, but it will eventually verify.

The high TTL indicates the record is invalid and must be changed.

The admin must wait for the TTL to expire before verification can be attempted.

The high TTL prevents the record from being seen by Atlassian at all.

A company uses multiple domains for employee emails, e.g., 'company.com' and 'company.co.uk'. They want to enforce SAML SSO for all employees. What must the admin do regarding domain verification?

Verify only the primary domain; the others will be automatically verified.

Verify each domain separately in the admin console.

Use a wildcard TXT record to verify all subdomains.

Create a new organization for each domain.

A company has two Atlassian organizations: one for internal employees (domain 'internal.com') and one for external contractors (domain 'external.com'). They want to enforce SAML SSO for internal employees only. What is the best approach?

Verify both domains in the internal organization and configure SAML SSO for all users.

Verify only 'internal.com' in the internal organization and ignore the external organization.

Create a new organization for the contractors and verify 'external.com' there, but do not verify 'internal.com'.

Verify 'internal.com' in the internal organization and 'external.com' in the external organization, then configure SAML SSO only in the internal organization.

After clicking 'Add domain' in the Atlassian admin console, what is the next step the admin must take to initiate verification?

Upload a certificate file to the domain's web server

Send an email to the domain's WHOIS contact for approval

Enter the domain name and click 'Continue' to receive the DNS TXT record

Create a new subdomain and point it to Atlassian's servers

AtlassianCloud Organization Admin

Domain 1Objective 2

Verify Domains ACP-520 Practice Questions (Page 1)

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 1–5

1application · medium
An admin is troubleshooting domain verification for 'example.org'. They have added the TXT record, but verification fails. They use 'dig' and see the record, but the TTL is very high (e.g., 86400). What is the likely impact?
Select an answer first
2application · medium
A company uses multiple domains for employee emails, e.g., 'company.com' and 'company.co.uk'. They want to enforce SAML SSO for all employees. What must the admin do regarding domain verification?
Select an answer first
3application · medium
A small business wants to verify its domain 'smallbiz.com' in Atlassian Cloud. The admin is not sure if they have the necessary permissions. Which administrator role is required to add and verify a domain in the Atlassian admin console?
Select an answer first
4expert · hard
A company has two Atlassian organizations: one for internal employees (domain 'internal.com') and one for external contractors (domain 'external.com'). They want to enforce SAML SSO for internal employees only. What is the best approach?
Select an answer first
5foundation · easy
After clicking 'Add domain' in the Atlassian admin console, what is the next step the admin must take to initiate verification?
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.