Verify Domains ACP-520 Practice Questions (Page 5)

Questions 21–25

1. 21application · medium

   An admin is verifying the domain 'acme.io' for their Atlassian org. They added the TXT record provided by Atlassian to their DNS provider, but after 30 minutes the verification in the admin console still fails. The admin confirms the record name and value are correct. What is the most likely cause and what should the admin do?

   • AThe TXT record must be added as an SPF record instead; delete the TXT and add SPF.
   • BThe domain is not registered with a public DNS provider; switch to a different registrar.
   • CDNS propagation is still in progress; wait longer and retry verification.
   • DThe admin must verify the domain from a different Atlassian site first.
   Reveal Solution Discussion Select an answer first
2. 22foundation · easy

   Which of the following is a direct benefit of verifying a domain in the Atlassian admin console?

   • AIt creates a public DNS record that improves email deliverability
   • BIt allows the organization to claim and manage all Atlassian accounts using that domain
   • CIt enables the organization to use a custom URL for its Atlassian sites
   • DIt automatically grants all users admin permissions in the organization
   Reveal Solution Discussion Select an answer first
4. 23application · medium

   A company wants to verify its domain 'company.com' in Atlassian Cloud. The admin is logged into the Atlassian admin console and has navigated to the correct organization. What is the first step to initiate domain verification?

   • AGo to Settings > Security > Domains, click 'Add domain', enter 'company.com', and click 'Add'.
   • BGo to Products > Users, click 'Invite users', and enter the domain in the invitation email.
   • CGo to Settings > General, and change the organization URL to the domain.
   • DGo to Billing > Subscription, and add the domain as a payment method.
   Reveal Solution Discussion Select an answer first
5. 24application · medium

   An admin added the DNS TXT record for 'example.net' and waited several hours. They now click 'Verify' in the Atlassian admin console, but the status still shows 'Unverified'. They use an online DNS lookup tool and see the TXT record is present. What should the admin do next?

   • ARemove the domain and add it again with a different spelling.
   • BCreate a new Atlassian organization and try again.
   • CUse a VPN to access the admin console and retry.
   • DCheck if the TXT record is exactly as provided, including the name and value, then retry verification.
   Reveal Solution Discussion Select an answer first
6. 25application · medium

   An admin is verifying 'example.org' and has added the TXT record. After clicking 'Verify', the status remains 'Unverified'. The admin checks the DNS using a public resolver and sees the TXT record, but the value is slightly different from what Atlassian provided. What is the most likely cause?

   • AThe TXT record was entered incorrectly, such as a typo or extra character.
   • BThe domain's DNS is hosted on a private server that Atlassian cannot access.
   • CThe admin needs to verify the domain from a different Atlassian site.
   • DThe domain has been verified previously and cannot be re-verified.
   Reveal Solution Discussion Select an answer first